nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Set date with lookup table and automation

Lana Kelly

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.

Screenshot 2023-09-19 at 10.53.12.png

Screenshot 2023-09-19 at 10.53.28.png 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!

Accepted answers

Tessa Tuteleers

Hi @Lana Kelly ,

A couple of things I notce without actually running the rule:

You need to call on your select field like this:
{{issue.fields.Mitigation due}} -> use the actual name with spaces and all
Your value is composed wrong:
{{now.plusDays(1)}} -> do not forget the "."

Please try these adjustments, it should work then.
Hope this helps!

- Tessa

All comments

Tessa Tuteleers

Hi @Lana Kelly ,

A couple of things I notce without actually running the rule:

You need to call on your select field like this:
{{issue.fields.Mitigation due}} -> use the actual name with spaces and all
Your value is composed wrong:
{{now.plusDays(1)}} -> do not forget the "."

Please try these adjustments, it should work then.
Hope this helps!

- Tessa

Lana Kelly

Hi @Piet Pieters

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!

Tessa Tuteleers

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

Bill Sheboy

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud