-
Bug
-
Resolution: Tracked Elsewhere
-
Medium (View bug fix roadmap)
-
None
-
6.1.6, 6.2.2
-
6.01
-
NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.
A project admin user moves an issue from Project A to Project B when still associated with Rapid Board A. The issue is added to the Project B rapid board.
Later a user in either Project A or Project B attempt to close their respective sprints in Project A or Project B rapid board. They are each greeted with an error:
Error
To update this sprint you must have Project Administrator permissions for all of the following projects: Project A, Project B.
It would be better if the move did not result in a requirement for an admin in both projects to close the sprint.
Also reported here in Confluence Docs:
https://confluence.atlassian.com/display/GH/Ending+a+Sprint?focusedCommentId=330795683#comment-330795683
This is really confusing to users because you can't remove the sprint from the moved issue unless that issue exists in some other board.
UPDATE: This also affects the ability to start sprint.
Workarounds
- Do a Bulk Edit on the moved issues to remove the value for the "Sprint" from those issues;
OR - Add the "Sprint" field to the Edit screens associated with the issue types for that project you moved issues to and edit the issues and remove the value for the "Sprint" field;
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
- is incorporated by
-
JSWSERVER-5035 As a JIRA/GH administrator, I would like to be able to specify who is allowed to create and start a sprint independently from the "Administer Projects" JIRA permission
- Closed
- relates to
-
-
- Closed
-
-
-
- Gathering Impact
-
-
- Closed
-
- Closed
[JSWSERVER-6850] Moving issue from project in rapid board to another project results in inability to close or start sprint for non admin
| Minimum Version | New: 6.01 |
| Workflow | Original: JAC Bug Workflow v2 [ 2850608 ] | New: JAC Bug Workflow v3 [ 2934440 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545313 ] | New: JAC Bug Workflow v2 [ 2850608 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1551906 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545313 ] |
| Description |
Original:
A project admin user moves an issue from Project A to Project B when still associated with Rapid Board A. The issue is added to the Project B rapid board.
Later a user in either Project A or Project B attempt to close their respective sprints in Project A or Project B rapid board. They are each greeted with an error: Error To update this sprint you must have Project Administrator permissions for all of the following projects: Project A, Project B. It would be better if the move did not result in a requirement for an admin in both projects to close the sprint. Also reported here in Confluence Docs: https://confluence.atlassian.com/display/GH/Ending+a+Sprint?focusedCommentId=330795683#comment-330795683 This is really confusing to users because you can't remove the sprint from the moved issue unless that issue exists in some other board. UPDATE: This also affects the ability to start sprint. h3. Workarounds * Do a *[Bulk Edit|https://confluence.atlassian.com/display/JIRA/Modifying+Multiple+(Bulk)+Issues#ModifyingMultiple(Bulk)Issues-PerformingaBulkOperation]* on the moved issues to remove the value for the "Sprint" from those issues; OR * Add the "Sprint" field to the *Edit* screens associated with the issue types for that project you moved issues to and edit the issues and remove the value for the "Sprint" field; |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Software Server*. Using *JIRA Software Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSWCLOUD-6850]. {panel} A project admin user moves an issue from Project A to Project B when still associated with Rapid Board A. The issue is added to the Project B rapid board. Later a user in either Project A or Project B attempt to close their respective sprints in Project A or Project B rapid board. They are each greeted with an error: Error To update this sprint you must have Project Administrator permissions for all of the following projects: Project A, Project B. It would be better if the move did not result in a requirement for an admin in both projects to close the sprint. Also reported here in Confluence Docs: https://confluence.atlassian.com/display/GH/Ending+a+Sprint?focusedCommentId=330795683#comment-330795683 This is really confusing to users because you can't remove the sprint from the moved issue unless that issue exists in some other board. UPDATE: This also affects the ability to start sprint. h3. Workarounds * Do a *[Bulk Edit|https://confluence.atlassian.com/display/JIRA/Modifying+Multiple+(Bulk)+Issues#ModifyingMultiple(Bulk)Issues-PerformingaBulkOperation]* on the moved issues to remove the value for the "Sprint" from those issues; OR * Add the "Sprint" field to the *Edit* screens associated with the issue types for that project you moved issues to and edit the issues and remove the value for the "Sprint" field; |
| Link |
New:
This issue relates to |
| Labels | Original: 1a affects-server fixme sprint st10 support | New: 1a affects-cloud affects-server fixme sprint st10 support |
| Labels | Original: 1a fixme sprint st10 support | New: 1a affects-server fixme sprint st10 support |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 908933 ] | New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1551906 ] |
| Remote Link | Original: This issue links to "Page (Extranet)" [ 111491 ] | New: This issue links to "Page (Extranet)" [ 111491 ] |
