You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi @Devin Holland, I think the rule can be simplified. You might try something like this:
With the JQL
(created > startOfDay() and created < startOfDay("8h")) OR (created > endOfDay("-8") and created < endOfDay())
Hi @Devin Holland -- Welcome to the Atlassian Community!
When performing date/time comparisons in automation rules using conditions, please check if the typing supports your intent.
Specifically, using things like longTime lead to a text expression. And so the compare no longer has the benefits of a date/time type to help. Will the converted text values correctly align with the clock time values you expect in the compare, with leading zeros and date components ordered as needed?
Hi @Devin Holland --
I think you're trying to catch tickets created between 5PM and 8AM CST?
So I believe the problem is that you didn't account for midnight.
That is, let's say a ticket was created at 6AM. That is definitely less than (before) 8AM.
But is it greater than (after) 5PM?
In our heads, yes. But according to the computer, no.
So I think what you really need is an OR operator for your comparisons.
At first I didn't think this was possible, but I played around with the IF, ELSE: add condition options component and figured out I could do ORs by choosing the "Run actions if... At least one condition matches" option! Cool!
I think this should work. Please let us know!