Transition Parent Issue

[Matthew Oldenkamp]

We have JIRA Premium and I'm trying to use Automation to transition a Parent Issue when the Child issue transitions from one status to another.

Is there a way to do this? The Parent issue is on the same hierarchy level as an Epic.

[Aaron Brady · Accepted solution]

Hello Matthew,

Welcome to Atlassian!

There are three things to consider when creating an automation in using Jira Automation: triggers, conditions, and actions. 

Below is an automation rule I created and tested that allows you to use the status of a task/story to update the status of the parent epic. 

Hope this helps!

-Aaron

[Trudy Claspill · Accepted solution]

Hello @Matthew Oldenkamp 

I believe you should be able to do that with Automation for Jira. 

(Side note, your post is tagged to indicate you have the Standard version rather than the Premium version).

To get to the parent issue you would either use the Branch / Related Issue as shown below...

...or you would use a Lookup Issues action to look up the parent issue by getting its key from the Parent Link field in the trigger issue.

[Matthew Oldenkamp]

Trudy,

Thanks for the quick response. For some reason I couldn't change the tag to the Premium version.

I've tried that Branch style and it only works on Epics. Not on the issue that is linked via the "Parent Link".

Do you have a JQL query for looking up the "Parent Link" issue?

[Trudy Claspill]

don't have access to a premium environment where I can replicate this and prove out the JQL. You should be be able to use the field name for the field that contains the Issue Key of the non-Epic parent issue in the child issue. Something like this:

"Parent Link" = <parent issue key>

That assumes there is a field called "Parent Link" in the child issue and it contains the issue key for the parent issue. Can you show us an example of an issue that is linked to a "parent" that is not an Epic so that we can see the designation of the parent issue within that child issue?

[Matthew Oldenkamp]

@Trudy Claspill 

I tried your JQL query and it worked circled back to the issue that triggered the automation. The field called "Parent Link" looks like:

Doing some more testing I figured out the solution. I created a variable {{Parent}} = issue.Parent Link.

Then searched for in the Branch JQL 

Key = {{PARENT}}.

This made the automation work. Thanks for the help @Trudy Claspill