Our folks in our Org, created the same sprint name across all projects. They also move issues across projects. Now the problem is that they cannot close the sprint since JIRA Agile keeps complaining that they do not have permissions to close the sprint since they are not apart of project administrators of the other project that they do not have access to or where the issue originated from. Only solution is make them project admins. Any ideas how to solve this issue.
Current Version : 5.2.11
Future Version : 6.4.12 (will upgrade shortly)
This is because when you clone an issue it clones everything including the Sprint information for the source project.
The easiest way to solve this problem would be to give project admin permissions on all such projects.
In medium term, to avoid this problem i would recommend to educate your users not to clone the sprint information. You can also set up email subscriptions to get notified if any of the user did this, i.e. cloned issues whilst retaining sprint information.
In long run, you can create your own clone operation using CLone plus plugin and customise the cloning operation and restrict the clonging of sprint information.
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