Is there a way to auto open the issue after creation so subtasks can be immediately added?

[JanaW]

When we create an issue and submit, it creates it and then gives you a brief pop up box to select it and open the issue. If you don't select that option quick enough we have to search for the issue and then open it. We would like the have the option to open the issue immediately upon creation so that we can add subtasks. If that is possible with a configuration setting, can it be done by project or would it be global, our preference would be by project.

[Dieter · Accepted solution]

You could vote for https://jira.atlassian.com/browse/JRA-28758 which also contains some workarounds to restore the issue creation behaviour from JIRA 4.4 which opens the view screen for the newly created issue

IMHO this was better definitely faster. Whoever had to select from more than 900 projects in the popup create screen knows what i am talking of ...

ok, this solution is just appropriate if you want to restore old behaviour without pop up create screen

[Karl Roth]

Henning, I have heard so many people complaining about this. Especially those who start editing the wrong issue. In my experience it it MUCH more common (natural?) to work in the new issue than the previous one.

[Alex Perez]

Is this issue fixed?

There are some bug reports about the create issue lighbox but in my opinion, the main problem is that the navigation flow changed and the users feel dissapointed for the extra step to view the issue just entered.

IMHO, the correct flow should direct the user to the "view issue" screen, unless "create another" flag is selected.

[Henning Tietgens]

IMO this depends on the point of view.

If the JIRA workflow and the screens are well designed there are a lot of situations where the user who creates the issue doesn't have to open the issue right after creating it. All needed information was added and the next action could already be triggered on the create screen (e.g. assign to the next responsible). E.g. for a support team this is very nice, because the user can work on an issue, take a call, create a new issue, which is proccessed later, and still stays on the issue which is currently in progress.

IMO it would be nice if this is configurable, maybe as part of the workflow.

Henning

[Karl Roth]

This behaviour is different from when you CLONE an issue, then you jump automatically into the new one.

I prefer that behaviour, but yes - configurable is the most interesting setup.

[Ian Springer]

I extracted the guts of Andrew Heald's Issue Quick Start plugin and converted it to a userscript, which will be easier to install than the plugin, since it doesn't require any changes to the JIRA server. It will also probably work on OnDemand/Cloud. Note, I have only tested it with JIRA 7.8.2 self-hosted.

Here's the userscript. You'll need to change the @match to your JIRA URL. Then install it using Tampermonkey.

// ==UserScript==
// @name JIRA Issue Quick Start
// @namespace http://tampermonkey.net/
// @version 0.1
// @description after creating a new issue, automatically open that issue (based on https://marketplace.atlassian.com/plugins/uk.org.sappho.jira.plugin.jira-plugin-goto-new-issue/server/overview)
// @author Andrew Heald
// @match https://jira.example.com/*
// @grant none
// ==/UserScript==

(function() {
  'use strict';

  console.log('issue-quick-start: Initializing...');
  AJS.$(document).on('DOMNodeInserted', function(event) {
    if (event.target.id == 'aui-flag-container') {
      console.log('issue-quick-start: Got post-it note!');
      AJS.$(event.target).on('DOMNodeInserted', function(event) {
        console.log('issue-quick-start: Post-it HTML: ' + event.target.innerHTML);
        var postItLink = AJS.$(event.target.innerHTML).find('a');
        var postItPath = postItLink.attr('href');
        if (postItPath && postItLink.attr('data-issue-key')) {
          console.log('issue-quick-start: Going to new issue path ' + postItPath);
          window.location = postItPath;
        }
      });
    }
  });
})();

[Victor Combal-Weiss]

Thank you VERY much!

Thanks to you I also discovered Tampermonkey, this is great!

[Kevin Mote]

I posted a solution in this Answer which works for version 5.1.

This feature is also available as a plugin: Issue Quick Start which works with versions 5.0 through 5.2.11. I just installed the plugin and ... so far, so good.

UPDATE: Plugin still works on JIRA 6 and JIRA 7. SECOND UPDATE: No longer works on 7.0.

THIRD UPDATE: Andrew Heald has released a new version of his plugin that works on JIRA7 (and should be compatible with JIRA6 as well). I just installed it and it works perfectly! Give it a try!!

[Karl Roth]

Still problem with OnDemand.

[Ian Springer]

I extracted the guts of Andrew Heald's Issue Quick Start plugin and converted it to a userscript, which will be easier to install than the plugin, since it doesn't require any changes to the JIRA server. It will also probably work on OnDemand/Cloud. Note, I have only tested it with JIRA 7.8.2 self-hosted.

Here's the userscript - you'll need to change the @match to your JIRA URL. 

// ==UserScript==
// @name JIRA Issue Quick Start
// @namespace http://tampermonkey.net/
// @version 0.1
// @description after creating a new issue, automatically open that issue (based on https://marketplace.atlassian.com/plugins/uk.org.sappho.jira.plugin.jira-plugin-goto-new-issue/server/overview)
// @author Andrew Heald
// @match https://jira.example.com/*
// @grant none
// ==/UserScript==

(function() {
  'use strict';

  console.log('issue-quick-start: Initializing...');
  AJS.$(document).on('DOMNodeInserted', function(event) {
    if (event.target.id == 'aui-flag-container') {
      console.log('issue-quick-start: Got post-it note!');
      AJS.$(event.target).on('DOMNodeInserted', function(event) {
        console.log('issue-quick-start: Post-it HTML: ' + event.target.innerHTML);
        var postItLink = AJS.$(event.target.innerHTML).find('a');
        var postItPath = postItLink.attr('href');
        if (postItPath && postItLink.attr('data-issue-key')) {
          console.log('issue-quick-start: Going to new issue path ' + postItPath);
          window.location = postItPath;
        }
      });
    }
  });
})();

[Akeles]

Agreed. Is there any issues that we can vote for?

[JanaW]

This appears to be fixed in the 5.2.7 upgrade. We just upgraded and now the issue opens after creation.

[JanaW]

As it turns out, this is not fixed in 5.7

[Corentin Méhat]

Hello,

(both tested ok with JIRA Server 7.2.2)

looking around this I found 2 different ways of doing so (to integrate in a plugin or in the banner):

AJS.$("#create_link").removeClass("create-issue");

cf. : https://confluence.atlassian.com/jirakb/how-to-disable-create-issue-popup-300813780.html

or the plugin "issue quick start" (also in js):

https://marketplace.atlassian.com/plugins/uk.org.sappho.jira.plugin.jira-plugin-goto-new-issue/versions

[Kevin Mote]

A plugin for JIRA 6 & 7 is now available. See my answer below for details and link.

[Wayne Walker]

Like Bob and others, 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. 

[Daniel Santos]

This solution also works for JIRA7: Disable the new Issue Creation dialog in JIRA 5.0

[Kevin Mote]

The solution you linked to does not address the problem described by the Original Poster.

[Daniel Santos]

Hi @Kevin Mote, could you help me understand why this solution do not address the poster problem?

[Kevin Mote]

The problem described on the page you linked to occurs as soon as the user hits the Create button. The problem described on this page occurs after the user creates the ticket and then hits Submit. Two totally different issues.

[Daniel Santos]

After the above suggested change, when you submit the ticket it is automatically opened. Since no banner is shown and the new created issue is automatically opened I understand it as a possible solution for the posted problem.

[Kevin Mote]

I guess, strictly speaking, that's true (assuming that your linked solution doesn't change pages after the Submit button is pressed. I haven't tested it). I will remove my down-vote.

[Daniel Santos]

Yes, I tested that. Thanks!

[Gordon Kotik]

I also agree. My software team finds this new behavior very frustrating. It causes many mistakes such as attaching files to the wrong issue.

[JanaW]

This appears to be fixed with the jira 5.2.7 upgrade. We just upgraded and now the issue opens upon creation.

[Henning Tietgens]

I think the use case is that all needed information is captured on the create screen. Our support line, where there are some users working as a dispatcher, love this because they are not visually interrupted while working on there current issue.

But it should be configurable on a user basis.

[Bob Swift OSS (Bob Swift Atlassian Apps)]

I agree. The change that was made to JIRA a few releases back to do this is very frustrating. I can understand doing this when working from a list but not when on viewing another issue. A high percentage of time I want to look at the newly created issue and add links or similar. If I don't catch it before it disappears it is painful to go find it. If I really DO want to get back to the original issue I was looking at, it would just be a simple back button click. I don't know what user case there was for the current behavior :(.