Automation rule - conditions

[Alex Shirokov]

Hello, 

Guys, I created a simple rule that we the user create a subtask it takes the status of the parent. So when the parent is in the "In progress" or "In testing" the newly created subtask should take the same status as its parent. 

I did it this way:

1. Trigger - issue created 

2. Issue type equals - Subtask

3. Then: Transition the issue to - Copy from Parent

Everything works great. The only issue is that when the parent is in the To do status I'm getting a failed automation rules notification. I tried to create an additional condition when the parent is in the "To Do" do nothing but... I cannot figure it out. 

Can you suggest how to do it?

Thank you, 

[bmccoy · Accepted solution]

Hi!

Not sure if you have already tried this, but we do have the 'related issues condition'.  It allows you to check things against the parent ticket.

Cheers,
Brydie

[Dance.makatuuk]

hello guys,

would you like to given how to create the rules:

Task progress with series model, second task can't progress when the first task already completed/done. and then continue to next task

[Stefan Salzl]

Hi @Alex Shirokov ,

could you check the workflow scheme? Regarding the description my first guess would be that parent issues are using a different workflow (thus: status) than subtask. Therefore it might be that subtask could not be transitioned to that specific workflow status.

In case they are using the same WF please add a screenshot of the error message from the audit log as well as a screenshot of your WF.

Best
Stefan

[Alex Shirokov]

Hi @Stefan Salzl 

100% we are using the same workflow for both issue types. 

There are some conditions applied to the workflow to restrict users to go back on the issue lifecycle. Only managers could move the issues left. 

Thank you!

Please find the screenshot from the audit log:

[Alex Shirokov]

@Stefan Salzl 

Stephan, 

I did screenshots of the workflow part:

Please note the in first and the second transition from "to do" to "in Progress" every project member can transition issues.

[Stefan Salzl]

Hi @Alex Shirokov 

Could you please share your screenshots in a clean manner? (I guess issue names and/or status names are not sensitive data). This would make anylaze a lot easier for the community.

Furthermore could you please also add a screenshot of your whole automation rule and also the action that processes the transition?

Best
Stefam