Hi Team,
Automation rule to update a field "Risk In Days" every 24hours after a field named "At Risk" updated to Yes.
Project name: CPB
Issue type: Yes
There are 2 automation i implemented,
1) to update "At Risk" to Yes, when CPB's Story transtioned to On-Hold/Blocked status
Here We have updated the "Risk In Days" to 0, and "At Risk Start Time" to {{now}}
2) to update "Risk In Days" every 24hours after a field named "At Risk" updated to Yes.
used below JQL:
project = CPB AND issuetype = Story AND "At Risk" = Yes AND "At Risk Start Time" IS NOT EMPTY
can you help us to resolve this issue.
Hi @Anitha R Nair -- Welcome to the Atlassian Community!
There are two problems with your rules and fixing them may help:
Your first rule performs multiple edits of the work item. When a rule uses the edit action, that updates the cloud data, but not what the rule currently has stored in memory. And if your fields are dependent the values will not be what you expect.
I recommend combining all three of those edits to a single one, updating all three fields at once. (The other approach is to add the Re-fetch Work Item action after each edit, but I would not recommend it for this scenario.)
In your second rule, you are using the field name as the smart value. However, smart values are name, spacing, and case-sensitive...and they often do not match the displayed field name on the pages. Please use this how-to article to identify the correct smart value (or custom field ID) for your field:
https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/
Kind regards,
Bill
Hey @Anitha R Nair
If your automation is looking on issues under status On-Hold/Blocked, and you have set the "Risk In Days" to 0, why not just increment it every day?
for example:
{{Risk In Days}} + 1
This will increase the counter.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Anitha R Nair , working from memory here...give this a try
{{issue.At Risk Time}}.diff(now).days}}
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.