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

Exclude conditions for Item Updated automation

Dmitry Alabyan

Greetings, community!
I have an automation that triggers upon "Work Item Updated".
Problem is, I need to specifically exclude any status changes to the issue from the trigger.
My first thought was to use {{#changelog.status}}{{fromString}}{{/}} for every status in the workflow as an IF condition - but this one, if I understand it correctly, will be pretty much blocking any executions of the rule, since there will be a changelog in the first place.
Any ideas how to make the rule work in WHEN work item updated EXCEPT for status change?

Accepted answers

All comments

arielei

Hey @Dmitry Alabyan

Switch the trigger from "Work Item Updated" to "Field Value Changed" and add all the fields you want to monitor.

Dmitry Alabyan

that would not be elegant, since pretty much every other change is monitored
and there is a great number of fields

Dilip_ybbekx

Hi @Dmitry Alabyan

could you please elaborate more on your requirement?

also,I noticed you are eligible for 1:1 support as per your plan, feel free to reach out to Atlassian support here:https://support.atlassian.com/contact/

arielei

Hey @Dmitry Alabyan ,
So use another method:
1. Create a CF called "LastStatus" , could be short text field.
2. Create an automation that when you change the status - copy the value to that field BUT before copied set a delay time of 4 sec.

3. Then, when you run your automation, run a compare between the current status to the CF LastStatus.

This way, you'll be able to exclude status updates.

Bill Sheboy

Hi @Dmitry Alabyan

When a work item transitions, that is a different event type than for an update, and so your rule with the Work Item Updated trigger should not run.

Are you observing the rule run for a work item transition only, rather than bundled with other edits?

If so, please post images of your complete rule and the audit log details showing the rule execution for a work item transition. Those will provide more context for the community to offer help.

Kind regards,
Bill

Dmitry Alabyan

Problem is, Work Item Updated actually includes the status update transition.

It does not show it explicitly, the audit log just shows that the condition has been triggered. But we know through trial and error that the only thing changed was the status. Screenshot 2025-06-30 at 18.18.56.png Screenshot 2025-06-30 at 18.12.53.png

Dmitry Alabyan

@Dilip never tried discussing these questions with the support team to be honest. Is that within your scope?

Dmitry Alabyan

not exactly. if I understand the logic correctly - there still will be a triggered Work Item Updated case

Bill Sheboy

How are you updating the status of the work item such that it triggers the rule?

When I tested with a manual status transition (i.e., direct field edit or drag-and-drop on the board) the status transition does not trigger Work Item Updated...

However, with a drag-and-drop change on a non-empty board, the Rank field often updates, and that will trigger the rule. This can be confirmed by writing the entire {{changelog}} smart value to the audit log. And, that is a different event than the transition itself.

Dmitry Alabyan

hm. that's an interesting insight indeed.
so, what would be the correct expression to exclude ranking changes?

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

automation