Forums

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

Epic creation from backlog not showing all fields

Esther Strom
Community Champion
June 12, 2019

We have added a number of fields to our Epic screen. We've noticed some odd behavior, and I don't know if it's a bug or if I've done something wrong.

When a user (any user, including me as admin; this isn't limited to specific users) creates an Epic using the + icon in the left navbar, all fields are displayed in the form. But when they use the Epic panel in a board backlog to create an epic, only a few fields display, and even if they click the Customize Fields button and select All, it doesn't remember the selection the next time.

This is the Epic creation screen when done from the + icon:
createEpicPlusIcon.png

This is what we see if we use the Epic panel in a backlog:

createEpicFromBacklog.png
createEpicConfigureFields.png

Is there any way to make the screen that displays there show all of the fields? I've checked both the screen (in admin mode) and the issue layout via Project Settings, and many of the fields that are not displaying are listed in the Primary Fields section of the layout, so I don't think it has anything to do with that.

1 answer

1 accepted

0 votes
Answer accepted
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 13, 2019

Hello Esther,

Thank you for the detailed description of the problem you are facing.

Indeed, the behavior described by you where the selected fields are not remembered when creating the issue through the board planning section (backlog) is a known bug in JIRA application. Here's the link of the reported bug:

Create Epic dialog does not remember which fields should be displayed

Feel free to vote and watch the bug to receive notifications about any possible workarounds or updates of its fix implementation.

For now, we suggest your team to keep using the + icon in the left navbar to create Epics to avoid this bug.

Let us know if you still have any questions.

Esther Strom
Community Champion
June 13, 2019

Thank you for the link. Yet another easily-corrected issue that's been open for 6 years. 

Suggest an answer

Log in or Sign up to answer