Forums

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

Auto assign rule not running as per the JQL?

GY July 24, 2020

What JQL should I use, so that issue should get auto-assign from 4:00 am CT to 1:00 pm  CT. I am using below JQL but issues are not getting auto-assigned from 4 am ct to 1 pm. it gets auto-assigned from 10:30 am ct and continues after 1 pm which should not happen.

created >= startOfDay(4h) and created <= startOfDay(13h)

created >= startOfDay(-1h) AND created <= endOfDay(8h)

GMT(-6) Chicago  is the default time 

1 answer

0 votes
Jack Brickey
Community Champion
July 24, 2020

Ganesh, I assume you are using some form of automation to action on the JQLs, correct? JQLs by themselves simply return results of the query. Now you indicate that your system time is set to CST but you should check to be sure (settings > system > general). Your first query should return issues created from 04:00:00 to 13:00:00 or 4am to 1pm which aligns with your goals. If you search for issues using this JQL and analyze the results do you see any issues that contradict this?

GY July 24, 2020

JQl gives correct data which is from 4 am to 1.pm CT . I am using project automation for auto assigning issues. I checked the time it's GMT -6 Chicago. Issue is the auto assignment of issues gets triggered at 11.30 am which should not happen it should trigger at 4 am to 1 pm as the the jql.

Jack Brickey
Community Champion
July 24, 2020

can you please provide the details of your automation? this seems to be a timezone issue.

GY July 24, 2020

So all the issues which will get created from 4 am CT to 1pm CT should get auto assigned to team member in round robin format. It's getting auto assigned but at 11.30 am and not getting auto stopped at 1 pm

Suggest an answer

Log in or Sign up to answer