I know a few people are saying they were contacted about the change but we are still very new to Jira and this was not something we were aware of. We now have the issue that the name exported to one of our other systems now doesn't match. I don't understand why you would use summary. The name was easy to see on a backlog and the summary is a long explanation of what the Epic is (or at least that is how we were using it). Not a great change in my mind.
I agree with Chris that the having the Epic is all uppercase hurts readability. I also prefer descriptive Epic short names, and I feel like the width of the Epic pillbox displayed in the backlog is way too small. Can we get a setting to specify the pixel width for that pillbox in the board settings please, or a column width that each individual user can drag to set this based on their screen size?
I'll add to the general sentiment here that this change has made a mess of our boards. Our teams preferred the previous use of Epic Name and have used that extensively. Since it seems unlikely that the change will be rolled back, can there be a configuration option to use the Epic Name rather than the Summary on the boards and other places?
Many of us use a shorter epic name specifically for labels, and a longer label in the summary. This change causes a usability issue and readability issue, especially when combined with the label text formatting. The characters are truncated sooner.
Why all-caps? Again, this contributes to the usability/readability issue.
Minimally, there should be options to use the Epic Name value again, and to use better formatting for the label.
How exactly was this change billed as an "improvement"? What improved? Was that more valuable compared to what we lost in usability?
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.
returns a lot of results. However, the field Epic Link still appears on my story screen, and Parent won't even if I manually add it. Can someone clarify how this works? Do I still put in values for Epic Link, but they get copied to Parent? Or should I be removing Epic Link from screens and replacing it with Parent?
I don't understand the point of keeping the Epic Name available, if it won't be used on the board if it's filled in. Its purpose was to allow for a prettier label on boards. I have to say it didn't click with me the implications of this change because of that.
Why not make the Epic Status optional? And/or provide a 'Status' custom field type that can be displayed as the tag in agile boards and backlogs? And/or allow the use of labels or component tags instead?
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.
What do people think of improved change management on improvements like this?
Specifically, perhaps outline the changes in a table format, with or without target dates, the last-updated-date for information, and indicate progress periodically. That will certainly help the community of users to know when something is broken, "rolling out", or "functions as designed".
In the backlog view, the lozenge used to show a short name, which could be a cryptic tag; a descriptive summary does not fit in the lozenge. The BEFORE/AFTER pictures do not reflect that the summary now will be limited to only part of a truly descriptive epic. Try viewing the backlog with an epic named and summarized something like:
Epic names were very useful for displaying as a badge in list of issues and scrum boards. I want to have a human readable epic summary and a very short epic name so that it fits the badge size. What I have now is not manageable truncated text which is really frustrating.
Epic name is now optional, so far so good, however when it is empty it breaks what is being displayed in reports (e.g. version report). Is anyone else experiencing this and knows if there is a fix short of filling in the optional epic name?
Question - This seems to have rolled out to me. FYI for others - automation rules look like they need to be manually updated.
When is Atlassian going to allow deleting the old Epic Link field? Right now it seems like it will have to be manually removed. It's a deprecated field so we should be allowed to delete it.
I'm not crazy about these changes, preferring to keep the distinction between parent issues and epics. If anything I would instead like to be able to see the epic that a subtask's parent belongs to (in addition to that parent)!
But, taking the changes as a given, my issue is that the color-coding and wrapping of the epic names has been lost when searching issues.
IMHO these changes have negatively influenced the usefulness of JIRA, one of the most notorious being epics previously marked as done have resurrected themselves and admittedly not a JIRA expert have been unable to find a way now of working out what epics were marked as done. A complete mess for established users.
The usage of the description field as a name when there was already a name field made a whole bunch of epics meaningless in my case as people has put "tasks related to this project" or similar in multiple description but at least the name field was still there and could be copied/pasted to "fix" the mess created. Displaying them in all caps reduced the amount of the name displayed in places where it is most important and is also a legibility issue.
I'm somewhat "stuck" with having to use JIRA at least once every other week but day to day I've reverted back to pen and paper and crossing off tasks so that I can avoid the system as much as possible.
I welcome all changes, except for the Epic name -> Issue Summary switch. This is simply not helping anyone. We just switched to the cloud version and now have to work with 1 field to search for epics as well as display them on the issues cards on the board. These two usecases do not always require the same field. Our cards are now not readable at first sight anymore with a simple Epic Name. We cannot keep it simple anymore because then we cannot do a detailed search for it since most fields in Jira are not searchable besides exporting things to excel. Please at least give us the option to choose what we display on an issue card. Thanks.
228 comments