Forums

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

Automation problem

Niclas Moberg August 28, 2025

I need helt to set up an automation in Jira.

I've tried using gpt, gemini and Rovo for guidance, but none of them give me correct instructions 

I want "Version released" as trigger, and the following to happen.

In project "TES" (Jira service management) there is a work item which is cloned to project "TR".

When the fix version of the work items in project "TR" is released, I want the custom field "Version released" of linked work items in project "TES" to be updated with the text "Version released".

1 answer

1 accepted

1 vote
Answer accepted
Thorsten Letschert _Decadis AG_
Community Champion
August 28, 2025

Hey @Niclas Moberg ,

What you're trying to achieve is not trivial, since out-of-the-box JQL does not support nesting, and a function like linkedIssues() only matches against specific issue keys or a saved set of issues.

While using the Version released trigger enables you to incorporate an Issues fixed in version branch to select your TR items, this approach also lacks a needed nesting to select the TES issues from there.

That being said, I'd suggest/ask the following:

Is the act of releasing the version tied to a status change of your TR items in that version? If so, using that status change as a trigger might be a more convenient way of starting your rule, since you already have the correct items as context and just have to look for your linked TES items.

Regards,
Thorsten

Niclas Moberg August 28, 2025

Hi @Thorsten Letschert _Decadis AG_ 

Thank you for taking the time to help me.

At the moment, the process is not tied to a status change, but I will definately try your suggestion.

 

BR,
Niclas

Suggest an answer

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

Atlassian Community Events