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

Portfolio produces erratic behavior when epics have multiple releases assigned

      Issue Summary

      Jira Portfolio only displays 1 release per an issue, even though epic can have multiple releases assigned. The dropdown itself when expanded shows multiple releases selected, while only 1 is displayed in the control. This can cause unexpected data loss when modifying Release attribute through Portfolio.

      To add to a confusion, the Release displayed out of multiple will always be the last associated with the epic, so it might differ between epics associated with the same releases.

      Steps to Reproduce

      1. Associate multiple releases to an epic.
      2. Check Releases column through the plan - only 1 release is displayed.

      Expected Results

      Multiple releases displayed in the column.

      Actual Results

      Last associated Release is displayed.

      Workaround

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

          Form Name

            [JSWSERVER-24946] Portfolio produces erratic behavior when epics have multiple releases assigned

            Marc Dacanay made changes -
            Labels Original: Plan-Release New: Plan-Release ril
            Marc Dacanay made changes -
            Remote Link New: This issue links to "Internal ticket (Web Link)" [ 956653 ]
            SET Analytics Bot made changes -
            UIS Original: 0 New: 1
            Bugfix Automation Bot made changes -
            Introduced in Version New: 8.2
            Aakrity Tibrewal made changes -
            Component/s Original: Releases [ 58390 ]
            Component/s New: (Advanced Roadmaps) Plan - Releases / Fix Version [ 63497 ]
            Key Original: JPOSERVER-2716 New: JSWSERVER-24946
            Affects Version/s Original: 3.27.0 [ 91818 ]
            Affects Version/s Original: 3.17.0 [ 90701 ]
            Affects Version/s New: 8.20.0 [ 95694 ]
            Affects Version/s New: 8.20.0 [ 95694 ]
            Project Original: Advanced Roadmaps [ 16510 ] New: Jira Software Server and Data Center [ 12200 ]

            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
            Stasiu made changes -
            Labels New: Plan-Release
            Stasiu made changes -
            Remote Link Original: This issue links to "JPOS-5069 (Bulldog)" [ 476432 ] New: This issue links to "JPOS-5069 (JIRA Server (Bulldog))" [ 476432 ]
            SET Analytics Bot made changes -
            UIS Original: 6 New: 0
            Bugfix Automation Bot made changes -
            Support reference count Original: 1 New: 2

              Unassigned Unassigned
              apatyuchenko Andrey Patyuchenko
              Affected customers:
              4 This affects my team
              Watchers:
              13 Start watching this issue

                Created:
                Updated: