Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-8031

Program Board - Features not visible in program board due to Anchor Sprint Deletion

XMLWordPrintable

    • 5
    • Severity 3 - Minor
    • No

      Issue Summary

       

      After Delete and re-adde anchor sprints in a Program Increment, synced scrum boards are showing as "not generated" despite the Features and Stories appearing to have the correct sprints. Attempts to resync using various methods have not resolved the issue, resulting in Features not displaying in the correct sprints on the boards, with some remaining in the unassigned backlog.

      This is reproducible on Data Center: (yes) 

      Steps to Reproduce

      1. create PI
      2. create Sprints
      3. create Feature
      4. create Stories
      5. assign Stories to sprints
      6. assign Feature to Anchor date
      7. delete Anchor date of Feature
      8.  

      Expected Results

      The Feature are not supposed to be removed from Program Board

      Actual Results

      The features were removed from the Program Board

      ...

      Workaround

      • Clean up old data
        • delete the sprints that were made orphan of PI if they still exist
      • for the children Stories, remove them from the Team
      • for the children Stories, remove them from Sprint
      • create the new anchors and Sprints if needed
      • add the children's Stories to the correct Team and Sprint
      • Stories should be visible once again on Program Board to be added to the right Sprint

          Form Name

            [JIRAALIGN-8031] Program Board - Features not visible in program board due to Anchor Sprint Deletion

            Mary Heather Cox added a comment -

            awww no!  My screenshots didn't take!

            Mary Heather Cox added a comment - awww no!  My screenshots didn't take!

            Mary Heather Cox added a comment -

            The recovery for this is as follows:

            1. Ask Atlassian to check for Feature's Team Target Completion Sprint having NULL values.  If they have null values, ask Atlassian to clear the NULL values.
            2. Recreate the correct anchor sprints via the PI
              1. Name the sprints differently than the deleted sprints
              2. Name the short name differently than the deleted sprints
            3. Using Atlassian Analytics determine the IDs for the deleted sprints and the IDs.  I did this by looking at Feature History:
            4. Once you have the deleted anchor IDs and the newly created IDs you can identify each sprint that needs deleted in the next step, using Atlassian Analytics, scope to the PI ID and the anchor sprint ID of the first anchor you just created. 
            6. In JA/Items/Sprints - Delete all sprints that were synced to the deleted anchors.  This includes sprints in Development and Closed. You will need to Unlock, set back to In Planning,  then Delete them. <be SURE to toggle off the bidirectional sync in Jira Setting/Jira Setup per Atlassian 11.9.x release notes indicate. If you fail to do this, the stories in Jira that have impacted sprints on them, will lose their sprint value>.  What this does is break the mapping of the Jira Sprint, to the JA Sprint, to the JA anchor sprint.  This delete and sync will reset that mapping.
              1.  On Jira Settings/Jira Integration - run integration on the impacted Projects with the query of sprint in( * ) where * is the Jira Sprint IDs and set the board sync to Yes with the related Jira Board Name..  Execute the Integration in small-ish batches.
              2. Once you finish that small batch, take the list of sprint IDs you used for integration and write a JQL in Jira to identify all related Jira items.  Bulk change all by adding a label. This forces the stories to sync back to JA with the Jira sprint value, which should now be correctly mapped to the new anchors.
            7. Using Atlassian Analytics, identify impacted Objectives, Dependencies, and Features
              1. For Objectives:
            8. For Dependencies,
            9. For Features
            10. Once you've identified the Objectives, Dependencies, and Features, you will manually update them with the new anchor sprint values.
              1. For Features this means you'll need to update Target Start Sprint and Target End Sprint values using the audit log/feature history from the last Atlassian Analytics chart. I exported to excel and created a vlookup to map the old anchor values to the new anchor values.
              2. From the Program Board, at this point, you should see all of the Features for the PI in the unplanned sprint column.  What plots the pucks into the correct anchor sprint column is the Target Team Completion Sprint value - only accessible by clicking on the puck to access the Quick View and updating there, by looking at the sprint values of all of the stories in the Feature and using the max value to populate that value.
            11. As you repair items, rerun the Atlassian charts you made and you should see the number of items shrinking.

            BE SURE to sync in small batches. There is a bug that will hang the sync and remove the ability to integrate, map states, and filter items.

            This is what worked for me.  Use at your own risk.

            Best of all, remove the ability for any role to delete anchors for all roles except admin.  

             

             

             

             

             

             

             

             

             

            Mary Heather Cox added a comment - The recovery for this is as follows: Ask Atlassian to check for Feature's Team Target Completion Sprint having NULL values.  If they have null values, ask Atlassian to clear the NULL values. Recreate the correct anchor sprints via the PI Name the sprints differently than the deleted sprints Name the short name differently than the deleted sprints Using Atlassian Analytics determine the IDs for the deleted sprints and the IDs.  I did this by looking at Feature History: Once you have the deleted anchor IDs and the newly created IDs you can identify each sprint that needs deleted in the next step, using Atlassian Analytics, scope to the PI ID and the anchor sprint ID of the first anchor you just created.  In JA/Items/Sprints - Delete all sprints that were synced to the deleted anchors.  This includes sprints in Development and Closed. You will need to Unlock, set back to In Planning,  then Delete them. <be  SURE to toggle off the bidirectional sync in Jira Setting/Jira Setup per Atlassian 11.9.x release notes indicate. If you fail to do this, the stories in Jira that have impacted sprints on them, will lose their sprint value>.  What this does is break the mapping of the Jira Sprint, to the JA Sprint, to the JA anchor sprint.  This delete and sync will reset that mapping.  On Jira Settings/Jira Integration - run integration on the impacted Projects with the query of sprint in( * ) where * is the Jira Sprint IDs and set the board sync to Yes with the related Jira Board Name..  Execute the Integration in small-ish batches. Once you finish that small batch, take the list of sprint IDs you used for integration and write a JQL in Jira to identify all related Jira items.  Bulk change all by adding a label. This forces the stories to sync back to JA with the Jira sprint value, which should now be correctly mapped to the new anchors. Using Atlassian Analytics, identify impacted Objectives, Dependencies, and Features For Objectives: For Dependencies, For Features Once you've identified the Objectives, Dependencies, and Features, you will manually update them with the new anchor sprint values. For Features this means you'll need to update Target Start Sprint and Target End Sprint values using the audit log/feature history from the last Atlassian Analytics chart. I exported to excel and created a vlookup to map the old anchor values to the new anchor values. From the Program Board, at this point, you should see all of the Features for the PI in the unplanned sprint column.  What plots the pucks into the correct anchor sprint column is the Target Team Completion Sprint value - only accessible by clicking on the puck to access the Quick View and updating there, by looking at the sprint values of all of the stories in the Feature and using the max value to populate that value. As you repair items, rerun the Atlassian charts you made and you should see the number of items shrinking. BE SURE to sync in small batches. There is a bug that will hang the sync and remove the ability to integrate, map states, and filter items. This is what worked for me.  Use at your own risk. Best of all, remove the ability for any role to delete anchors for all roles except admin.                    

              9430c2193c41 Bhanu Vanjaku
              f58471712ff6 Victor Fragoso
              Affected customers:
              4 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated: