Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,556,100
Community Members
 
Community Events
184
Community Groups

Automation for Version Release Trigger

Johannes Huber
Johannes Huber May 17, 2023

Hey guys,

right now I try to find a way to create an automation for the following:

Everytime, a version (in project: SCRUM) is released, I want to check each single issue of this version if its status is done and if so to set its related (is cloned by) issue (in project SUP) to done.

How can I do this?

Kind regards,

Johannes

Answer
Watch
Like Be the first to like this
415 views

1 answer

0 votes
John Funk
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.
Become a leader
May 23, 2023

Hi Johannes,

Can you post the rule that you have so far and what is not working with it? 

View More Comments
Johannes Huber
Johannes Huber May 24, 2023

Hey @John Funk , thank you very much for the quick response.

 

The problem so far is, that for my understanding I have to combine two branches:

1. for adressing the issues in the current version from my trigger "version released"    

     therefore I used either the "for issues fixed in version" branch or a "for JQL" branch,          both seemed to work.

Screenshot 2023-05-24 090311.png

 

2. for adressing the related (is cloned by) issue in another project.

Screenshot 2.png

 

 

Unfortunately after creating a branch,within this I can just create an action or a condition, but not another branch.

Is there a way to create this kind of rule?

 

kind regards

Like
John Funk
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.
Become a leader
May 24, 2023

Okay, if I understand it correctly, you probably want to use lookupIssues instead of the first branch. Then use the values returned from the lookupIssues in the bottom branch. 

Like
Johannes Huber
Johannes Huber May 24, 2023

I tried this, but an error occurred:

Screenshot 3.png

 

Screenshot 4.png

Can you help me with that?

ALSO: In case of using lookupissues, what can I do to look up fore more than 100 issues?

Like
Johannes Huber
Johannes Huber May 30, 2023

@John Funk Could you help me again, please :) ?

Like
Reply

Suggest an answer

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

Atlassian Community Events

See all events