Provide UI method to identify origin board for a sprint.

Problem Definition

Sprints can now be affected by complex filters on the origin board if the filter is too complex. The manage sprints permission introduces the "origin board concept for sprint". 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 blog post Updates on the planned second release of sprint management permission and Sprints shared between multiple boards for reference.

Suggested Solution

• Provide a UI method that will show the origin board of sprint to resolve the complex query issue.
• When showing the sprints on a board that is not their origin board, it would be great to have the additional feature below:
  • indicate that the sprint is shared with its origin board
  • allow copying the sprint locally to stop sharing it
  • indicate/warn that the changes in the shared sprint's attributes affect the same sprint on the other boards
  • allow marking the sprints as allowed to be shared or not and treat the act of sharing a sprint as an error or not accordingly.
• Log the sprint attribute's changes in :
  • atlassian-jira log
  • the JIRA audit log
• Log the board filter changes in :
  • atlassian-jira log
  • the JIRA audit log

Workaround

• Cloud users:
  Please contact support.atlassian.com
• Server users:
  Please contact your Database administrator for your JIRA DB to execute the following query to find the origin board for a sprint:

  select b."ID", b."NAME" as board_name, s."NAME" as sprint_Name from "AO_60DB71_SPRINT" s, "AO_60DB71_RAPIDVIEW" b where s."NAME" = '<SprintName>' and s."RAPID_VIEW_ID" = b."ID";
  

  The above SQL was written for Postgres. Syntax for the query may need to be adjusted for your DB engine.