Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Jira Automation: Related issues condition find linked issues from another project

David Leal
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 26, 2023

I was trying to use Related issues conditions and I realized that I am able to find linked issues from the same project on a given issue, but not when the linked issue is from another project. I found the following related question: Search for issues in other projects and automatically link them when at least one component matches and per the answer provided by @Bill Sheboy it will require a global/multi-project scope rule. 

I am wondering if there is no need to have a global/multi-project scope for that, This will require getting involved my Jira admin and then I cannot edit the rule, I would depend on a third party to edit it. It is very unfortunate that Jira Automaton has such limitations.

Thanks,

David

1 answer

1 accepted

4 votes
Answer accepted
Fabian Lim
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 27, 2023

Hi @David Leal

Unfortunately, you will have to get your sys admin involved.  Any time you are using a condition, branch, action, in another project it has to be a global configuration.

Regards,

Fabian

David Leal
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 27, 2023

thanks, @Fabian Lim I was able to find a workaround, I guess the only exception is the Clone issue action that allows me to clone an issue on a different project, so It took that approach, and then while cloning to set the values I wanted.

My initial approach was trying to look at linked issues after cloning the issue with one rule, and with a second rule to update the values for the cloned issue, but because I wanted to clone from one project to another the linked issue was from another project, so I could not find it. Now I have all the processes in a single rule, cloning and at the same time updating the fields from the trigger issue. Thanks

Screenshot 2023-08-27 at 4.57.37 PM.png

and for example to set the values as follows for bugs created in another project.

Screenshot 2023-08-27 at 5.10.47 PM.png

Like Fabian Lim likes this
Fabian Lim
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 27, 2023

Correct, as long as you are creating/cloning tickets in another project it doesn't need the global admin rule.  You only need to make sure that whoever is executing the rule (user/automation) has access to create ticktets in the other project.

Like David Leal likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events