When attempting to close a sprint Jira Software reviews issues within the sprint to determine if the user has the proper permissions in order to close it.
In larger environments this can be notoriously difficult to track down because board filters can be complex and issue history is taken into account. Consider the following example:
- simple board filter, project = A, sprint id 42
- Creating an issue in project B, mistakenly select sprint 42
- Fix sprint on issue in project B
Because an issue in project B was mistakenly assigned a sprint from project A a user will now need the Manage Sprint permission in A and B in order to close sprint 42. Currently the user nor the administrator will be able to determine this in the product itself.
This request is to provide a message visible to Jira administrators informing them of which projects need the 'Manage Sprint' permission in order to close a sprint and ideally why.
Notes
See further documentation for background