Details
-
Bug
-
Resolution: Fixed
-
High
-
29
-
Severity 3 - Minor
-
82
-
Description
Issue Summary
Customer reporting custom field ´Impact´ was created by him according to the audit log but claims he didn't create it.
Steps to Reproduce
Not been replicable but below are the steps that should reproduce it. However, a620038e6229 could confirm in this Slack thred he could already see 2 Impact fields in his instance.
- Go to a test site
- Enable JSM product
- Create a project ITSM-1, and the Impact field should be created.
- Create another JSM project ITSM-11 with the option Share settings with an existing project and choose ITSM-1 for it
Expected Results
The existing Impact field should be used
Actual Results
Another Impact field was created
Workaround
Remove the duplicate and assign the existing field manually.
Attachments
Issue Links
- split to
-
JSDCLOUD-13035 Creating ITSM projects or Change issue type can cause duplicate field names
- Closed
-
JSDCLOUD-13036 Creating ITSM projects or Incident issue type can cause duplicate field names
- Short Term Backlog
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...