• We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      With the advent of 5.0, there is a new issue creation dialog box. We have had some customers for which that is a blocking issue, and have kludged a workaround that disable it. We'd really appreciate having a toggle in the UI that we could direct admins to.

            [JRASERVER-28758] Disable QuickIssueCreate lightbox via dialog

            Kenneth Yu added a comment -

            Please reopen this issue so we can vote on it. 

            Kenneth Yu added a comment - Please reopen this issue so we can vote on it. 

            With this new dialog, Google Chrome doesn't control whatever text fields contain and therefore does not warn a user if he closes the tab with some info in it. Which doesn't happen with the old one.

            Could it be fixed somehow?

            admin@ru.axxonsoft.com added a comment - With this new dialog, Google Chrome doesn't control whatever text fields contain and therefore does not warn a user if he closes the tab with some info in it. Which doesn't happen with the old one. Could it be fixed somehow?

            #metoo

            Bachowny Plamborgs added a comment - #metoo

            francis added a comment -

            We had a couple customers asking for a workaround.  Especially when they have large tables (using the table grid editor), the lightbox is too narrow.

            Given that this issue has been closed as won't fix, we created an addon to support full screen dialogs (which includes resizing the input fields)
            https://marketplace.atlassian.com/plugins/com.idalko.fullscreendialogs/server/overview

             

             

            Francis

             

            francis added a comment - We had a couple customers asking for a workaround.  Especially when they have large tables (using the table grid editor), the lightbox is too narrow. Given that this issue has been closed as won't fix, we created an addon to support full screen dialogs (which includes resizing the input fields) https://marketplace.atlassian.com/plugins/com.idalko.fullscreendialogs/server/overview     Francis  

            @dave You don't have to disable the creation dialog, just redirect to the new ticket you've created instead of letting it disappear.

            Deleted Account (Inactive) added a comment - @dave You don't have to disable the creation dialog, just redirect to the new ticket you've created instead of letting it disappear.

            CollinM added a comment -

            Agree with some of the others posting here.  When an issue is created it is natural for them to want to review it.  Trying to click on the pop-up before it goes away is very frustrating.  Can this be changed?

            CollinM added a comment - Agree with some of the others posting here.  When an issue is created it is natural for them to want to review it.  Trying to click on the pop-up before it goes away is very frustrating.  Can this be changed?

            Please re-open so people can vote for this. Users should be able to choose their preferred workflow.

            Phil Rittenhouse added a comment - Please re-open so people can vote for this. Users should be able to choose their preferred workflow.

            Like many, I find the new behavior extremely frustrating....

            However, in my browser, I've found a work around for the popups. I either middle click on the Create button, or I right click and select open in a new tab. Either of these gets the "light box" on its own page and makes the popup go away. Unfortunately, you are still stuck with the narrow entry problem.

            Wayne Walker added a comment - Like many, I find the new behavior extremely frustrating.... However, in my browser, I've found a work around for the popups. I either middle click on the Create button, or I right click and select open in a new tab. Either of these gets the "light box" on its own page and makes the popup go away. Unfortunately, you are still stuck with the narrow entry problem.

            Dave,
            Russell is right. we want submitting a create to take us to the ticket we created, or make the popup "id of the new ticket" box stay onscreen a long time (30 seconds?)

            Wayne Walker added a comment - Dave, Russell is right. we want submitting a create to take us to the ticket we created, or make the popup "id of the new ticket" box stay onscreen a long time (30 seconds?)

            Hi Dave - I think the issue is not the issue creation dialog box, but the confirmation popup that is shown after the issue is submitted. The expected functionality in my opinion would be to forward the user to the created issue instead of staying on the same page.

            Russell Zager added a comment - Hi Dave - I think the issue is not the issue creation dialog box, but the confirmation popup that is shown after the issue is submitted. The expected functionality in my opinion would be to forward the user to the created issue instead of staying on the same page.

            Dave Meyer added a comment -

            Hi everyone,

            Disabling the issue creation dialog box is not going to be supported in JIRA. Our goal is to simplify the app and create a faster, fluid experience for users.

            Please contact me if you have any questions: dmeyer@atlassian.com

            Regards,
            Dave Meyer
            Product Manager, JIRA

            Dave Meyer added a comment - Hi everyone, Disabling the issue creation dialog box is not going to be supported in JIRA. Our goal is to simplify the app and create a faster, fluid experience for users. Please contact me if you have any questions: dmeyer@atlassian.com Regards, Dave Meyer Product Manager, JIRA

            Hi Matt,

            After creating an issue, there is a brief notifier that swoops in and out, but if you don't press it, then the issue that was already on your screen when you pressed Create remains. This is leading to a lot of our users attaching screenshots and files and comments to the wrong issue.

            Neal Applebaum added a comment - Hi Matt, After creating an issue, there is a brief notifier that swoops in and out, but if you don't press it, then the issue that was already on your screen when you pressed Create remains. This is leading to a lot of our users attaching screenshots and files and comments to the wrong issue.

            Has everyone got this figured out? Being an accidental Jira admin and being forced to jump Jira from 4.1.1 to 6.3.15 - imagine the nasty surprise as i work thru my Selenium tests - i create the issue but i don't land on the created issue. So now what? I guess i do some SIL + jql in a post function to figure out newly created issue and then jump to that page? How do the big dogs do it? (and i like Dave's suggestion because i can poke that checkbox with Selenium and continue with my tests)

            Richard Fears added a comment - Has everyone got this figured out? Being an accidental Jira admin and being forced to jump Jira from 4.1.1 to 6.3.15 - imagine the nasty surprise as i work thru my Selenium tests - i create the issue but i don't land on the created issue. So now what? I guess i do some SIL + jql in a post function to figure out newly created issue and then jump to that page? How do the big dogs do it? (and i like Dave's suggestion because i can poke that checkbox with Selenium and continue with my tests)

            I'd like to see a checkbox, maybe next to the "Create another" checkbox that allows you to select whether you land back where you were or open the issue. Seems like that will make everyone happy.

            Dave Theodore [Coyote Creek Consulting] added a comment - I'd like to see a checkbox, maybe next to the "Create another" checkbox that allows you to select whether you land back where you were or open the issue. Seems like that will make everyone happy.

            The workaround works but creates this bug https://jira.atlassian.com/browse/JRA-34926

            Would really like to see an option to disable this "feature".

            Jonathan Dowd added a comment - The workaround works but creates this bug https://jira.atlassian.com/browse/JRA-34926 Would really like to see an option to disable this "feature".

            Hi Matt,
            The lightbox made project selection a lot slower than in JIRA 4.4 when there is a large number of projects (>900).
            It also caused newly created issues not to be displayed anymore on the view issue screen. So if a user misses the link that is displayed for some seconds after creation he needs to go to the issue history. This makes it more difficult for users to revise a newly created issue. User need to think where they didn't have to think before!
            I really wish we had at least a check mark to turn on/off the 5.0 behaviour.
            Regards,
            Dieter

            Dieter Greiner added a comment - Hi Matt, The lightbox made project selection a lot slower than in JIRA 4.4 when there is a large number of projects (>900). It also caused newly created issues not to be displayed anymore on the view issue screen. So if a user misses the link that is displayed for some seconds after creation he needs to go to the issue history. This makes it more difficult for users to revise a newly created issue. User need to think where they didn't have to think before! I really wish we had at least a check mark to turn on/off the 5.0 behaviour. Regards, Dieter

            Christiano added a comment -

            After applying the solution on Announcement banner and click the button to open a new issue, a new screen appears with only two fields: project and issue type. Then I need to click on next button to pop up the entire screen. Is there some trick to appear all fields at once instead of having to click the button next ?

            Christiano added a comment - After applying the solution on Announcement banner and click the button to open a new issue, a new screen appears with only two fields: project and issue type. Then I need to click on next button to pop up the entire screen. Is there some trick to appear all fields at once instead of having to click the button next ?

            Paul,

            Totally unrelated. My apologies.

            John Garcia (Inactive) added a comment - Paul, Totally unrelated. My apologies.

            Paul Ingemi added a comment - - edited

            Hi John, I saw your comment in JRA-24424 on a workaround disabling the New Issue Creation lightbox and it being superseded by this issue. Since JRA-24424 is concerned with the lightbox used for images... does this workaround help with that? The two seem unrelated to me but I'm probably missing something.

            Paul Ingemi added a comment - - edited Hi John, I saw your comment in JRA-24424 on a workaround disabling the New Issue Creation lightbox and it being superseded by this issue. Since JRA-24424 is concerned with the lightbox used for images... does this workaround help with that? The two seem unrelated to me but I'm probably missing something.

            David Yu added a comment -

            Personally not a fan of lightboxes but I can see why this might be useful in areas such as the Rapid Board where you don't want to force a page reload.

            I would like it more if the width would auto-adjust based on my screen resolution so I'm not scrolling up and down.

            David Yu added a comment - Personally not a fan of lightboxes but I can see why this might be useful in areas such as the Rapid Board where you don't want to force a page reload. I would like it more if the width would auto-adjust based on my screen resolution so I'm not scrolling up and down.

            MattS added a comment -

            That first one is an interesting case, but seems to me like some user education might solve it better. Anyway, the second reason is a really good one that I'll keep in mind.

            Yes, Summit was a blast this year. The next Atlassian User Group is at Atlassian SF, might see you there.
            https://confluence.atlassian.com/display/AUG/SF+Bay+Area+Atlassian+User+Group

            MattS added a comment - That first one is an interesting case, but seems to me like some user education might solve it better. Anyway, the second reason is a really good one that I'll keep in mind. Yes, Summit was a blast this year. The next Atlassian User Group is at Atlassian SF, might see you there. https://confluence.atlassian.com/display/AUG/SF+Bay+Area+Atlassian+User+Group

            Matt,

            A couple of things come up. In the case that brought me here, the admin was hoping to push user behaviour into explicitly reviewing the Project field because too many issues ended up in the Most Recent project in error.

            Another common request is that IE8 has a bug that prevents it from showing the full Project list if there are more than 350 projects or so. Admins with many IE8 users (or in environments that are restricted to IE8) like to disable this to return to the old Project picker, which appears to work fine.

            Also, great meeting you at Summit '12!!

            Thanks!
            John Garcia
            Atlassian Support - SF

            John Garcia (Inactive) added a comment - Matt, A couple of things come up. In the case that brought me here, the admin was hoping to push user behaviour into explicitly reviewing the Project field because too many issues ended up in the Most Recent project in error. Another common request is that IE8 has a bug that prevents it from showing the full Project list if there are more than 350 projects or so. Admins with many IE8 users (or in environments that are restricted to IE8) like to disable this to return to the old Project picker, which appears to work fine. Also, great meeting you at Summit '12!! Thanks! John Garcia Atlassian Support - SF

            MattS added a comment -

            John,

            Out of interest why did some users want to disable this feature? I'm expecting to be asked to do this but I'm curious.

            ~Matt

            MattS added a comment - John, Out of interest why did some users want to disable this feature? I'm expecting to be asked to do this but I'm curious. ~Matt

            John Garcia (Inactive) added a comment - Workarounds can be found here

              Unassigned Unassigned
              jgarcia John Garcia (Inactive)
              Votes:
              64 Vote for this issue
              Watchers:
              50 Start watching this issue

                Created:
                Updated:
                Resolved: