Automation Rule is not working for Lookup Table

[Vikrant Yadav]

Hi Expert,

I am trying to create a score based on Severity and Dev field. 

For Dev if Value is Done then Score would be 50

For Dev if Value is Closed then Score would be 100

I have created a lookup table for this. 

I am trying to get the value from the lookup table but in logs it's showing nothing while in logs it's showing the selected value. 

Kindly suggest how can get the value from the lookup table based on the value selected in dropdown field. 

[Bill Sheboy · Accepted solution]

Hi @Vikrant Yadav 

Without seeing your rule's audit log...

• What is the type of the custom field: select option, an asset value, something else?
• Have you confirmed the lookup table Key values have no trailing spaces?
• Same thing for the custom field value?
• Have you confirmed the lookup table Key values exactly match the case of the field?
• Have you checked if the rule is "glitched", which can sometimes happen in the rule editor?  (The check for this is to disable the rule and re-create it from scratch before testing.)

Kind regards,
Bill

[Vikrant Yadav]

Hi @Bill Sheboy  
Field is a single select list field

Yes, I have double checked no space in key and value

Custom field value also don't have space

"customfield_10058": [
      {
        "self": "https://powerusers.atlassian.net/rest/api/3/customFieldOption/10808",
        "value": "Closed",
        "id": "10808"
      }

Option name is exactly same in lookup table. 

Lookup Table data in log : 

LookupTable{objectMap={Done=50, Closed=100}, size=2, entries=[LookupTableEntry{key=Done, value=50}, LookupTableEntry{key=Closed, value=100}]}

[Bill Sheboy]

Thanks for checking those things, @Vikrant Yadav   I just ran my ginormous test rule to exercise lookup table features and saw no change in behaviors.

Have you tried disabling this one and re-creating it to test for a rule "glitch"?

And, you do not show your entire rule.  What is trigger?  Perhaps there is some weird timing problem.  That could be diagnosed with:

• Save the field value to a variable and then use the variable in the get() function
• When the trigger is for work item create, linking, or the rule has "allow rule trigger" enabled, add a Re-fetch Work Item Data action after the trigger.

[Vikrant Yadav]

@Bill Sheboy  Trigger is manual trigger as for now. It will change to "Field Value Change"

[Vikrant Yadav]

Thanks @Bill Sheboy  I have tried to create another rule with a different field which is single select list field. 

Creating another rule from scratch fix my issue. 

[Bill Sheboy]

Awesome; I am glad to learn that solved it!

If you are interested and still have the old rule, you may be able to identify the cause by exporting it to JSON and reviewing it.  My hypothesis is it's one of these:

• the lookup table's stored ID value is corrupted and does not match between the two actions: the create and the get() usage, or
• the custom field ID in the get() was not stored / resolved correctly