nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Enable Create Issue Pop-up modal

Darren Simons_kbpaso

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!

Accepted answers

Walter Buggenhout

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!

All comments

Walter Buggenhout

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.

Hope this helps!

Darren Simons_kbpaso

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 P 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_kbpaso

@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 Create Issue 1.png Create Issue 2.png Create Issue 3.png Create Issue 4.png

Sabina af Jochnick

I ran into this issue this week and after some digging and troubleshooting I have found the answer to the behavior between inline creation vs the popup. It all comes down to project filtering.

I have 2 projects, project A and project B:

Project A had popups, project B did not. Both had the same screens, same required fields etc.
In project B the "Create" button didn't work at all on some boards while it worked well on other boards.

After some digging and testing, where it did not work at all, there was no project specified on the board's filter. Where it had the inline option, one project was specified, and where the pop-up happened, it had two or more projects specified in the filter.

Not sure if this helps but to add some complexity for my troubleshooting, was that we have a custom field created for teams (since Jira's own field doesn't work well with dashboards) which uses contexts depending on which team belongs to which project.

In project A, our teams exists on both projects while project B's teams only exist in project B. If I added a team for only project A but didn't include it in project B, I got the same behavior with the create button not working in project A, but a popup in project B, even if a project wasn't in the filter.

The conclusion is that in order to create a new ticket, the project field is required, and if not specified it can't create one. If you have more than one project to choose from, it triggers the pop-up so you can specify which project you want it in. If no project is specified, Jira doesn't know where to create it.

(And with my custom teams field, when I put the filter for only that team in the other project, Jira triggered the pop-up since the team only existed in project A, but was used in project B, noticing a conflict on projects).

I hope this helps someone (:

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud