Automation rule Field value UNCHANGED
Asked by Jan ?imek:

Hi I would like to ask if anyone know about workaround for automation, when I have custom field, which needs to be monitored for changes.

In one status if the field is changed it then transition the issue to another status.

But I need to setup a automation rule, which will be triggered by me not changing field value, but only simply commenting on issue.

The scenario is this:

We are adding charts to our cases from past to see, what profit we have made on each case. If the field is not updated, that means there was no profit and I simply only add empty charts in comments, which I want this automation to sent issue to FInal status.

There can be also scenario, where I comment on issue and the fields are changed, in which case the issue remains in current status.

Unfortunately I have not been able to find a way ho to achieve it.

I could easily every month change current fields and the automation would trigger, but since the values are overall per all months, it makes no sense at all tbf.

This is current rule, which i know is not correct, because it works only with values which are the same as in automation.

Can someone help?

Thanks![Sn?mek obrazovky 2023-03-06 134359.png](/t5/image/serverpage/image-id/243971i930B14C385844111/image-size/large?v=v2&px=999 "Sn?mek obrazovky 2023-03-06 134359.png")


Answers:
author: Alex Koxaras _Relational_
body: ?? [@Jan ?imek](/t5/user/viewprofilepage/user-id/4837318)

I read your post twice and still haven't figured out exactly what you want to accomplish, other that you want your rule to be triggered via comments. So based on your scenario:
> We are adding charts to our cases from past to see, what profit we have made on each case. If the field is not updated, that means there was no profit and I simply only add empty charts in comments, which I want this automation to sent issue to FInal status.
>
> There can be also scenario, where I comment on issue and the fields are changed, in which case the issue remains in current status.

If the fields (total minutes \& total profit) are not updated then the issue must be sent to the final status. But if the fields are updated, then the field must remain on the same status.

Is my above statement correct?

comments: author: Jan ?imek
body: Hi [@Alex Koxaras _Relational_](/t5/user/viewprofilepage/user-id/4150197)

I might have been too overdetailing all of it.

But yes, your statement is correct.


author: Alex Koxaras _Relational_
body: [@Jan ?imek](/t5/user/viewprofilepage/user-id/4837318)

Imo the automation would occur if the fields had changed and not the opposite. In your case and since the fields are not changed, then I would simply transition the issue manually.

However if you really really really really **really** want to transition the issue when you paste images without changing the fields then you could do the following rule:

![comment rule.png](https://community.atlassian.com/t5/image/serverpage/image-id/244078i0922EF6C3CD6E7FD/image-size/large?v=v2&px=999 "comment rule.png")

Searching for the comment containing the string !image- is equivalent of searching for an image within a comment. The response of an issue as JSON returns the following:

![json comment.png](https://community.atlassian.com/t5/image/serverpage/image-id/244079i56A8CB1BC67AB3DC/image-size/large?v=v2&px=999 "json comment.png")

I've tested it and it works if I paste just a single image. This rule will run even if you paste a image and write some stuff. Meaning you have to be very careful with it.

Imo, I wouldn't use it and I would stick to manually transition the issue, OR find another business requirement with which I could automate the procedure.


author: Jan ?imek
body: I have figured out the automation for it except for the imagine. Honestly I think that possibility do have automation rule where condition can be when nothing is changed should be added.


Tags: cloud

jira-work-management-cloud