Automation Rule Not Updating Field Count Beyond First Change

[Selvam A]

I have set up an automation rule in Jira to track how many times the "Acceptance Criteria" field gets updated during a sprint. The count is stored in a custom field called "Count."

While the rule works successfully for the first update (sets the count to 1), it does not increment or update the count for subsequent changes to the "Acceptance Criteria" field, even though the automation logs show that the rule runs successfully.

Could someone guide me on what might be causing this issue or how I can fix it so the count field increments correctly with every update?

Thank you in advance!

[Bill Sheboy]

Hi @Selvam A 

First thing, context is important for automation rule questions.  Please post an image of the audit log details showing the rule execution, for both the first update and a later one.  These will show if the rule is executing all the steps you expect.

Next, smart values are name, spacing, and case-sensitive.  When an incorrect one is used, that returns as null, often failing with no errors in the audit log.

Please confirm you have the correct smart value (or custom field id) for your field using this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Kind regards,
Bill

[Kai Becker]

Hi @Selvam A 

thank you for you question. Just to make sure. I think there needs to be issue.Counter in the smart value instead of issue.Count ?

If this still does not solve the issue I would try to split the rule into two parts. The first handling the initial setting of a value and the second part doing the increment, if the field is not empty.

[Selvam A]

Thank you @Kai Becker

I have changed to issue.Counter but it is not working.

[Kai Becker]

@Selvam A what type of field is the Counter field? Is it a number field?

Did you try my second approach?

[Selvam A]

Yes @Kai Becker

it is a number field and the second approach also not working ;(

[Kai Becker]

@Selvam A I just built this in my dev environment with a manual trigger and it is working as expected. Please review my screenshots:

First update:

Second update:

[Selvam A]

@Kai Becker 

Thank you for your time and effort. Its working fine now:)