Issue Summary

      When opening the Live Roadmap view, duplicate Features may appear in the name column.

      Steps to Reproduce

      This behavior was not reproduced in our Atlassian lab instance.
      When this was reproduced the steps were:

      1. Set in the tier 1 filter a:
        1. Program or a Team
        2. Program Increment
      2. Go to Programs > Roadmap
      3. Select Work > Features (Jira Epics)
        (You can enable the 'Group by' option under the View configuration although it does not have an influence).

      Expected Results

      No duplicate features are shown in the Live Roadmap.

      Actual Results

      Duplicate features appear under the name column (within the same grouping if enabled) as shown in the images below with state grouping


      or

      Workaround

      To workaround the issue set the tier1 filter to one of the following options:

      1. use the Portfolio and the program increment instead of the Program or the Team.
      2. use only the program increment without the Program or the Team.

        1. AWS Production-1 Frankfurt query.csv
          2 kB
          Gang Liu
        2. AWS Production-1 Ohio query (1).csv
          5 kB
          Gang Liu
        3. AWS Production-1 Sydney query.csv
          0.4 kB
          Gang Liu
        4. image-2022-11-11-16-51-25-726.png
          460 kB
          Francois Panaget
        5. image-2022-11-11-17-09-13-010.png
          105 kB
          Francois Panaget
        6. image-2022-11-11-17-09-34-373.png
          105 kB
          Francois Panaget
        7. image-2022-11-11-17-10-07-440.png
          110 kB
          Francois Panaget
        8. image-2022-11-11-17-11-10-951.png
          74 kB
          Francois Panaget

            [JIRAALIGN-4558] Features are listed twice in the live Roadmap

            Don Fuller added a comment -

            A fix for this issue was delivered in 10.118.1.

            Don Fuller added a comment - A fix for this issue was delivered in 10.118.1.

            Don Fuller added a comment -

            086a04b86628 We are currently working on a fix for this issue. It has turned out to be more complicated than we originally thought. The main bug has been fixed. We are working on data integrity now to be sure after the fix has been deployed the backlog ranking is not impacted and the backlog rank will continue to show the expected rank for al work items.

            The issue is, the duplicate work item has a rank assigned, when the duplicate work item is removed from the backlog the rank is not adjusted for all other work items. For example, if items two and three in the backlog were duplicates, when item three is removed the ranking of the remaining work items are ranked 1, 2, 4.

            We are working now to ensure that after a fix for the issue is released the backlog rank works as expected and there are no gaps in the ranked work items.

            We have a fix for the duplicate ranked items and are working ensure data integrity. We expect the fix to be released within the next few weeks.

            Don Fuller added a comment - 086a04b86628 We are currently working on a fix for this issue. It has turned out to be more complicated than we originally thought. The main bug has been fixed. We are working on data integrity now to be sure after the fix has been deployed the backlog ranking is not impacted and the backlog rank will continue to show the expected rank for al work items. The issue is, the duplicate work item has a rank assigned, when the duplicate work item is removed from the backlog the rank is not adjusted for all other work items. For example, if items two and three in the backlog were duplicates, when item three is removed the ranking of the remaining work items are ranked 1, 2, 4. We are working now to ensure that after a fix for the issue is released the backlog rank works as expected and there are no gaps in the ranked work items. We have a fix for the duplicate ranked items and are working ensure data integrity. We expect the fix to be released within the next few weeks.

            Gang Liu added a comment -

            Gang Liu added a comment - https://octopus.tools.jiraalign.com/app#/Spaces-1/projects/adhock-work/operations/runbooks/Runbooks-1028/overview and results attached.

            Hello,

            This is something critical as it affects the use of Align during PI Planning. This view is used all the time

            Hina Tufail added a comment - Hello, This is something critical as it affects the use of Align during PI Planning. This view is used all the time

              dfuller@atlassian.com Don Fuller
              646db21d89d1 Francois Panaget
              Affected customers:
              3 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: