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

After a Board Is Deleted, Related Sprints Remain Active

XMLWordPrintable

      NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.

      When a JIRA Agile board is deleted, all sprints that are active on it cannot be deleted nor can reports from them be viewed.

      Steps to reproduce:

      1. Create a new Scrum Board
      2. Create a sprint on the board and add issues.
      3. Start the sprint.
      4. Delete the board.
      5. Sprint stays active and cannot be ended and report page is blank.
        Active sprints from deleted boards are still displayed in the 'Sprint' field suggestions too, which may be confusing for the users.

      Expected behaviour
      When a user attempts to delete a board, show a notification about the active sprints and let them choose to either complete or remove the sprints, or keep them active.

      Workaround

      1. If there are issues associated with the sprints:
        • Create a new board.
        • Associate the filter of deleted board to new board.
        • You can now end sprint from this board.
      2. If there are no issues associated with the affected sprints:
        • Create a test project
        • Show sprint field on the field configuration of the test project
        • Create new issue, associate with this new issue
        • Create new board
        • Associate test project with the board
        • Now you can end the sprint from this board

      Although you can manually update the table to remove the board, but it is not recommended.
      the sprints will need to be deleted with a manual update of the "AO_60DB71_SPRINT" table.

      This sprint was showing up because it wasn't marked as closed, but the board it was on had been deleted.

      jira=# select * from "AO_60DB71_SPRINT";
 CLOSED | COMPLETE_DATE |   END_DATE    | ID |     NAME      | RAPID_VIEW_ID | STARTED |  START_DATE
--------+---------------+---------------+----+---------------+---------------+---------+---------------
 t      | 1393896023571 | 1393894020000 |  2 | Sprint 0      |             3 | t       | 1392079630319
 t      | 1397593903516 | 1394351160000 |  3 | Sprint 1      |             3 | t       | 1393919198734
 t      | 1397594141661 | 1397593980000 |  4 | Sprint 2      |             3 | t       | 1396384385510
 t      | 1399057753082 | 1398712020000 |  5 | Sprint 3      |             3 | t       | 1398107259097
 f      |               | 1399662840000 |  6 | Sprint 4      |             3 | t       | 1398798867723
 t      | 1410895731347 | 1393276980000 |  1 | Week 2 - 2/14 |             1 | t       | 1392067397490
 f      |               | 1411369140000 |  8 | Sprint 1      |             4 | t       | 1410159606021
(7 rows)

jira=# select * from "AO_60DB71_RAPIDVIEW";
 CARD_COLOR_STRATEGY | ID |     NAME      | OWNER_USER_NAME | SAVED_FILTER_ID | SPRINTS_ENABLED | SPRINT_MARKERS_MIGRATED | SWIMLANE_STRATEGY
---------------------+----+---------------+-----------------+-----------------+-----------------+-------------------------+-------------------
 issuetype           |  1 | February 2014 | ted             |           10000 | t               | t                       | parentChild
 issuetype           |  2 | Operations    | aaron           |           10100 | f               | t                       | custom
 issuetype           |  4 | RevUp         | aaron           |           10200 | t               | t                       | parentChild
 issuetype           |  6 | Data          | aaron           |           10400 | t               | t                       | parentChild
 issuetype           |  8 | RevUp2        | msteffeck       |           10500 | t               | t                       | custom
(5 rows)

      I created a new rapid board, and edited the "RAPID_VIEW_ID" line from that sprint to the new board id (11).

      jira=# update "AO_60DB71_SPRINT" set "RAPID_VIEW_ID" = 11 where "ID" = 6;
UPDATE 1

jira=# select * from "AO_60DB71_SPRINT" where "ID" = 6;
 CLOSED | COMPLETE_DATE |   END_DATE    | ID |   NAME   | RAPID_VIEW_ID | STARTED |  START_DATE
--------+---------------+---------------+----+----------+---------------+---------+---------------
 f      |               | 1399662840000 |  6 | Sprint 4 |            11 | t       | 1398798867723
(1 row)

      This showed the sprint "Sprint 4" in the test board I created and allowed me to close it off. I did some tests on another instances and indeed, deleting a board while a sprint is active will leave the sprint orphaned.

          Form Name

            [JSWSERVER-11263] After a Board Is Deleted, Related Sprints Remain Active

            Brian Hanrahan added a comment -

            Orphaned data of any type is really obnoxious. It seems it would be super easy to add the option to select any active sprint from any (or no assigned) board.

            Ziko's solution worked for me as well, but it's 15 minutes of my life I'll never get back.

             

            Brian Hanrahan added a comment - Orphaned data of any type is really obnoxious. It seems it would be super easy to add the option to select any active sprint from any (or no assigned) board. Ziko's solution worked for me as well, but it's 15 minutes of my life I'll never get back.  

            Michal Karpinski added a comment -

            I encountered this issue recently. I used workaround mentioned by Ziko Rajabali

            Michal Karpinski added a comment - I encountered this issue recently. I used workaround mentioned by Ziko Rajabali

            Ziko Rajabali added a comment -

            I found an alternative approach that worked for me, at least in my JIRA Agile Cloud instance. Hopefully it works for others as well.
            1) Create a Filter that gets all issues across all projects
            2) Create a Board based on the filter from step 1
            3) Create a random Issue, and associate it with the Sprint that you want to delete
            4) The orphaned / unavailable Sprint now shows up in the Board from step 2
            5) Delete the Sprint (if it is in planning) or Close the Sprint (if it is already active)

            Ziko Rajabali added a comment - I found an alternative approach that worked for me, at least in my JIRA Agile Cloud instance. Hopefully it works for others as well. 1) Create a Filter that gets all issues across all projects 2) Create a Board based on the filter from step 1 3) Create a random Issue, and associate it with the Sprint that you want to delete 4) The orphaned / unavailable Sprint now shows up in the Board from step 2 5) Delete the Sprint (if it is in planning) or Close the Sprint (if it is already active)

              b6cf9181bff6 Krystian M
              jrobison1 JordanA
              Affected customers:
              44 This affects my team
              Watchers:
              52 Start watching this issue

                Created:
                Updated:
                Resolved: