Automation using lookup table

[Lyndl]

I am having difficulty creating automation using a lookup table. What I want to achieve is to separate the value from the lookup table into three different custom fields. I hope someone can help me, thank you.

[Bill Sheboy · Accepted solution]

Hi @Lyndl -- Welcome to the Atlassian Community!

Would you clarify your scenario a bit?  And have you looked at the articles describing this new feature of rules:

• https://community.atlassian.com/t5/Automation-articles/New-Automation-action-Create-lookup-table/ba-p/2311333
• https://community.atlassian.com/t5/Automation-articles/Update-Create-lookup-table-action-improvements/ba-p/2427798

From what you have described thus far, it seems you are trying to set the value of custom fields using a lookup table.  That could be done using the smart values to get() your value, such as with:

{{tblMyTableData.get(someKeyValue)}}

Where someKeyValue could be a smart value or a literal value, like "myKey".

If that does not help, please post images of your complete rule, images of your issue edit actions, and of the audit log details showing the rule execution.  Those may provide more context for the community to offer suggestions.

Kind regards,
Bill

[Lyndl]

Hello, @Bill Sheboy

This is what I'm trying to achieve. When you input a value into the postal code, it will retrieve the value I placed in the lookup table. Once it retrieves the value, it will split it into three custom fields (region, province, & city). Is it possible to accomplish this in Jira automation?

[Bill Sheboy]

Starting with your use of a lookup table, please see the information I provided as you do not appear to be using them correctly.  The way they work is:

1. create a lookup table
2. retrieve a value from the table using the get() function, passing your key value as a parameter from a smart value or literal text value, to return the row data

And please note: you appear to be keying your table on postal codes.  The lookup table can only contain 200 rows and so that is unlikely to work for something like postal code, which usually has thousands of rows.

When using the "Additional fields" area to edit an issue, JSON is used, as described here: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/

You may not need to use JSON for your rule, assuming your custom fields are listed in the drop-down list for the issue edit.

For example you can:

• type/copy-and-paste this value in your field
• the smart value will appear below the field as you enter it
• select the value below the field to use it

Putting these together, let's assume you have a lookup table, named tblAddressInfo, containing your Region, Province, and City as slash-delimited values.  An example usage would be:

{{tblAddressInfo.get(issue."Postal Code").split("/").get(0)}}