Issues in a sprint that have been cloned within the project, or to different projects prevent the sprint from being completed.
Error comes up stated that user must have project admin right in each of the projects that issues have been cloned in. After granting the project admin rights, user is still unable to complete the sprint.
As a jira admin, I can complete the sprint, however a warning comes up stating that the issues not completed in the sprint will be moved to the back log. All of the issue in the sprint are complete. The incomplete issues are the cloned issues that are in the other projects.
Is this a known issue? How are people getting around this?
When an issue in an active sprint is cloned, the relationship to the active sprint is being maintained as you've painfully discovered.
For those issues that are being cloned to be dealt with in a different release, we have added a same-state transition which clears the fields that we use to signal the need for Triage: Priority, Sprint and Scrum Team.
This way, if users are cloning items to help flush out a story/task, then they save time and have the work in the sprint.
The alternative, i think, if you want to optimize for "cloned issues should be triaged" would be to add a post-function to the issue create step which nulls out any Sprint value being submitted.
In that alternative, you'd have to somehow make sure that the cloned issues, which probably have your priority/fix version information, are caught by triage and don't get lost.
Either way, the user has to somehow make their intent known by editing the issue/pushing a button.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs