Why do Moved issues still require Admin on OLD project?

[Randall Fisher]

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)

[Randall Fisher · Accepted solution]

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.)

[Jonas Andersson]

Because they set a different permission scheme on the other project. By applying the same permission scheme you would be able to do the same in both projects.

[Randall Fisher]

They have the same permission scheme. Why does one need ANY access in the OLD project once it is moved to a NEW project?