Uploaded image for project: 'Jira Software Server and Data Center'
  1. Jira Software Server and Data Center
  2. JSWSERVER-13265

Provide UI method to identify origin board for a sprint.



    • 97
    • 39
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.


      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.


      • 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.


        Issue Links



              Unassigned Unassigned
              jcastro Jose Castro (Inactive)
              117 Vote for this issue
              52 Start watching this issue