Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Automation for Jira - Server Plugin Closing out Parent task when creating Sub-task

Pretty much what the title says. I have automation set up so that when a field value changes, a sub task for the issue in which the field was changed is created, and an email sent.

Both things happen as advertised, however the Parent issue for which the sub-task was created gets its Resolution put into Done. The Status is still In Progress, just the Resolution changes.

I don't see how to prevent this. Anyone else seen this? Have any ideas how to avoid it?



2 answers

1 accepted

0 votes
Answer accepted

Darryl you were right, had nothing to do with the automation. Nic had an answer in a different post... it was screen related. My mistake..

Darryl Lee Community Leader Dec 10, 2020

Interesting! Yeah, based on what you shared about Scriptrunner, I was going to ask if the behavior still manifest if you disabled the Automation.

Glad you found the fix. There's a reason Nic is a top-answerer!

Hi @lukec 

Have you checked your workflow to see if something else is setting the resolution?

What does the individual issue's log indicate about who/how the Resolution was set?

Best regards,


Thanks @William Sheboy , 

The only transition that modifies the resolution is when it goes to the Done status, as a post function.

But using the automation for jira plugin, if the issue stays in To Do status, or In Progress status.. and does not transition thru the workflow, the resolution is still changed when that field value is modified (thereby kicking off the automation). 

The log shows that I marked it as Done, as seen below: 


Luke C made changes - 09/Dec/20 4:39 PM

Field Original Value                                            New Value
                                                     Product categorization Parent values:                                                                                   Security(13076)Level 1 values: Incidents(13162)
                                                     Resolution Done [ 8 ]

Darryl Lee Community Leader Dec 09, 2020

Hrm, that log entry makes it look like Automation isn't involved at all. (If it was Automation editing the field, I think it would show up in a separate entry.)

Could it be a ScriptRunner Listener?

Like lukec likes this

Thanks @Darryl Lee 

I looked at the ScriptRunner Listener (I only have one set up) it just looks for SSNs, this test issue I made doesn't have anything resembling a 9 digit number. Here's the log from the plugin:



So ticket 257 is the parent.. 258 is the sub task that was created, and shows up on the parent ticket. But 257's resolution gets marked as Done when it shouldn't. Again it doesn't even move through the workflow at this point. All I'm doing to activate this automation is change a field value. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Atlassian Automation

Jira Automation: Sum Up Story Points Roundup (Initiatives -> Epics -> Story/Tasks -> Subtasks)

Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...

1,846 views 2 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you