We just solved an issue where a user had added a demo issue within a sandbox environment to a live sprint that was just about to start. Upon attempting to start the sprint, the Project Manager of the live project received an error stating he needed Administrative priveleges over the Sandbox project.
My question is: how do I prevent people that administer project A that do not have any priveleges for Project B in adding issues to sprints belonging to Project B? I do not want to remove the 'Sprint' field from the screen, as it's also visual feedback for the actual users of this functionality.
It appears that it is not possible for now, where it should be. This could led to a confusion as the sprint field will still populating any Sprint regardless of the project or permission. It appears that this have raised as a story in our issue tracker system:
I would like to suggest you to watch, vote and add a comment on the ticket, so the developer could review it.
Hope this information could be useful.
Thanks for pointing out the ticket Julian. I wish I could upvote it once for every user affected by it, as although not all visitors to this forum have an enterprise setup for JIRA with many projects in one instance, it does affect many more users with only me reporting it.
I'll keep an eye on the progress.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
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