-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
1
-
5
-
Scenario
User is performing multiple project imports of projects that belonged to the same board / shared of the same sprint. For each import performed, JIRA creates a different sprint with the exact same name.
Expected Behaviour
JIRA would notice that the Sprint already exists throughout the import and not create a new one.
Workaround
Bulk edit the issue in the duplicated sprint to the original sprint by referring to the Sprint ID and not name. This will however, impact the reporting for the sprint if its related to an active sprint
- is related to
-
JRASERVER-61569 Project Import does not map issues to existing sprints
- Gathering Impact