Issues with Epic

Hi, I have some questions about Epic. Our team was not using it before as we were not using a scrum process. But recently we upgraded to Jira 6.03 and one of sub team would try the scrum board.

1. In our Jira configuration, we don't have Epic type. I find Requirement issue type is automatically considered as an Epic, which means when I create a requirement it turns to Epic. Is this set somewhere? I really don't want to use Requirement type as an Epic type, as it could create confusion for other sub-teams who don't use scrum.

2. Epic Name suddenly becomes required after upgrade! and it is locked! How can we fix it?

These are quite urgent issues for us. Apprecidate your rapid response.

Thanks and Regards


1 answer

0 votes
  1. Requirement as Epic issue type, might have something related to SCRUM DEFAULT TEMPLATE that is pointing Requirement as Epic. You can check out
  2. The locked Epic name, really to secure the custom fields that should only be modified GreenHopper (JIRA Agile) instead of JIRA. You can look into

I would actually recommend you to contact for further assistance.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Mar 13, 2019 in Marketplace Apps

Marketplace Spotlight: Marketing apps for Confluence to keep your teams working on the same page


204 views 0 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you