Hello,
More questions on automation lookup tables.
I am trying to create an automation that sets a due date based on a custom field duration chosen by the user. The custom field is a single choice selector, and here is the automation I have so far.
The audit log says that the get command isn't actually pulling anything, so there's something in the syntax I obviously don't understand.
Any help you could provide would be great, thank you!
Hi @Lana Kelly ,
A couple of things I notce without actually running the rule:
Please try these adjustments, it should work then.
Hope this helps!
- Tessa
Thanks so much for your help. I had originally had the . but didn't have the space for the field part. It worked perfectly once I added that. Thank you!
It's so confusing, because some fields don't have the spaces (affectedVersion and dueDate, for example), so I was going off the documentation I could find. Thank you again for your help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Lana Kelly ,
those are jira fields (not custom fields), they often have a different notation, it is indeed confusing!
If the answer helped, please mark it with "Accept answer", this way, other users having a similar question will find the solution faster.
Have a great day!
- Tessa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Lana Kelly
Yes, and...to Tessa's answer:
Smart values are name, spacing, and case-sensitive, and so it can sometimes be unclear what to use in rules for a field. To find the smart value for a field, and if it is supported by rules, this how-to article can help. Essentially you find an example issue with your field, call a REST API function with a browser, and then search for your field to find the smart value.
https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/
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 @Bill Sheboy I'm sure that will come in handy in the future. It seems I'm doing Jira configs every day!
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.