-
Suggestion
-
Resolution: Unresolved
-
2
-
4
-
Issue Summary
After the changes to Epic related fields the Epic name one now reflects the Epic's Summary.
The Epics' children issues will display their respective parent Epic's label on their cards which shows the Epic's Summary.
Currently the Epics are also displaying their own Epic name labels on their cards. Conceptually that does not make much sense and creates duplicated information in the cards since the Summary is basically displayed twice:
- The Epic's Summary is Lumi Epic
- It also displays its own Epic name label, making the information duplicated and irrelevant for users
Steps to Reproduce
- Create an Epic
- Create a Kanban board and make sure that Epic is displayed on it
Expected Results
Only the children issues of the Epic will contain the Epic name label.
Actual Results
The Epics display their own Epic name labels as well.
Workaround
None at the moment.
Update - October 9th/2024
This will affect any issue type that's on the Epic level within the hierarchy.
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-86948] Epic name label displayed on Epic level cards in board view
Not making explicit changes to correct this behaviour - will be dealt with by UIF.
As discussed in this thread https://atlassian.slack.com/archives/CFGQDM81H/p1688441430020069 - this behaviour is an outcome of deprecating the epic name field.
The customer has been given context and the upcoming UIF rollout will clean up inconsistent behaviour. Nothing more needed for now.
Hi all! I'm a product manager working on Jira. We'll be converting this to a suggestion ticket as currently the behaviour is expected. Although we acknowledge the experience is not the ideal experience. As pointed out above the text within the epic lozenge is no longer relevant on epic cards. The ideal experience is for us to remove the text and retain the lozenge as the colour still has meaning and can allow for the parent child relationship to be visualised across many cards. This change is currently sitting in the backlog and is something we hope to get done - but we do not have an ETA for it. There are many exciting changes being made right now across Jira but this means there are tough prioritisation calls that ensure we are delivering the highest value to the most amount of customers. We apologise for the inconvenience in the short term.
Thanks,
Eoin