Different naming convention for EPICS and User Stories within the same project.

[Manu Tyagi]

I have a project with the key say XYZ. When I create epics or US in that project they all get named XYZ-1, XYZ-2, and so on, randomly. I cannot distinguish whether an item is an epic or a user story(except for the symbol/icon, of course) and are parent-child as well. I basically am looking for some indicator that shows the parent-child relationship between an epic and the US. 

E.g. Say if I have an epic XYZ-23. I would like to have a naming convention like XYZ-23-1, XYZ-23-2, and so on or something on similar lines for the US of that epic. 

[Alex · Accepted solution]

Hey @Manu Tyagi welcome to the community!

The issue key is composed by the project key and a sequencial number (Ex. KEY-123). Jira does not allow to handle the issue unless and change how it is created. 

However, as per your question, when viewing an Epic issue in the screen please note a session named Child Issues listing all stories and tasks linked to the Epic.

Additionally, in the issue view you can also note a field named Epic Link, which has the role to identify the parent Epic of a particular issue. This field will be changed soon and you can find the article https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/ which explains the changes. 

I hope this helps.

Cheers,

Alex

[Tom Lister · Accepted solution]

Hi @Manu Tyagi 

It's not possible to customise the issue keys based on any criteria.

When reporting issues is it possible in most cases to show the issue type and/or epic link to  make it more readable.

Note that Epics and Stories don't have to be in the same project as long as they are visible to each other. i.e. you can have a project for epics and and separate project for stories so the keys are different for you.