Our team is counting the amount of times an issue changes status using custom field "Number of Status Changes". Below counter is executed whenever the status changes but is not set to 0 when new issue is selected. Custom field counter keeps incrementing which assigns subsequent issue activations with a starting value higher than 0.
Thanks in advance.
{{#increment}}{{issue.Number Status Changes}}{{/}}
Setting default to zero is working. Thanks again for your assistance.
Context is important for automation rule questions...
Did you get this solution approach / rule from a template or help article? If so, please describe that.
When does this problem happen: for all created issues, for cloned issues, etc.?
And, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, and an image of the audit log details showing the rule execution. Those will provide context for the community to offer ideas. Thanks!
Until we see those...
I hypothesize you are either missing a default value for your field, as John suggests, or your rule does not properly detect the initial conditions (i.e., new versus cloned issues), and so just increments.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the response. I will try setting default to 0.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tyrone,
Do you have a Default value of 0 for the custom field? Try adding that and see if it solves the problem for new issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.