-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
None
-
Affects Version/s: JCMA - 1.9.0, JCMA - 1.10.3, JCMA - 1.12.3, JCMA - 1.12.7
-
Component/s: Jira - Migration Assistant - Export
-
20
-
Severity 3 - Minor
-
121
Issue Summary
Using JCMA 1.9.0, JSM Project was migrated to Cloud, priorities were added to cloud priorities but request types with customfield Priority set as hidden were migrated not correctly. Some of them are set to nothing as they are set as a default value and some of them show Error warning. All should have priority set as in source Jira DC.
The customer can set it up manually, but there are 506 migrated requesttypes and we don't know, why this had happened and how many other requesttypes are affected.
Please see the attached screenshots.
Steps to Reproduce
- create a JSM project
- create a custom field as Priority
- set the request type with customfield Priority as hidden
Expected Results
the actual Values for Priority field should be migrated
Actual Results
Missing default value - Some of them are set to nothing as they are set as a default value and some of them show Error warning.
Workaround
none
