When field is changed not working
Asked by Cindy Vel:

Hi,

Last week I created a few automation rules that were triggered by changes in priority, assignment group, short description or description, etc (One rule for each field). They were triggered when their particular value changed, and were working fine.

Today, none of those rules are triggered unless I change them to Issue changes (updated, transitioned, etc) and once I do, for example, a change of status, they do update. Only my automation rules that were originally set to field value changes are not working anymore, they don't even detect the trigger of change in the tickets that I create.

Just to clarify, no modifications to any other rules or new rules were implemented since last week, I'm wondering if someone is having this same issue or if there was an update that changed how this rules worked or are triggered.

Thanks in advance for any suggestions or info on the matter,  

Cin  

<br />

EDIT:

I raised a ticket with Jira and apparently it's an internal issue that me an other customers were having, and it should be fixed soon. Thanks for your suggestions!


Answers:
author: John Funk
body: Hi Cindy,

Maybe the rule is getting triggered as the result of a different rule? Can you check the Rule details to see if the box is check for **Allow rule trigger**?

comments: author: Cindy Vel
body: For the one rule that I showed below, that is not checked. I did checked it to see if that was necessary (just in case) but the result was the same, so I unchecked it again.

Some of the other rules that are also triggering with "When value field changes..." are checked but again, this wasn't a problem last week :( It only started to happen since yesterday.


author: John Funk
body: If it is not firing at all - even when the box is checked, then you need to open a support ticket with Atlassian for them to determine what is going on.

Please post back here with the resolution so future readers will know what's going on.

Good luck!

<https://support.atlassian.com/contact/#/>


author: Darryl Lee
body: Hi [@Cindy Vel](/t5/user/viewprofilepage/user-id/5240306) -

Maybe check your Usage to see if you've exceeded the number of Executions for your tier?

<https://YOURSITE.atlassian.net/jira/settings/automation#/tab/usage>
> Customers on Free and Standard plans have access to a limited monthly trial allotment of global and multi project rule executions (100 and 500 per month, respectively).
>
> Premium users have 1000 global and multi-project rule executions per paid user per month. Ex: 200 users in Jira Cloud Premium will have 200,000 monthly global/multi-project rule executions per month. This is pooled across all Jira tools and all users.
>
> Enterprise users have access to unlimited automation executions.

<https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/>

comments: author: Cindy Vel
body: Hi Darryl,

Sad to say but we are Premium users, I don't believe it might be that.

As I mentioned, all of our rules are executing as before and triggering as expected, only those triggered by Changes to field value are not working.


author: Tim Perrault
body: Hi [@Cindy Vel](/t5/user/viewprofilepage/user-id/5240306)

Have you checked the audit logs on the rules? Did that show any information on why they were not successful?

comments: author: Cindy Vel
body: That's the thing, it's not showing any error.

It's just not triggered at all. It doesn't detect any changes made on the fields.


author: Tim Perrault
body: Would you mind sharing a screen shot of the automation? Is the automation a global rule or project rule? Team-managed or company-managed project? Free edition of cloud?


author: Cindy Vel
body: Sure, please ignore the erased sections, it's just that project is company-managed.

But you can see that the trigger rule was working and executing itself correctly last week. Today, we realized it was not triggering at all, despite no changes made. I added extra conditions to see if that was needed but it still didn't trigger, only when I changed the trigger to updates in issue (updates, transitioned, moved, etc) it actually triggered the rule on what to do when the priority changed (that is, I had to make a change in the ticket status for it to be triggered). But when I revert it to just value changing for a specific field, it goes back to not detecting any trigger.  
![Screenshot 2023-06-20 142526.png](https://community.atlassian.com/t5/image/serverpage/image-id/264165i3C927ED4163E43BC/image-size/large?v=v2&px=999 "Screenshot 2023-06-20 142526.png")  

This is the same for all the rules I create that trigger only with the option of Value changes for (field). Every other rule is working fine, just like last week.

I even created a new one just to add a comment on the ticket if a field was changed, to see if it would trigger, but still, no trigger was even detected.


author: Tim Perrault
body: Could it be possible that the rule Actor lost permissions to the project?


author: Tim Perrault
body: Actually do you have other rules that this rule could be triggered by or trigger?


author: Cindy Vel
body: I don't think it's about the permissions. As I mentioned, the other rules are working fine and they have the same Actor, and those that don't work are fixed if I change to Issue updated rather than Value field changed (although a temporary solution, it is not ideal).

About the rules, this would only be affected if I check the "Allow rule trigger" box, won't it? The one with "Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule."

That box is not currently checked for the shared rule. Although I did check it to see if that was the issue, but it didn't trigger anyways :(


author: Tim Perrault
body: Yea honestly I'm just grasping at straws. I am at a loss for why the rule isn't triggering.


author: Cindy Vel
body: It is strange, we tried to replicate the issue in another project but it does get triggered in the other projects. It's just here where it stopped working.

If we had made any changes I'd have an idea but since it's a demo that we hadn't touch for the last couple days, the fact that it's not working now was weird, which is why I asked here, to see if maybe someone else had a similar issue, or maybe this could come from Jira.

Doesn't look like it's that either.


author: Tim Perrault
body: Hopefully others will be able to chime in and if all else fails maybe a support ticket with atlassian. Sorry I couldn't solve your issue. Good luck


Tags: atl-gruland