Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-21236

Sprint appears in REST API but not in UI when only subtask matches board filter

      Issue Summary

      Sprints can show up on multiple boards and that's expected.

      When only the subtaks of a sprint match another board's filter, though, that sprint doesn't show up in the UI, but shows in the API endpoint /rest/agile/1.0/board/{boardId}/sprint

      Steps to Reproduce

      1. Create two boards with mutually exclusive filters. For example, one filters the Fix Version 2.0 and the other, 3.0
      2. Create a sprint "2.0 Sprint 1"
      3. Add a Story with a subtask to it
      4. Change the subtask version to 3.0
      5. Check the board for version 3.0
      6. Run the REST API call to board to version 3.0

      Expected Results

      The REST API sprints are consistent with the UI.

      Actual Results

      The REST API shows "2.0 Sprint 1", but the UI doesn't.

      Workaround

      Search for the subtasks in the sprint and make the appropriate changes so they don't show up in the other board.
      This could involve either editing the subtasks or the board filter.

          Form Name

            [JSWSERVER-21236] Sprint appears in REST API but not in UI when only subtask matches board filter

            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2
            Stasiu made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 674945 ]

            This issue is also happening when issue is in Epic, not only subtask as suggested by the description.

            Possible (though not very user friendly) workaround is that loading the sprints via REST API for the user will make the missing sprints again visible.

            This is one quite significant for us - our teams share same sprint, however they have each separate board + some general board for all teams.

            Milan Å turcel added a comment - This issue is also happening when issue is in Epic, not only subtask as suggested by the description. Possible (though not very user friendly) workaround is that loading the sprints via REST API for the user will make the missing sprints again visible. This is one quite significant for us - our teams share same sprint, however they have each separate board + some general board for all teams.
            Marcin Sasinowski made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Bugfix Automation Bot made changes -
            Support reference count New: 1
            Bugfix Automation Bot made changes -
            Introduced in Version New: 8.2
            Allan Gandelman created issue -

              Unassigned Unassigned
              5fb7769fcbc7 Allan Gandelman
              Affected customers:
              2 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated: