Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

I am trying to create an automation using for each branch using a custom filed from discovery

Deleted user August 21, 2024

 

I am trying to create an automation using for each branch using a custom filed. The automation catches that change but doesn't take the action of creating a task as required 
when I tried removing the branch it worked but that doesn't serve my need to create a task with different details based on the filed  input 
image.png

image.png

3 answers

1 accepted

0 votes
Answer accepted
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 21, 2024

Hi @[deleted] 

Change your rule to use an IF/ESLE condition

In the IF use the JQL as in the first branch and the action, and in the ELSE the JQL from the 2nd branch and the related create action.

Deleted user August 21, 2024

Hello @Marc - Devoteam I would normally use if else but actually I will include more than 2  cases 

Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 21, 2024

HI @[deleted] 

You can create multiple ELSE options, if/else is not bound to 2 actions.

But if you want to use branches, be aware they run in parallel, and use the JQL option,

Start the JQL with key = {{triggerissue.key}}

But best practice is IF/ELSE

 

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 21, 2024

Hi @[deleted] 

Would you please explain the problem your rule is trying to solve?  That is, "why do this?"  Knowing that may help the community to offer better suggestions.  Thank you!

Kind regards,
Bill

0 votes
Nikola Perisic
Community Champion
August 21, 2024

Hello @[deleted] 

I've replicated the same automation rule as yours, but I haven't included the additional branch. I've recommend to create two separate automation rules for Journey and Partners as well.

Screenshot 2024-08-21 at 10.15.25.png

Also for the Dependency Team trigger, have you checked for which operations it will trigger. It should be set to any operation,and also for a Change type see if its for any change that has been made.

As a final result:Screenshot 2024-08-21 at 10.18.47.png

Additionally, you can use IF/ELSE condition, much simpler than the FOR branch.

Deleted user August 21, 2024

Hello @Nikola Perisic  thanks for ur detailed answer 
I have the filed update trigger for added value and for edit only can this be an issue ?
I tried using it for all operations but instead it created issues for all discovery ideas that had the filed not empty 
I will also include more than 2 cases I was just testing 

Nikola Perisic
Community Champion
August 21, 2024

Hello @[deleted] 

Try updating the trigger that applies to all of the operations and then test it again.

Deleted user August 21, 2024

I did still not working 

Nikola Perisic
Community Champion
August 21, 2024

Make sure that the issue that you have created had either one of the checkboxes actually been checked as well, then  validate it with the JQL that you have defined it. Make sure that you are not doing in the automation rule.

Deleted user September 5, 2024

I used if else after asking jira ai to create the flow for me it worked thanks a lot 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events