Hi,
I was using the {{triggerIssue.fixversions.name}} smart value last week and it was working without issue but when trying to use the same automation rule today the rule is failing.
To test this I have set up a simple rule which logs the fix version but it doesn't seem to work whether I am using {{triggerIssue.fixversions.name}} or {{issue.fixversions.name}}. Other fields seem to be able to be accessed without issue.
I have checked the following page and have capitalised the "V" in versions to match and it still doesn't work:
https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/
Does anyone know if the accessing of the fix versions value has changed in the last few days?
Thanks
Dan
@John Funk @Jack Brickey Thanks for your responses.
I have double checked this morning and this was a mistake by me; it was a data issue causing my problem, not a system issue.
Apologies for wasting your time, it was a long day yesterday!
Hey Daniel,
Can you share the trigger that you have?
And are you getting an error? Or it just isn't returning anything?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
have you tried to use the action "log action" with {{issue.fixVersions.name}} to assess what Automation is actually interpreting? I gave this a quick try and it seem to work out OK.
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.