Manage Sprint Permissions bug

[Bhav]

A Scrum Master attempted to "Start Sprint" on their board (lets call that Project A) but received the error that they needed Manage Sprint permissions of all issues in their Backlog to progress.

After doing some digging we found that a ticket in their Backlog was "moved" from another Project (lets call that Project B) to theirs and was causing the block.

To fix this, we needed to provide the Scrum Master Manage Sprint permissions on Project B to allow them to start their sprint on Project A.

I'm not sure why we had to do this since the ticket move from Project B to Project A was successful.

Is this a bug? 

Cheers

[Danyal Iqbal]

+1 for bug if the creator of the sprint recieves the same error .

[Mirek]

I think it is not a bug. First check your board filter and what issues are returned. Then you would see if there is any reference to other projects. Usually people are facing exactly this problem

https://confluence.atlassian.com/jirakb/users-with-the-permission-to-administer-projects-in-a-sprint-are-still-unable-to-start-a-sprint-779159069.html

[Rilwan Ahmed]

This bug even present in Jira 8.2.1 also

[Bhav]

I came up against this problem again for another user where a ticket had "moved" from Project B to Project A.

In order to resolve, I will need to provide the user with Administer rights to Project B which I think is really bad, since the user has nothing to do with Project B. I dont like the idea of giving multiple people Administer rights to a Project they are not involved in.

Surely there is a bug in the "Moving" of a ticket from one project to another where it is retaining details of the origin project even though it is no longer required.