Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Custom Issue Type for Epic not showing Epic Name Field.

Benson
Contributor
June 16, 2019

Hi I have created a Custom issue type for Epic and under the field configurations for Epic Name, I did configure the field in three screens (Create, Edit and View)

However, the Epic Name field if not showing up when I create a new Epic.

When I used "where is my field?" It highlighted the following issue: 

The field 'Epic Name' is not configured in scope of the project '[Project Name]' and issue type 'Epic [XXX]' To solve this issue, go to 'Epic Name' configuration page and add it to the scope.

However, I am on JIRA cloud license and unable to unlock the Custom Field Configuration schemes for this custom field.

Is there any other workaround for this issue?

 

2 answers

1 accepted

1 vote
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 16, 2019

Only Epic type issues can have the Epic Name field, and you can only have one Epic type.  Even if you could unlock the scheme (which you can not do on Cloud), adding the field would make no difference, as your issue type is not an Epic.

There's no "workaround" - there's nothing to work around!

Benson
Contributor
June 16, 2019

Hi Nic,

Thank you for the quick response. I am planning to manage 3 related products in one project. Hence, wanted to use custom issue type Epics for each product in my project. However, the 'Available context' for custom field only lists the default 'Epic' Issue type.

Will JIRA server version allow me to configure the custom Issue Types as Epics?

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 17, 2019

No.  It has the same base as Cloud.

You can unlock fields on server, but

  • Do not do it, they are locked for a good reason - to stop you breaking things by doing things like changing the epic name field context
  • It won't do what you think it will.  Your new issue type will NOT behave like an Epic.  You'll get Epic Name on the new issue type, but it won't do anything more than be some extra text.  And Jira software will start throwing some "interesting" errors instead of working.

You can only have one issue type that is an Epic.

0 votes
Benson
Contributor
June 17, 2019

Noted, Nic. Thank you for the clarification.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events