Cloned Issues and 'Manage Sprints' permission

[Joe Emett]

Hi there,

A user had reported that 'Complete Sprint' was greyed out, even though he had the 'Manage Sprints' permission for all projects specified in the JQL query behind the board.

On closer inspection I found there were cloned issues derived from an issue in the project contained in the JQL query behind the board, which belonged to a project where he did not have 'Manage Sprints' permission. When I gave him that permission on the project of the cloned issue, he was able to 'Complete Sprint'.

My expectation is that the user should of been able to Open/Close any sprint for any projects contained within the returned JQL query, and there is no consideration taken of cloned issues and permissions of the project the cloned issue is associated with, but the user requires 'Manage Sprints' permission on the projects where issues have been cloned.

Thanks very much

[Petter Gonçalves · Accepted solution]

Hello Joe,

You are correct. The general "Manage Sprint" permission will always be applied to the JQL Query behind the board's project, considering ALL the issues returned by the query and the cloned ones.

The root cause of this behavior is that the cloned issues inherit the Sprint value from the "parent" issue in the database, so basically, the cloned issue is also part of the Sprint the user was trying to complete and the cloned issue project will be applied to the permission too.

We have opened a bug to fix this behavior here:

- Cloned issues inherit the Completed Sprint value and can't be removed

Feel free to watch the bug to be notified about the progress of our developers.

Let me know if this information answers your question, Joe.

[Joe Emett]

Thanks very much for your reply, Petterson, yes it does answer my question,

Joe

[Petter Gonçalves]

You are welcome, Joe!

Have a nice day.