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

Multiple fix versions are no longer displayed on Advanced Roadmap plans

XMLWordPrintable

      Issue Summary

      In the older Live Plans an issue with multiple fix versions would show them in the Live Plan, for example:

      However, in the new interface only one fix version is displayed even when there are multiple:

      This is reproducible on Data Center: Yes

      Steps to Reproduce

      1. Create new Advanced Road Map plan
      2. Assign multiple fix versions to an issue in Jira
      3. View issue from Advanced Road map plan

      Expected Results

      Multiple fix versions are displayed as they were in Live Plans

      Actual Results

      Only one fix version is displayed

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

        1. 2022-09-26_7-18-40_2022-09-26T14 32 49.301Z.png
          80 kB
          Jeff Curry
        2. Issue release column display in the plan_2022-09-09T19 15 58.857181Z.png
          20 kB
          Jeff Curry
        3. Actual Issue View display of mult-version association_2022-09-09T19 16 00.332168Z.png
          28 kB
          Jeff Curry
        4. Screen Shot 2022-10-14 at 11.23.17 am-1.png
          65 kB
          Sachithra Dangalla
        5. Screen Shot 2022-10-14 at 11.23.17 am.png
          65 kB
          Sachithra Dangalla

            [JSWSERVER-24947] Multiple fix versions are no longer displayed on Advanced Roadmap plans

            Brady McIntosh added a comment -

            Please add affects versions 9.9.1 and 9.12.1 (at least). This is still a problem for us.

            Brady McIntosh added a comment - Please add affects versions 9.9.1 and 9.12.1 (at least). This is still a problem for us.

            Aakrity Tibrewal added a comment -

            Dear all,

            I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
            Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

            Sincerely,
            Aakrity Tibrewal
            Jira DC

            Aakrity Tibrewal added a comment - Dear all, I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged. Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments. Sincerely, Aakrity Tibrewal Jira DC

            Roi Fine (Inactive) added a comment -

            Hi Joseph,

             
            I'm a Product Manager for Advanced Roadmaps. Closing duplicate tickets is a standard protocol for us. It doesn’t mean we won’t look at it in the future. You can add yourself as a watcher to the original ticket linked to this ticket. I am sorry that this issue has been causing frustration for quite a while. Unfortunately, we won't fix this issue in the next 12 months (at least) as we have higher priorities in our cloud offering. We apologize for the inconvenience. 
             
            Roi Fine 

            Roi Fine (Inactive) added a comment - Hi Joseph,   I'm a Product Manager for Advanced Roadmaps. Closing duplicate tickets is a standard protocol for us. It doesn’t mean we won’t look at it in the future. You can add yourself as a watcher to the original ticket linked to this ticket. I am sorry that this issue has been causing frustration for quite a while. Unfortunately, we won't fix this issue in the next 12 months (at least) as we have higher priorities in our cloud offering. We apologize for the inconvenience.    Roi Fine 

            Joseph Chung Yin added a comment -

            Hi Mariya:

             

            Since you closed out this case (reported yesterday by Atlassian Support Team) because it is a duplicate of an existing case.  I visited the old case and the old case (created back in 2017?) still have no solution?  This is not acceptable.

            Either you reopen the case or provide solution.

            Best, Joseph

            Joseph Chung Yin added a comment - Hi Mariya:   Since you closed out this case (reported yesterday by Atlassian Support Team) because it is a duplicate of an existing case.  I visited the old case and the old case (created back in 2017?) still have no solution?  This is not acceptable. Either you reopen the case or provide solution. Best, Joseph

            Mariya Shmalko added a comment -

            This is a duplicate of this existing JAC ticket: https://jira.atlassian.com/browse/JPOSERVER-1931 

            Mariya Shmalko added a comment - This is a duplicate of this existing JAC ticket: https://jira.atlassian.com/browse/JPOSERVER-1931  

              Unassigned Unassigned
              jcurry Jeff Curry
              Affected customers:
              19 This affects my team
              Watchers:
              25 Start watching this issue

                Created:
                Updated: