Enable Create Issue Pop-up modal

[Darren Simons]

When I am in the backlog and click 'Create Issue' in a particular sprint, I do not get the Create Issue pop-up modal for me to fill out the details of the issue. It only gives me the option to type text and submit which immediately creates the issue in the backog.

I am looking for the system to pop up the Create Issue modal where I can add all the applicable details before actually creating the issue. How can I enable this setting?

Additionally, it is enabled in SOME of our company projects but i can not figure out what differences exist between the projects to see why some do pop-up and some do not

Thanks!

[Walter Buggenhout · Accepted solution]

Hi @Darren Simons and welcome to the Community!

The link you click in the backlog view is designed for quick, in-line creation of issues with limited fields just to be able to move fast.

If you want to add the full details of an issue, you can always do so (wherever you are in Jira) by clicking the big create button in the menu bar at the top of your screen. As long as you select the right project and issue type there, your issue will land nicely in the backlog of your board. Jira remembers the last project / issue type you selected so you can pretty quickly add additional issues the same way.

Hope this helps!

[Darren Simons]

Hey Walter, thanks for your answer. I understand you can create stories from the top, which, do pop up the create issue modal I am looking for.

I think that many of our analysts prefer to create new issues from the sprint itself because then the modal pre-fills the sprint (whereas, in cases where you forgot to add the sprint when creating from the top, it just puts the issue in the bottom of the backlog and can get forgotten about.)

My biggest ?? is why a few of our projects do pop up the modal when clicking the create issue within the sprint and some do not. I am hoping there is a way to have all our projects set up where it pops up when creating from the sprint (counterintuitive to the "quick" issue create, I know, but that is what we prefer :))

[Trudy Claspill]

Hello @Darren Simons 

Are you working with Team Managed projects or Company Managed projects? It will say at the bottom of the navigation pane on the left.

For the projects where the pop up is appearing, are those Team Managed or Company Managed?

Are you talking about the functionality that is described in this article?

https://community.atlassian.com/t5/Jira-articles/Introducing-a-new-issue-create-experience/ba-p/2212427

[Darren Simons]

@Trudy Claspill Thanks for your response. That article is not what I am referring to. Maybe if I add some screenshots I can better explain.

I am using a company managed project for all of our projects... not just the ones where the pop-up appears or doesn't appear, so I do not think it has to do with that.

The functionality I am referring to is in the attached screenshots. From one of our projects, once you click create issue it just forces you to type in the issue details and creates it inline. For the other, when you click create issue it pops up the modal and lets you edit all the details before actually creating

[Trudy Claspill]

For the projects where the Create Issue dialog is displayed, are there additional fields that are Required besides Project, Issue Type, Summary, and Reporter?

When there are more Required fields, per the Field Configuration for the project/issue type, then the Create Issue dialog will display.

[Darren Simons]

They both have the same required fields.

I was able to find a work around from your response above where I did make more fields required in my project and the modal pops up after you type your summary and click create now (so not on clicking create the first time, but rather after you type your "What needs to be done?" and then hit enter it pops up.)

So you've got me to a point where it works but not exactly what I was looking for :)

Either way, I greatly appreciate the help!

[Dominique]

Hi Darren, 

I am looking for the exact opposite and was wondering if you found out what triggers that issue screen. 

I have several projects, all company managed, and only one gives me the "create issue" pop up screen when using the inline function. I dont want it to open and can not find a setting option for it. 

In case you found out how to solve it, I would appreciate your help.

Thanks,

Dominique

[Darren Simons]

Hey Dominique,

Basically, what I have found is that screen is controlled off the fields you have set to be "required" when creating a specific issue type. So for example, if you just have the issue type and summary required then you would be able to create it inline, but if you start to make other fields required (like description for example) it will open the create issue modal because you need to add that info before the issue can be created. Check your settings for required fields in your Field Configurations. 

[Dominique]

Hey Darren, 

thanks for your quick reply.

I checked that, but I reused the same scheme for all projects, so the setting should be the same. So, I still don‘t have clue.

[Darren Simons]

I don't think there are any other settings I am aware of that control this. Behind the scenes there must be something set as required that is causing the modal to pop-up rather than create in-line. If reviewing this doesn't produce anything of note, I would open a separate thread with Atlassian :)

[Dave Elger]

I've been searching for a solution to this problem and this is the best, most descriptive thread I have found.  I have the added layer of complication that I am forced to use workflow validators instead of required fields because some of my required fields are "locked" by Atlassian.

The Create issue screen associated with the inline creation buttons will only pop up if one of the required fields is marked as required in the field configuration.  When I moved to using workflow validators, I un-required the fields in the field configuration and the create issue screen stopped being displayed.  When I went back and marked the field as required in field configuration, the Create Issue screen is displayed and the user can avoid the error.

If you have followed me this far, my field is double-required, once in field configuration and once in workflow validators.  And it works.