Closing sub-tickets after the main ticket was not approved

[Boehm_ Dominik]

Greetings,

im working on an automation which creates a ticket which needs to be approved and two linked issues. One of the issues is just created, if a custom field "Hardware required" is set to "yes", otherwise just one issue is always created.

Now i'm trying to edit the automation so that it closes all the linked "sub-ticktes" when the main ticket isn't approved. That way the other tickets will get closed aswell and aren't worked on.

So far i can't get it to work, since one issue is always created and one only, if a custom field is filled. Maybe you can help me find the correct path.

Kind regards

[Marc - Devoteam]

Hi @Boehm_ Dominik 

@Michael F Kelly Jr solution will work, but this gets all related work items/issues.

If it's related to sub-tasks only, use the branch on sub-tasks option.

[Boehm_ Dominik]

Thanks for the provided help!

When i create a branch which should affect all issues, nothing happens. I found the option myself but it seems i'm having trouble in figuring out where to put it. Also do i need to create a completly new branch? 

So far i created a new branch with the following options:

New branch for every issue: If status = Declined, then change workflow status to "Canceled" As shown in the picture. Which does not seems to work.

[Marc - Devoteam]

Hi @Boehm_ Dominik 

Can you show your complete rule (preferably in English) and where you have the issue achieving what you want?

[Boehm_ Dominik]

Hello Marc,

thanks a lot for your help and patience!

I created some screenshots of the whole Automation. I hope this helps you! 

I also created a test ticket to show you what happens. When i create a ticket, it asks for an approval. If i decline this approval, the two subtickets which are created should switch to the status "Decline" aswell. 

I hope this helps you out!

[Marc - Devoteam]

Hi @Boehm_ Dominik

So you need an automation rule that triggers based on the issue transitioning to declined and then branch out so all sub-tasks are transitioned to the declined status.

The rule you show is the create rule, as you explain this works.

You need another automation rule the triggers on the status change (as outlined above)

[Boehm_ Dominik]

Greetings Marc,

thanks so far for your help. Sadly i just had time today to work on the problem. I came a bit further and made progress.I created a new rule with a transitioning from "Waiting for approvel" to "Declined"

My problem now is, that i can't branch out anything, since the branch wants "One of the following elements must be created at an earlier stage, usually by the trigger or with a "For Each Element" branch, for this component to work:" to happen

I tried several alternatives and i can get it to work in a weird way, were two new tickets get created which transfer itself to my desired status but now i have 4 linked issues which doesnt really help, since the first two are still opened and can be worked on. 

[Michael F Kelly Jr]

related issues only actions the single last issue, use all created issues