I suspect there might be a bug in this migration process.
My teams have reported that Zombie Epics have started to surface in their backlogs in the last week or so.
It looks like the value for Epic Status has stayed as it was (value set to Done)
Someone in our team has added some statuses (good old fashioned statuses for workflows) in this time
Somehow, those statuses have been appended to the array of values for Epic Status
This has triggered all the Epics, still with Epic Status set to Done, to resurface in the backlog Epics panel, and giving the user the option to Mark as Done to remove the Epic from the backlog. It appears now that Mark as Done changes the Epic Status to the last value in the array of available values for Epic Status
I'm a Site Admin for our Jira instance and our audit log doesn't show any configuration change to Epic Status, and I do not have the ability to revert the configuration of the statuses back to the simple trio of To do, In progress and Done.
I always found two fields: Epic Name and Summary very useful. We use Jira Advanced Roadmaps to share/coordinate our work across the organization. It is nice to have a long/more descriptive Epic Summary to show here. But for team use, on Epics Panel, it's better to have a short/crisp Epic Name which makes the board cleaner. :(
Thanks for your feature suggestions @Karlon Auger and @Walter Buggenhout we'll keep these in mind when we prioritise our future projects to improve Jira.
While you work on the epics displaying options, is there a way to align these two "Epic status views"? I find it confusing that they differ so much.
A) In the backlog epic panel I usually see this view, telling me "100% of estimated work done (5 of 5 Story Points)": Why is it blue colored if its "Done" (and not green)?
B) When I look at the same epic in the "View Epic details" view, it looks like that (below). I can see that there are 10 issues in this epic, 3 are in Done, 1 in Progress, and the remaining 6 have not been started yet or are still in "To do", etc.
The lower view contains much more relevant details and I´d like this view to be displayed in the Backlog epic panel instead of the upper one.
@Rohan Swami1 My teams are definitely excited for changes in this space, but I have a few questions as we plan for them- specifically around the epic name -> issue summary change. The lack of distinction between the purpose of the two fields causes confusion but many of my teams have made the best of it and now have distinct reasons for what they put in the epic name and the issue summary fields.
1) Do we have any option to not take this particular change?
2) Would we be able to add, through board settings, the epic name as an additional field on the card layout for the active board and backlog views after the issue summary starts appearing in the lozenge?
3) Is there a user benefit statement I can share with them other than it better aligns company managed and team managed projects? We don't currently use team managed projects.
What is the character limit for the parent lozenges displayed on issues?
The article answers my question " If you’re updating your issue summaries, keep in mind that the names displayed on the board and backlog have a max character limit (19) "
@Rohan Swami Currently, to link a story to an Epic using Epic Link, you need the project "Edit Issues" permission on the project where the parent Epic resides. Conversely, when linking an Epic to a higher level (e.g. Initiative) using Parent Link, you do not need the project "Edit Issues" permission on the parent.
Will these changes remove the need for the Edit Issues permission on the epic Parent? This would be helpful for some of our clients, who wish to lock down editing on epics, but still allow teams to link to those epics.
Hi @Rohan Swami - I was testing the Epic status → Issue Status Category changes and I'm noticing that it still displays the Epic in the Backlog EPICS Panel even though the Epic is in a Done status and all of its child tickets are in a Done status. Am I missing something? :) ...is anyone else experiencing this?
Atlassian Team members are employees working across the company in a wide variety of roles.
July 5, 2022 edited
@Mark Thompson we'll get that uploaded as a Community blog shortly as well which will have comment functionality. Please feel free to create a support request as well if you have specific concerns we can help with.
Hi @Rohan Swami and Happy New Year! I have a few people asking for updates on timing of the Epic field sunsetting / converting to 'parent' - any new news you can share?
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Thanks for this @Rohan Swami1 - please advise when this will be rolled out on our instance. I just went to have a look and see that the Epic Name is still used on board labels for instance. I would like to make sure we know when this is rolled out to us. Thank you
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
228 comments