-
Bug
-
Resolution: Duplicate
-
Medium
-
None
NOTE: This bug report is for JIRA Software Cloud. Using JIRA Software Server? See the corresponding bug report.
- A board is defined for a project X.
- A sprint is created and an issue in project X is added to it from the backlog.
- The same issue is now moved to a different project Y and so it no longer appears on the board but the Sprint field is still set for the issue.
- A User with project admin permission for project X but not project Y tries to close the sprint. GreenHopper says that the moved issue in project Y is stopping the sprint from being completed because the user doesn't have project admin permission
- If the user cannot edit the Sprint field directly there is no easy way to complete their sprint except to move the issue from Y back to X, view it in GreenHopper and use Remove from Sprint there, then move it back to Y
- duplicates
-
JSWCLOUD-6850 Moving issue from project in rapid board to another project results in inability to close or start sprint for non admin
- Closed
- is related to
-
JSWSERVER-9499 Moving issues can stop a sprint from being completed
- Closed