Our UX initiative is a Jira project. Within that project we have created EPICs for all our products. Designs for new features and functionality are stories within those EPICs. Our current numbering scheme does nothing to make the parent > child relationship apparent. For example if one of our EPICs is numbered as follows "UX - 911 Collaboration Service" when we create new stories to enhance the functionality of that module the numbering is unrelated. Right now new stories are auto numbering as UX -8XX. This is really confusing and there is no hierarchical relationship in the left nav, it's just a jumble of epics and stories.It would make much more sense if a story within an EPIC had an obvious relationship.EPIC 911- Story 911- 01- Story 911- 02I'm not sure whether this is just our implementation of the product creating this disconnect in the auto numbering of EPICs and Stories or whether this is possible. I've searched on the issue and haven't found an obvious answer. Any help would be appreciated.

Community
Q&A
Jira
Questions
EPIC and Story numbering - can we make the parent/child relationship obvious

In a create screen I need another attachment field.

In a create screen, already I have an attachment field and also we have option in description for second choice of attachments, but I need an another attachment field particularly other than description type field. I need same attachment field like second field with "Additional Attachments" name.

1 answer

1 accepted

0 votes

Answer accepted

It's not clear which left nav you mean, a screenshot would help. Also, Jira Server or Jira Cloud?

In general you can't change the format of a Jira issue key. You can show the Epic Link or Links fields in the Issue Navigator results List View