Automation keeps affect tickets that already been changed

Anita Sudan February 23, 2023

Hi all,

I've set up an automation that adds a certain symbol to the ticket summary if the ticket's due date is in 2 days or overdue.

I need this automation to run everyday, so new tickets get affected, but I also don't want already affected tickets to have one more symbol added.

So far, unfortunately, the tickets that have been already marked, are still getting marked and I cannot figure out why and how to fix this.

I'd appreciate some help!

Thank you!

2 answers

1 accepted

0 votes
Answer accepted
Vamsi Kandala
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.
February 23, 2023

Hi @Anita Sudan

Welcome to the Atlassian community!

There are two ways to do this:

  1. Select the checkbox 'Only include issues that have changed since the last time this rule executed'.  This will ensure that the tickets which were already updated by the automation rule during the previous runs will not be affected and will not be updated again.
  2. In the JQL query which checks for the ticket's due date, add the check for 'summary' to see if it does not contain the symbol (assuming it is a character or string).  So, it will return only the issues which does not have the symbol in the ticket summary and due date is in 2 days or overdue

Hope this helps.

Thanks,
Vamsi

Anita Sudan February 23, 2023

Thanks Vamsi,

 

  1. 'Only include issues that have changed since the last time this rule executed' is checked, but doesn't work :( 
  2. the symbol being added is an emodji, so JQL doesn't work: returns 0 issues

I'm curios though why 'Only include issues that have changed since the last time this rule executed' is not working... 

Vamsi Kandala
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.
February 23, 2023

Hi @Anita Sudan

Sorry, it is the other way around.

Try unchecking that and see if it works.  Basically, checking this option is returning the same set of issues that were updated earlier.  So, it should be unchecked.

Hope this helps.

Thanks,
Vamsi

Like Anita Sudan likes this
Anita Sudan February 24, 2023

Got it!

Thanks!

0 votes
Content Authoring IBL
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 3, 2024

What was the automation. I would like to use that. Thanks in advance

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