3 answers

The field Epic Name, Epic Link, Epic Color, and Epic Status are add-on fields (NOT custom fields, they are add-on fields) that are tied to the Epic Issue Type upon JIRA Agile installation. This is why they only show up on the Epic Issue Type, this is why they do not show up on others. Additionally, the Epic Link functionality, along with Scrumboard Agile functionality, are specifically tied to the issue type.

As far as I know, you cannot simply add a new issue type to extend this functionality.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

There should be option to allow JIRA admins to add a new field like Epic. Simple and important business case is, As a product owner I want to create one more level "theme" between Epic and User Stories to manage my backlog better. Pls let me solution for this ?

This is very important for product owners, dont understand why Atlassian dont work on it and provide a solution? This should not be that tough !!

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

I'd like to add an even simpler oversight from Atlassian - being able to create addtional Epic issue types. If they see fit that we can create our own issues with different names. workflows etc, why do they think that all these issue types can just be bundled under one epic type.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...