How can I customize the create issue dialog when looking at an epic?

[Markus Günther]

Hi there,

starting with Jira poses a looooooooot of questions. 

So my question is: 

While looking at an epic, you're able to create subtasks. So far so good. But our epics require components, so do their subtasks. But the mask doesnt allow adding a component to a new subtask. The only chance to achieve this is 

a) either stop making components mandatory

b) create an issue and use the "epic link" field

non of this is satisfaying. Cant I add a second field to this dialog? thx

[Matthew Canham]

Hi @Markus Günther, thank you very much for raising this issue. My name is Matt, I'm a product manager on Jira Cloud and my team has just had a look into this one for you.

After a bit of digging we were able to reproduce this. We believe the problem arrises because the required field is not on the "Create" screen for this issue type.

You can fix this by going to Project Settings -> Screens and dropping down the screen configuration for the issue type in question. You will then want to confirm that the "Create" screen that is selected has the required field on it. See screenshot below that points this out.

You can either add the required field to this screen, or if you'd like you can create a new screen that has all of the required fields and link this new screen to the "Create Issue" operation.

Let me know if this helps.

[Markus Günther]

Hi Matthew,

thanks for following up on this. 

With respect to my minimal experience in Jira I may be wrong, but I did as described above and both my components and my due date field are selected for this particular screen. I will provide screen shots and a little more testing once I'm in the office, screen shots just dont look good on my current screen.

[Earl McCutcheon]

Hello @Markus Günther ,

Thanks for pointing out the issues, and I created the following Bug report so we can follow up on this one:

• https://jira.atlassian.com/browse/JRACLOUD-75648

Currently, in the new issue view, there is not a way to bypass this without removing the required fields as you noted, but you can temporarily disable the new issue view under your personal settings to revert to the classic view until the end of March as a workaround, noting:

From Mar 31, 2021, we'll be moving all users on the old issue view in Jira Cloud products (Jira Software, Jira Service Management, Jira Core) to the new issue view — which means you won't be able to switch back to the old view anymore. For key dates, what's next, and more details, check out our official announcement.

Hope this helps out until the bug is fixed, and make sure to add yourself as a watcher to get updates.

Regards,
Earl