-
Suggestion
-
Resolution: Duplicate
-
None
Problem Definition
The Manage sprints permission introduces the "origin board concept for sprint" which is important to identify who can complete a sprint. With the Manage sprints permission, permissions are now checked against the filter query of the origin board — the board from which the sprint is created — not just against the issues within the sprint. In case of issues, admins need to identify the origin board to investigate why a user cannot complete a sprint for example.
Another situation that requires investigation is, if the filter query for a sprint is complex (several clauses) it requires the filter either be simplified or the user must have the manage sprints permission for all projects in the instance not just associated projects with the filter. This can cause problems managing a sprint if it exist in several boards as there isn't an easy way via the UI to identify origin board the sprint was created on to resolve the issue.
See Use manage sprints permission for advanced cases for more details.
Suggested Solution
Provide a UI method that will show the origin board of sprint to resolve the complex query issue.
Workaround
- Please contact support.atlassian.com
- duplicates
-
- Gathering Interest
- was split from
-
- Gathering Interest
[JRACLOUD-91025] Provide UI method to identify origin board for a sprint
| Component/s | Original: Board (Company) - Active Sprints [ 60792 ] | |
| Component/s | New: Board - Sprints [ 78002 ] | |
| Key |
Original:
|
New:
|
| Project | Original: Jira Cloud [ 18511 ] | New: Jira Platform Cloud [ 18514 ] |
| Workflow | Original: JAC Suggestion Workflow JSWCLOUD [ 4274848 ] | New: JAC Suggestion Workflow 3 [ 4373802 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Link | New: This issue duplicates JSWCLOUD-13265 [ JSWCLOUD-13265 ] |
| Description |
Original:
h3. Problem Definition
The *Manage sprints* permission introduces the "origin board concept for sprint" which is important to identify who can complete a sprint. With the *Manage sprints* permission, permissions are now checked against the filter query of the _*origin board*_ — the board from which the sprint is created — not just against the issues within the sprint. In this case, admins need to identify the origin board to investigate why a user cannot complete a sprint for example. Another situation that requires investigation is, if the filter query for a sprint is complex (several clauses) it requires the filter either be simplified or the user must have the manage sprints permission for all projects in the instance not just associated projects with the filter. This can cause problems managing a sprint if it exist in several boards as there isn't an easy way via the UI to identify origin board the sprint was created on to resolve the issue. See [Use manage sprints permission for advanced cases|https://support.atlassian.com/jira-cloud-administration/docs/use-manage-sprints-permission-for-advanced-cases/] for more details. h3. Suggested Solution Provide a UI method that will show the origin board of sprint to resolve the complex query issue. h3. Workaround - Please contact support.atlassian.com |
New:
h3. Problem Definition
The *Manage sprints* permission introduces the "origin board concept for sprint" which is important to identify who can complete a sprint. With the *Manage sprints* permission, permissions are now checked against the filter query of the _*origin board*_ — the board from which the sprint is created — not just against the issues within the sprint. In case of issues, admins need to identify the origin board to investigate why a user cannot complete a sprint for example. Another situation that requires investigation is, if the filter query for a sprint is complex (several clauses) it requires the filter either be simplified or the user must have the manage sprints permission for all projects in the instance not just associated projects with the filter. This can cause problems managing a sprint if it exist in several boards as there isn't an easy way via the UI to identify origin board the sprint was created on to resolve the issue. See [Use manage sprints permission for advanced cases|https://support.atlassian.com/jira-cloud-administration/docs/use-manage-sprints-permission-for-advanced-cases/] for more details. h3. Suggested Solution Provide a UI method that will show the origin board of sprint to resolve the complex query issue. h3. Workaround - Please contact support.atlassian.com |
| Link | New: This issue was split from JSWSERVER-13265 [ JSWSERVER-13265 ] |