Problems with a Cron expression

[rob_brown]

I've inherited a Jira instance as an IT ticketing platform, and trying to kick some bits into a better place as an interim.

One of which is adding a scheduled reminder for when tickets haven't been touched for a few hours.

Principle logic is straight forward enough:

When: Scheduled

Using Cron: 0 0 10-16 ? * MON-FRI

Then: Add comment to work item

Which 'should' if 4 different cron generators are to be believed, trigger between Mondays and Fridays at the hours of 10:00, 11:00, 12:00, 13:00, 14:00, 15:00 & 16:00

Unfortunately, it's not working, and I'm at a loss. It validates fine in the rule builder, and currently tells me 7 work items found will meet the criteria. It just never seems to actually work.

Any suggestions welcomed!

[Marc -Devoteam- · Accepted solution]

Hi @rob_brown 

Your JQL finds 6 issues, but you also have the checkbox enabled: "Only include work items that have changed since the last time this rule executed"

This means the JQL finds 6 issues, that are conform the search query, but if those issues have not been touched (updated) since the last run of the rule, these issues are skipped.

If you want all issues to be executed on, disable this checkbox.

[rob_brown]

Lordy - I just wasn't seeing that at all. Talk about forests and trees!

Tested and working. Thanks!

[Staffan Redelius]

Hi @rob_brown and welcome!

I assume you are using Jira Automation to fire the CRON job?

Please paste a screenshot of your rule so it is easier for us to propose a solution (mask any sensitive data if needed). And also please add any information from the log for the automation.

Best regards,
/Staffan

[rob_brown]

I thought this was pretty cookie-cutter - but I'm obviously missing something or doing something wrong - just can't put my finger on what.

[rob_brown]

I should note that when I validate the query, it thinks there are 7 work items that match - but yet the audit log shows nothing actually happening!

[Staffan Redelius]

Hi,

It looks like you are using a smartvalue here: 

It doesn't look like it is the correct syntax if you are looking for the status "Waiting for 3rd party" it should be {{issue.status.name}} but it might be easier to add it to the JQL in the Cron.

I did a short test in my own sandbox configuring a rule that looks like this and it seems to do what you described (i set the JQL to just update Epics that are not done just to not mess up my installation).

I have not added the "send email" but that can easily be added.

Let me know if this helps!

Best regards,
/Staffan

[rob_brown]

Aah yes, I'd tried that as well - here's the reverted version:

As you can see, it thinks there's 6 work items found that it'll apply to - but yet when manually running it, the audit log comes back with nothing: