Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-90585

Epic Panel and Backlog dropdown will incorrectly be renamed in case customers rename their #1 Issue Type Hierarchy could leading customers to confusion

      Issue Summary

      The Epic Panel in your Board's backlog will only display the original Epic Issue Type (typically with Issue Type ID 10000 - which now could be renamed to any other Issue Type name), and that could lead customers to confusion as the 'Epic Panel' will be renamed to the Level 1 Issue Type Hierarchy name.

      Let's assume I change my 'Epic' Issue Type Hierarchy (#1) to 'Feature'. This will be reflected in the Epic Panel, which now will show 'Feature' instead of 'Epic', however, the 'Epic Panel' will only display 'Epic' issue type, regardless if there are any other issue types on the same hierarchy. 

      The same behavior happens with the 'Epic' dropdown that filters for Epic in your backlog. This feature is currently filtering for Epics, however, it is also incorrectly renamed.

       

      Steps to Reproduce

      1. In my test instance, I have changed the Level 1 Issue Type Hierarchy name to 'Feature', instead of Epic.
      2. Every reference in my Backlog was changed from 'Epic' to 'Feature'. However, for 'Epic Panel' that should not be reflected as this only displays the standard 'Epic' Issue Type.

         
      3. Now, if I add another Issue Type in my Level 1 Issue Type Hierarchy, these Issue Types won't be displayed on this Epic Panel.

      Expected Results

      All Issue Types from that #1 Issue Type Hierarchy should show up on the 'Epic Panel'.

      Actual Results

      Only Epics will be shown on the Epic Panel, regardless if they changed the original Epic name to another Issue Type.

      Workaround

      -

            [JRACLOUD-90585] Epic Panel and Backlog dropdown will incorrectly be renamed in case customers rename their #1 Issue Type Hierarchy could leading customers to confusion

            Vu Le added a comment -

            Hi all, with CLOUD-25522 fixed, the epic panel and dropdown should display all L1 issues for the majority of customers. We will close this bug ticket.

            Vu Le added a comment - Hi all, with CLOUD-25522 fixed, the epic panel and dropdown should display all L1 issues for the majority of customers. We will close this bug ticket.

            Kevin Cai added a comment -

            Hi 750c3ee75cc3,

            We're currently working to support all Level 1 Issue Types in the epic panel and backlog dropdown as part of this public bug ticket: https://jira.atlassian.com/browse/JSWCLOUD-25522 which will align the name of the epic panel/backlog dropdown with the actual user experience. If you'd like updates on this work feel free to keep an eye on the mentioned bug ticket!

            Cheers,

            Kevin

            Kevin Cai added a comment - Hi 750c3ee75cc3 , We're currently working to support all Level 1 Issue Types in the epic panel and backlog dropdown as part of this public bug ticket: https://jira.atlassian.com/browse/JSWCLOUD-25522 which will align the name of the epic panel/backlog dropdown with the actual user experience. If you'd like updates on this work feel free to keep an eye on the mentioned bug ticket! Cheers, Kevin

            Hello 7bd5bc3e63c1 any news about this bug, when can we expect a fix. Thanks in advance for your feedback 

            Andreas Beham added a comment - Hello 7bd5bc3e63c1 any news about this bug, when can we expect a fix. Thanks in advance for your feedback 

              vle2@atlassian.com Vu Le
              fb70dbb86db0 Antonio Carlos
              Affected customers:
              3 This affects my team
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: