How to sync the status of newly created issue with the parent?

[Alex Shirokov]

Hello experts, 

I have a parent (Epic) and let's say it is in the status "In progress". When I'm going to the Epic and creating the child issue "Task" it takes the status "To Do". Can I somehow transition an issue to the same status as its Parent? 

I tried an automation rule:

Trigger: Created issue

Condition: issue type: Task

Branch: Epic parent

Action: transition the issue (copy from Parent).

and nothing works! 

Or does it relate to a workflow part?

Thank you! 

[Ilya Stekolnikov]

You can do it by using Scriptrunner plugin. But you will need some groovy script for that.

On Create transaction you can use move in posttfunction. And also there you will write your logic (something like - If parent status = In progress - make a transaction)

[Alex Shirokov]

Thank you Ilya, 

I wish my client would have the ScriptRunner. 

While reading your email I was thinking maybe I can do it via "if" condition in the rule? 

[John Funk]

Hi Alex,

Take a look at the first example in the common use cases for Automation for Jira.

https://www.atlassian.com/software/jira/guides/expand-jira/automation-use-cases

[Alex Shirokov]

Thank you, John, 

I'm afraid it is not my case. I have a rule that moves all tasks (issue type) with the parent. I need to make sure that the new issue I created will land up in the same status as the parent. 
Thank you, again

[John Funk]

What status is the Epic transitioning to?

[Alex Shirokov]

It can be any of three: To Do, In progress, Delayed. When it is in To-Do then it is fine since the new issue will land there but when it is in In progress or in Delay then ... I need to solve it. 

For example: the Epic (in my case it serves as a "project") is in Delayed. The user will create a Task (let's call it Risk related) from the Epic as a child. Therefore this newly created issue should land up in the same status as an Epic (parent). 

Thank you

[John Funk]

The problem with Automation doing this is that currently there is not a way to trigger a rule based on the Epic Link field being updated. So it doesn't know that a link was made. 

So, you might experiment with something like this: