Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Comparison of two field values ​​"before" and "after"

Nikita Mukovozov June 6, 2025

Hello everyone!
I have an auto rule that when creating a task sends a web request with the Order field value (customFieldId=11200) with a value from 1 to 4 and with the SDTicket label

Some tasks do not fall under this rule because the Order field or label can change while working on the task

I want to make a rule that will send the same web request, but when the Order and Labels fields change, but I'm stuck on the conditions:

When changing the Order field (custom Field=11200) it took a value from 1 to 4, but before that it had a value from 5 and further

When changing the Labels field it took the value "SDTicket" (it is possible with other labels), but before that it did not have such a label

It should work in both directions:

If the Order was between 1-4 and did not have the "SDTicket" label and it was added, then the web request is sent

If labels takes the value "SDTicket", and before that it did not have such a value and before that it already had Order 1-4, then the web request is sent

Now my rule works like this, for example:
The task has Order 1-4, the "SDTicket" label is added - a web request is sent, but if something else is added to the labels, the web request is sent again and I want to fix it

I would be grateful for any help

Снимок экрана 2025-06-06 141242.png

1 answer

0 votes
Jaime Escribano
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 6, 2025

Morning @Nikita Mukovozov ! Hope you are having a lovely day.

Check out this documentation on the "fieldChange" smart value:

 

The changed field value will be available anywhere smart values are supported using the {{fieldChange}} substitution. Use {{fieldChange.fromString}} and {{fieldChange.toString}} to access display values and {{fieldChange.from}} and {{fieldChange.to}} to access raw values (for a select field for example).

{{fieldChange}} will only contain the first changed value. If multiple values are changed (e.g. when setting multiple Fix Versions) then you can iterate over these using the {{#changelog.fixVersion}}{{toString}}{{/changelog.fixVersion}} expression.

 

 

If I understand correctly you want the webhook to trigger whenever the values are changed and they used to be eligible for your rule.

 

In that case you want to have the value changed trigger and add a conditional that checks for if the value that has changed used to be eligible.

 

For this, use the conditional "smart value condition" which will allow for you to check if the {{fieldChange.fromString}} <= 4

 

If you need some more help let me know and ill try getting a prototype toguether in a few hours!

 

Regards,

Jaime Escribano

 

 

 

 

Nikita Mukovozov June 6, 2025

Доброе утро  @Jaime Escribano  !

Yes, I read this documentation for the "Field value changed" trigger

I need the webhook to fire once when the conditions match, for example:
The task already had Labels - "SDTicket", but the Order was 7. The order changed to 3 - the webhook fires
The task already had Order 2, but Labels "SDTicket" were added - the webhook fires
The task had Order 10 and did not have Labels "SDTicket". The order changed to 4, Labels "SDTicket" were added - the webhook fires

Also, I don't have the "smart value condition" condition

Снимок экрана 2025-06-06 150553.png

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 6, 2025

Hi @Nikita Mukovozov 

Please try the Advanced Compare Condition.

That is the original name of the condition.  It was renamed in Jira Cloud to "Smart Values Condition" a while ago.  @Jaime Escribano was using the name from Jira Cloud rather than for your Data Center version of automation rules.

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer