Issue did not match the JQL condition

Aamir_Aslam
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 28, 2024

Created an automation which would prevent duplicating predefined set of tasks for the specific columns if we accidentally jumped on to the wrong workflow column ... Am able to prevent the duplication by using the following JQL :
Status was not ... before now()

Screenshot 2024-04-28 203940.png

 

 

Its only creating problem when for the first time the issue enters into the desired  column where JQL is set and it doesn't let the Predefined tasks to load in the first instance .... the Following Error is shown

Screenshot 2024-04-28 204440.png

So I have to manually remove the JQL condition and then only my regular automation of loading the task will work for that column ..

Let me know what needs to be done as in one way its working for me by not duplicating the tasks but its creating an impediment to load the tasks to start with.....

1 answer

0 votes
Kseniia Trushnikova
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 29, 2024

Hi @Aamir_Aslam,

Try to use before -1m instead of before now().

Typically, executing a rule takes some time; now() at the time the rule is triggered and at the JQL check are different. The difference may be in milliseconds, but still.

Kseniia Trushnikova
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 29, 2024

Another way is to use before {{now.jiraDate}}:

status was not "XXX" before {{now.jiraDate}}

By default, now() returns value in date and time format: https://confluence.atlassian.com/automation/jira-smart-values-date-and-time-993924864.html

Suggest an answer

Log in or Sign up to answer