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; } } }

Defining "Only include issues that have changed since the last time this rule executed"

Richard Stamp

Morning all

I'm attempting to setup an automation which executes a JQL search and edits tasks accordingly (flags/unflags issues based on set criteria). This works fine, this isn't the issue.

Execution time of this Automation is ~500, so obviously I want to bring that down - the checkbox on the rule states

"Only include issues that have changed since the last time this rule executed"

but it doesn't seem to catch everything, but does run significantly faster. Does anyone know the exact definition of "Issue Changed" in this context?

Accepted answers

Nic Brough -Adaptavist-

It looks at the "updated" date/time on the issue.

That is set by any action on the issue except ranking and being linked to by other issues (I can't remember if linking from an issue to another changes the updated date on the issue you create the link from, but it does not affect the issue being linked to). Attaching a file, edit, transition, comment, etc, all set the updated date.

All comments

Nic Brough -Adaptavist-

It looks at the "updated" date/time on the issue.

Richard Stamp

Excellent, thanks. I was worried it was monitoring specific fields and would therefore miss certain custom fields we use.

Thanks for the concise answer!

Nic Brough -Adaptavist-

np. I confess I don't know the exact rules about which changes do not hit the "updated" date/time, but I do know that any edit of a custom field always counts as an update (except for rank and sprint, which I think of as system fields, despite them being implemented as custom fields)

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