Forums

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

Set a field of a lookup issue in automation

Simone Pellegrini June 5, 2023

Hello, I need a way to change a field of an issue that I get in automation as a lookup issue. is there a way to do it? I can't use a branching rule cause I should nest it to do that.

 

My specific use case is that i have a service desk and I have an automation that duplicates the task in the service desk in my project where I have a custom kanban board with a backlog where I can manage how and when my devs should work on an issue. I want to close the issue on the service desk if the duplicated task on my project transitions to done. I have linked the issues to keep track of the original issue on my service desk. This should be an easy automation but I don't want to consume useless automation triggered by transition, cause I don't need the service desk to be always up to date and this creates a huge number of executions that can make me reach my automation limit, so I tryed to create a scheduled automation that look for all the issue in done on my board and set the issue from wich they are duplicated by on the service desk to done.

 

Everything is working fine but I cant set the status of the linked issue and I'm stuck right now. Here is a reference of my test automation: 

Immagine 2023-06-05 172225.png

Thanks in advance, 

Simon

1 answer

1 vote
Trudy Claspill
Community Champion
June 5, 2023

Hello @Simone Pellegrini 

You can incorporate the JQL in your first branch into the Scheduled trigger to select the Bug issues.

Then use a Branch For / Related Issues / Linked Issues branch to get the linked Service Desk tickets and operate against those within the Branch.

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.
June 6, 2023

Hi @Simone Pellegrini 

Adding to Trudy's answer...

As this rule will have multi-project/global scope, and you appear to be on a Standard license level, you will want the JQL for the trigger to be as specific as possible.  Otherwise this will use more of your quota of global rule executions than needed.

Kind regards,
Bill

Like Trudy Claspill likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events