JIRA Agile: Turn Off Global Auto Transition of User Stories once Sub-Tasks Are Complete

Malik Graves-Pryor March 9, 2014

Is this possible somewhere? It used to be exposed when it was Greenhopper but it doesn't seem to be available now that it's a core component of JIRA.

I've got default workflows in place that do not fit into the standard "all sub-tasks are done? ok great, transition the parent story to done. Oh, I can't? Pop up a window stating as much as have the user click acknowledge".

Turning off that default global transition for all workflows would be ideal.

5 answers

2 votes
Jake Fisher March 31, 2015

I turned this off by editing the header.jsp in the atlassian-JIRA  . See this article

 

Added this snippet

<script type="text/javascript">
try{
GH.Dialogs.CompleteParentDialog.showDialog = function(issue, transitions, columnData) {};
}
catch(err) {
}
</script>
Jonas Andersson
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 22, 2016

Hi Jake,

Does this script demand a script-runner or some other dependency? Have added it to the top of header.jsp (JIRA_APPLICATION_DIR/atlassian-jira/includes/decorators/aui-layout/header.jsp) and restarted the server, but we still see the popup dialog..

Jake Fisher January 25, 2016

There were no other dependencies at the time I used that solution. The solution itself is a bit of a dirty hack. If the version of JIRA or JIRA agile were different than the version I had been using last March I suspect Atlassian easily could have changed something internally that would have caused it not to work anymore.

I would echo, the solution really shouldn't be very hard for them to technically implement  and now that the agile code base is no longer a plugin but part of a core product maybe they may be more likely to change it. Since the original issue has been closed maybe we need to craft a new one that better addresses how it breaks team's agile process and definition of done to move a main line story to done, just because a set of subtasks is done.Once the story's tasks are done it should be accepted before being moved to done

0 votes
ZachE January 21, 2016

Wow, another example of Atlassian totally deprioritizing a simple win that would remove a major annoyance. How hard could it be to add an admin checkbox to disable this feature and they won't even keep the feature open. I have such a love/hate relationship with Atlassian and their forever-ignored-bugs. 

Paul M Sorauer July 31, 2018

It's a feature not a bug... :P

Like Jesus Oros likes this
0 votes
Krzysztof June 2, 2015

Hey,
it worked, thanks a lot @Jake Fisher

Greetings

0 votes
Simon Kegel //SEIBERT/MEDIA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 20, 2014

Hey there,

this option should be in the Misc Workflow Extension Plugin if I'm not mistaken, get a trial and see yourself smile
It should be definitely be able with ScriptRunner and a little bit of scripting.

Hope this can help.

Greets
Simon 

0 votes
Malik Graves-Pryor March 9, 2014

As a note, I've seen these issues recorded over the past 1.5 years:

https://jira.atlassian.com/browse/GHS-8770

https://answers.atlassian.com/questions/156616/suppress-update-parent-issue-pop-up

https://answers.atlassian.com/questions/100653/how-to-prevent-the-update-parent-dialog

However I haven't seen anything else so I'm hoping something has come up to provide resolution and it wasn't tracked, or someone has developed a plugin that can do this.

Suggest an answer

Log in or Sign up to answer