Here is a general example of the different scenarios where this issue is manifesting itself.
So a user moves an issue from project ABC to DEF. When admin duties on a sprint in JIRA Agile (new, active, or closed) that contains the Moved issue (in DEF), JIRA Agile will complain if the user does not have admin access to ABC.
Has anyone else observed this (or similar) behavior?
(JIRA 6.1.9 - JIRA Agile 6.6.80)
A user cannot move sprints on the backlog view if they do not have permission on all the issues assigned to sprints on the board, even if the issues in those sprints are being filtered out, off of, the board.
Do a quick audit of open issues in all projects in the error and ensure that there is not a sprint marker assigned from the board you are looking at. Use an issue filter, looking at open sprints, and look for a sprint that does not belong to the project the board covers. (Hopefully you do not use short Sprint names like 'Sprint 1' on all your projects.)
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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