-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
20
-
1
-
Problem Definition
Currently in JIRA Software it's possible to have multiple Epics with the same Epic Name. This is causing a number of confusions as follows:
#1 - Not possible to tell which Story belongs to which Epic from Backlog, Active Sprint, and Issue Navigator
If 2 Epics on the same board (they may belong to 2 different projects) have the same Epic Name and Color, and each has a few Stories, it's impossible to tell which Story belongs to which Epic. This applies to Backlog, Active Sprint, and Issue Navigator.
Workarounds for #1
- If possible, change the Epic Name of 1 of the Epics
- If Epic Name can't be changed for any reason, change the Color of 1 of the Epics - this can be done from Backlog and it will look like this afterwards:
Suggested Solutions for #1
- Prevent Epics from having the same name - as per
JSWSERVER-16366 - Pre-pend the issue key of an Epic to its name for labeling purpose, e.g.:
- EPIC-1 - Same Epic Name
- EPIC-2 - Same Epic Name
#2 - Exporting issues to HTML (or Excel) and CSV
Take a look at this search result:
If we export that search result to HTML (or Excel, as HTML can be opened by Excel and saved as XLSX), the exported data will look like this:
Notice that Epic Names are exported under Epic Link column
Apparently it's impossible to tell which Story belongs to which Epic
If we export that search result to CSV instead, the exported data will look like this:
Notice that issue keys of the Epics are exported under Epic Link column
Users may base on the issue keys to find the right Epics (take note that Epics and Stories must be exported together)
Workarounds for #2
- If possible/applicable, change the Epic Name of 1 of the Epics
- If you're using HTML export and expect issue key to be exported instead of Epic Name, switch to CSV export - this is for
JRASERVER-62296 - If you're using CSV export and expect Epic Name to be exported instead of issue key, switch to HTML export - this is for
JRASERVER-67146
Suggested Solutions for #2
If we can pre-pend the issue key of an Epic to its name for labeling purpose, e.g. KEY-123 - Epic Name, then use this value for Epic Link field and consistently export it regardless of HTML/CSV exports.
Notes
As per JSWSERVER-14746, users may expect that an issue should have both Epic Name and Epic Link for a search result similar to search.png, so that when issues are exported, they can see the Epic Name under Epic Name column and issue key of the Epic under Epic Link column. This is a misconception and can't be achieved because:
- Epic Name is specific to Epic issue type
- Epic Link is used by other issue types to link to an Epic issue type
So basically:
- An Epic has Epic Name but no Epic Link
- Other issue types can have an Epic Link but can never have an Epic Name
Refer to #2 above for a possible workaround.
- is incorporated by
-
- Closed
- relates to
-
JRASERVER-62251 Import epic link through CSV is no longer working
-
- Closed
-
-
- Gathering Interest
- supersedes
-
-
- Closed
-
-
-
- Closed
-
-
- Closed
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-15878] Better handle Epic Name, Epic Link, and issue exports to HTML/CSV
Hi
I am using this for seeing the hierarchy between Initiatives and Epics as set-up in Advanced roadmap. The sum-up view looks good and I can see the issue key and summary. When I export, however, all I get is the Summary field. I can't see a way to add the Issue key which is what I need for cross-referencing.
I would expect to have 2 columns in the export - "Issue Key" and "Summary".
It's of limited use as is.
Please rectify
Thanks
An update. I just found the "Key" field, so I can use this which is good and this is no longer an issue
Please implement the requested change. There is a lot of value in being able to see the name of the epic when reviewing reports. The epic issue key adds zero value as it isn't useful for reporting.
Please see this separate ticket requesting the Epic name (unique or not) be included in the CSV export and add your votes and comments.
I wouldn't want the Epic Name field to be mandatory unique for all Jira projects. That would greatly diminish the value of cloning - which we do a lot.
May I suggest that perhaps instead of pre-pending the Epic Key to the Epic Name (changing the data and making the text field longer) in order to solve the CSV export issue that both or at least the later of the following are implemented:
- The Epic Name field is coded to be unique in the DB. Yes, this will mean some initial pain for existing customers with duplicates, so a check before upgrade will need to be included also. The benefit here is that the
- Both the Epic Link and Epic Name fields get populated and exported any time either of the fields exist within the exported data, even if both are not requested. This should not be difficult to code. This would essentially behave in the same way as the Project Description field, which get's exported whenever the Project (name) field is one of the fields being exported even though it is not requested
Alok Misra
added a comment - Good work
Need the user story extract/excel import to allow text instead of key to display same as in HTML/Jira report views. When using HTML export of user stories the epic link will show as 'text' (name is shown) instead of the epic issue key. Same applies in the Jira views and reports. This is really helpfull since the key does not give context info of the epic for the listed user stories. I was asked to automate the export for reporting purposes and found that the csv and excel plug in te get Jira data in excel, both only provide the key and mess up my report views as well relevant stakeholder info is missing now, since the epic textual description is not available anymore. So automation is also not possible to replace the manual extraction via HTML.
I understand the Jira issue but both the key and name of the epic would be very useful when extracting to /importing in excel the user story data.