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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,551,938
Community Members
 
Community Events
184
Community Groups

How do I write Version name filter for action Version released in Jira automation?

When I release Unreleased version, I want all tickets in that version to be transited to status "Deployed" automatically.

When trying to set it in Project automation I am getting an error:

Error

  • The rule has been configured with components that require issues to be provided by the trigger. To run these components you must add a branch for this version or JQL. The following components require issues: Transition issue

with comment below:

Execute this rule when a version is released. You can access the version object in other components by using the 'version' smart value e.g. {{version.name}}Screenshot 2020-04-15 at 14.13.29.pngwhat should I put in Version name filter.

2 answers

1 accepted

4 votes
Answer accepted
joehardin
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.
Nov 12, 2020

Old thread, but the problem with your rule is that the "transition the issue to" is referring to just that: an issue (and not a version). 

Instead you need to keep the same trigger, but instead of the transition action, you need to use the "branched rule / related issues" component. Within the branched rule select "issues fixed in version" then add whatever action(s) you'd like to occur after that.

Joehardin, thank you! 

Very not native from jira to make it this way

Like John Funk likes this

is there any way to perform an action on "linked (cloned by) issues" of those "issues fixed in version", regarding the same automation trigger?

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 23, 2023

Hi @Johannes Huber  - Welcome to the Atlassian Community!

You should always start a new question so more people will see it and can help. And answers can be tailored to your specific situation. 

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 23, 2023

Yikes! Thanks for updating. I responded to the link above. Let's see if we can generate some activity for you. 

I've got exactly the same question for the same user case

Suggest an answer

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

Atlassian Community Events