The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

automation checking for more than one condition

Colleen Cosgrove
July 22, 2024

I have set up automation that if a version is released, all tickets with that fix version  in state of resolved get marked as closed.  i would like to add an additional condition that they don't also have a fix version that is unreleased.... so if a ticket is fixed in version 1.1 and 2.1 but only 1.1 is released, it stays in resolved, when 2.1 is released it would move to closed. Any help in writing that condition?

What I currently have is attached... I want to add for issues fixed in the version if they have any other fix versions that are not released then transition

Screenshot 2024-07-22 at 6.27.33 PM.png

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Trudy P Claspill
Community Champion
July 22, 2024

Hello @Colleen Cosgrove 

Welcome to the Atlassian community.

Whenever asking for help with an Automation rule, it will help us to help you if you provide screen images showing us the complete automation rule.

It should be as simple as adding this condition:

Screenshot 2024-07-22 at 2.52.02 PM.png

Colleen Cosgrove
July 22, 2024

I added to the original description

 

Trudy P Claspill
Community Champion
July 22, 2024

If you add the condition I showed as another condition in your branch that should address your need.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events