Automation Rule Failing

[Devin Holland]

Can anyone help me understand why the second condition is failing when it's basically written the same as my first condition? 

[Tim Kopperud · Accepted solution]

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())

TimK.

[Tim Kopperud]

Hi @Devin Holland, thanks for accepting the answer. I'm really glad the suggestion helped. 

TimK. 

[Bill Sheboy]

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?

Kind regards,
Bill

[Darryl Lee]

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!

[Devin Holland]

I ended up using your suggestion of using ELIF block. Changed to issue.created.shortTime and i had success. Thanks for your assistance.