Issues with Epic

[Zhenning Bao]

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

Zhenning

[Zul NS [Atlassian]]

1. Requirement as Epic issue type, might have something related to SCRUM DEFAULT TEMPLATE that is pointing Requirement as Epic. You can check out https://confluence.atlassian.com/display/GHKB/How+to+Fix+the+Duplicate+GreenHopper+Custom+Fields+After+Upgrading
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 https://confluence.atlassian.com/display/GHKB/How+to+unlock+a+Locked+field

I would actually recommend you to contact support.atlassian.com for further assistance.