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

Roadmap Sync may fail without a correct/useful information message.

XMLWordPrintable

    • 1
    • Severity 3 - Minor
    • No

      Issue Summary

      When users try to sync, from the Roadmap, the health of a particular feature, the changes may not be propagated. Instead, a generic message without information about why the sync failed and how to fix it is thrown.

      In the backend or looking at the web browser developer, we may see that the sync was unsuccessful due to a '400 - Bad request' and again with very little information.

      This is reproducible on Data Center: yes

      Scenario 1

      Steps to Reproduce

      Pre-requisites:
      You need to have at least two Planning Increments (PI) with the same start/end dates and the same anchor dates associated with the same program.
      (for example)


      and

      Once or more Epics containing one or more Features
      All the Epics and the child Features belong to the same program and are associated with the same PI.

      1- Launch the roadmap with the Program and PI where the Epic/Features belongs
      2- Select > Work > Feature by Epic
      3- Navigate to one of the features
      4- Make sure that one of the features has its start and end date included in one of the PI anchors.
      5- Right click to change the health from (for example 'On Track' to 'Done').
      4- Click on the Sync button
      5- Leave the default options (ie. Health and 'Planning Increments/Anchor Dates')
      6- Click Sync
      The Sync is successful
      7. Go to the PI1 and delete one of the anchors that correspond to the start/end dates you see in the roadmap for one of the Features
      For example, the end date for the PI1Feature2 we see in the roadmap




      8- Go back to the roadmap
      9- Right click to change the health again.
      10- Click on the Sync button
      11- Leave the default options (ie. Health and 'Planning Increments/Anchor Dates')

      Expected Results

      The sync is successful and the Feature's Target Sprints are updated accordingly if needed.

      Actual Results

      You get the message:
      'There was an error when attempting to update the work items. If you continue to see this error, please contact the Jira Align Support team'.


      Even if you manually set the new EndDate in the Feature, the error occurs.

      Workaround

      Select option 'Target Start/Target Completion Dates' instead of 'Planning Increments/Anchor Dates' while syncing the change.

      Scenario 2

      Steps to Reproduce

      Pre-requisites:
      You need to have a Planning Increment (PI) without anchor dates.
      Once or more Epics containing one or more Features.
      All the Epics and the child Features belong to the same program and are associated with the same PI.

      1- Launch the roadmap with the Program and PI where the Epic/Features belongs
      2- Select > Work > Feature by Epic
      3- Navigate to one of the features and right-click to change the health from (for example 'On Track' to 'Done').
      4- Click on the Sync button
      5- Leave the default options (ie. Health and 'Planning Increments/Anchor Dates')
      6- Click Sync
      (As both Epic and Features are assigned to the same PI/Release which does not have any anchors, it is expected to fail.)

      Expected Results

      You get the message with a message indicating the reason for the failure such as:
      The Planning Increment assigned to the Feature is not having any anchors. Update the Planning Increment with anchors to allow this move.

      Actual Results

      You get the message:
      The parent is not assigned to the Planning Increment you are trying to assign it to. Update the parent to the Planning Increment to allow this move.

      Workaround

      Select option 'Target Start/Target Completion Dates' instead of 'Planning Increments/Anchor Dates' while syncing the change.

        1. image-2023-04-24-11-43-16-348.png
          image-2023-04-24-11-43-16-348.png
          289 kB
        2. image-2023-04-24-11-43-47-493.png
          image-2023-04-24-11-43-47-493.png
          232 kB
        3. image-2023-04-24-11-44-06-185.png
          image-2023-04-24-11-44-06-185.png
          230 kB
        4. image-2023-04-24-11-44-27-791.png
          image-2023-04-24-11-44-27-791.png
          392 kB
        5. image-2023-04-24-11-44-39-286.png
          image-2023-04-24-11-44-39-286.png
          405 kB
        6. image-2023-04-24-11-46-36-696.png
          image-2023-04-24-11-46-36-696.png
          428 kB
        7. image-2023-04-24-11-46-55-924.png
          image-2023-04-24-11-46-55-924.png
          428 kB
        8. image-2023-04-24-11-47-13-873.png
          image-2023-04-24-11-47-13-873.png
          510 kB
        9. image-2023-04-24-11-47-24-227.png
          image-2023-04-24-11-47-24-227.png
          432 kB
        10. image-2023-04-24-11-48-06-404.png
          image-2023-04-24-11-48-06-404.png
          902 kB
        11. image-2023-04-24-11-48-17-486.png
          image-2023-04-24-11-48-17-486.png
          460 kB
        12. image-2023-04-24-11-49-05-460.png
          image-2023-04-24-11-49-05-460.png
          162 kB

            dfuller@atlassian.com Don Fuller
            646db21d89d1 Francois Panaget
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: