I have an automation rule to update a custom field based on the issue type. I have several issue types that work correctly but one that does not, even though it is set up exactly the same as the others.
The error I get in the audit log is: The following issues did not match the condition:
It only seems to fail for the last issue type on the list of automatic updates.
Any ideas?
@David Kott please provide more context to your problem: What type is that custom field? Is it the same with the other? How do you set up the value? Did you place a log component to check the value of the condition?
The custom field is just a Select List (single choice). It is the same field that is used for the others.
How would I place a log component?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
With smart values and by reading this:
https://support.atlassian.com/cloud-automation/docs/debug-an-automation-rule/
Basically you want to search why your automation failed to pass that check. So log the value of the field you are checking. Run the rule and then check the audit log.
Crosscheck the value you are getting from the log, with the actual value of the condition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok. I added the following:
Custom Field is {{issue.customfield_13006}}
and ran the rule. Still didn't work and didn't get any notification in the audit log.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@David Kott without seeing the rule I can't help you any more. Can't tell where you've placed the log.. Most likely the rule didn't went that far to run the specific component. Try adding the log before the condition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hold on... you have a condition about the issue type being equal to "SDA CCR". And your rule doesn't pass this condition, meaning that the issue which trigger this rule, is not of that specific issue type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The project ended up not being used so it is a moot point. Thanks for you help, though.
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.