-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Affects Version/s: None
-
Component/s: Jira - Migration Assistant - Export
-
None
-
11
-
Minor
-
33
Issue Summary
This is reproducible on Data Center: yes
Steps to Reproduce
- Create an issue security scheme with more than one level
- Associate a project role/group picker/user picker to one of the levels
- Associate this issue security scheme with more than one project
- Use the JCMA to migrate the projects
Expected Results
JCMA will not create project role duplicated entries for a given issue security level.
Actual Results
For every project migration, JCMA will create an additional copy of the same project role for a given level.
| After the first migration | Second migration |
|---|---|
| Migrating one project | Migrating two projects that share the same issue security level |
| |
|
Workaround
- Delete the additional entries on every issue security level impacted by this through the UI
- Create a copy of the issue security level on the cloud and associate it with the projects after the migration is finished.
- First, migrate only one project
- Create a copy of the permission scheme used by this project on the cloud
- Migrate the remaining projects
- After the migration is finished, associate the copy of the issue security level scheme with the impacted projects