You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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:
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:
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.
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?
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:
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:
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: