-
Bug
-
Resolution: Fixed
-
High
-
6
-
Severity 3 - Minor
-
1
-
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
- In my test instance, I have changed the Level 1 Issue Type Hierarchy name to 'Feature', instead of Epic.
- 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.
- 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
-
- relates to
-
JRACLOUD-80492 Add the ability to create multiple Epic issue type in JIRA Software
- Closed
- mentioned in
-
Page Failed to load
Form Name |
---|
Epic Panel and Backlog dropdown will incorrectly be renamed in case customers rename their #1 Issue Type Hierarchy could leading customers to confusion
-
Bug
-
Resolution: Fixed
-
High
-
6
-
Severity 3 - Minor
-
1
-
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
- In my test instance, I have changed the Level 1 Issue Type Hierarchy name to 'Feature', instead of Epic.
- 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.
- 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
-
- relates to
-
JRACLOUD-80492 Add the ability to create multiple Epic issue type in JIRA Software
- Closed
- mentioned in
-
Page Loading...