Skip to content
This repository has been archived by the owner on Dec 13, 2022. It is now read-only.

Problem with escalation's name during a duplication #5512

Closed
mariegallardo opened this issue Aug 4, 2017 · 1 comment
Closed

Problem with escalation's name during a duplication #5512

mariegallardo opened this issue Aug 4, 2017 · 1 comment
Labels
kind/enhancement status/implemented
Milestone
2.8.12

Comments

@mariegallardo
Copy link
Contributor

BUG REPORT INFORMATION

Centreon Web version: 2.8.10

Steps to reproduce the issue:
I create an escalation
I save it
I duplicate this escalation

Describe the results you received:
An ' 1' is added to the initial escalation name instead of a '_1'.

Describe the results you expected:
An '_1' should be added at the end of the initial name.
@lpinsivy lpinsivy added this to the 2.8.12 milestone Aug 4, 2017
lpinsivy added a commit that referenced this issue Aug 4, 2017
@lpinsivy
#5512 add underscore on object name on duplication
7257419
loiclau pushed a commit that referenced this issue Aug 4, 2017
@lpinsivy @loiclau
#5512 add underscore on object name on duplication (#5513)
93f0212
loiclau pushed a commit that referenced this issue Aug 4, 2017
@lpinsivy @loiclau
#5512 add underscore on object name on duplication (#5513)
4090008
@thiuyendang
Copy link
Contributor

OK 2.8.12-4; centOS6, centOS7

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/enhancement status/implemented
Projects
None yet
Milestone
2.8.12
Development

No branches or pull requests
4 participants
@loiclau @lpinsivy @mariegallardo @thiuyendang