nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JQL AFTER -1d stopped working?

Bud Herz_4dzuwt

I have two automations that helped me notice one has stopped working correctly:

#1) This reports in Slack immediately for a Status change to three specific statuses
UAT READY
UAT DONE
CLOSED

^^ This is working fine.

#2) This reports in Slack daily with a summary count for the previous 24 hours of tickets reaching those statuses.

^^ This has recently stopped reporting correctly. It's report never matches the manual count from Automation #1
This is the Query that used to work, but recently stopped:

issuetype in (Bug, Story, Task) AND status in ("UAT-DONE", "Closed", "UAT Ready") AND status CHANGED TO ("UAT-DONE", "Closed", "UAT Ready") AFTER -1d ORDER BY status ASC, updated ASC

Any ideas why? Have I missed some new thing I need to update? I haven't found anything yet.

Accepted answers

Bill Sheboy

Hi @Bud Herz

I do not have a specific answer to why the counts are different, and I wonder...

The AFTER expression with the CHANGED operator uses a date value only, and there is nothing documented about the time part. I wonder if the time zone is causing the differences in which date is used.

If you examine examples of specific issues for each query, and where they are different, that may help to identify the cause.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Bud Herz

I do not have a specific answer to why the counts are different, and I wonder...

The AFTER expression with the CHANGED operator uses a date value only, and there is nothing documented about the time part. I wonder if the time zone is causing the differences in which date is used.

If you examine examples of specific issues for each query, and where they are different, that may help to identify the cause.

Kind regards,
Bill

Bud Herz_4dzuwt

Thanks @Bill Sheboy

Maybe there's been a change around the timezone and I just haven't found it.

As a further explanation:
We had three issue yesterday that the query should have reported at 9:00am EST
They all fell within the window as written, but it it reported zero issues.

I adjusted the query to this and it reported one of the three. Which is still not correct:

issuetype in (Bug, Story, Task) AND status CHANGED TO ("UAT-DONE", "Closed", "UAT Ready") AFTER -1d ORDER BY status ASC, updated ASC

I will keep picking away at this, but maybe posting here will help someone else.
Thanks again

Bud Herz_4dzuwt

@Bill Sheboy Sharing with you because you're the GOAT. I'm not sure if my situation is some how unique, but FYI - I've noticed the query will only return results from today.

So what before would report from 9:00am EST to the previous 9:00am EST will now only report 9:00am EST back to 12:00am EST (the start of the same day).

Bill Sheboy

Interesting...I just did a quick test and did get AFTER to work with hours, such as:

project = ABC AND status CHANGED TO "In Progress" AFTER -24h

This was for a clean, Jira Cloud, Free License site which was never converted (i.e., such as from Server or Data Center).

Perhaps try that version, adjusting the hours value to dial-in and observe what is happening and what the JQL finds.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud