Trouble with lookup tables

[Brian Gauthier]

I have created a lookup table called Sprints (see below), and when I try to refer to these sprints later through referencing the lookup table, I do not get a response.  

I'm passing it the value that's in customfield_10020.  Then I'm trying to test it with a log in later on.  The idea is to then pass that value into an API for an update into a different system.

Please help

[Bill Sheboy]

Hi @Brian Gauthier 

For a question like this, context is important for the community to help.  Please post the following:

• an image of your complete automation rule,
• images of any relevant actions / conditions / branches, and
• an image of the audit log details showing the rule execution.

Until we see those...

What is the field type for issue.customfield_10020: text, number, single-select option, etc.?

If it is single-select option, please try using the value attribute in the lookup, such as issue.customfield_10020.value

Also, I recommend always adding a prefix to variable and table names to avoid possible human (and rule) confusion / errors with similarly named smart values. 

For example, perhaps name that table varSprintIdToName.

Kind regards,
Bill

[Brian Gauthier]

@Bill Sheboy - I've added a few more images.   Sprint is a single select option and I've tried using issue.customfield_10020.value, but that still didn't work.  I'm guessing there is a small detail that I'm missing.

[Bill Sheboy]

Thanks for that information.  Please also post an image showing the audit log details for the rule execution as that will help compare the steps to what happened.

Have you confirmed the custom field id (or smart value) for your field?  You may use this how-to article to do that: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

I see your rule is triggered on a change to the built-in, Sprint field.  Then the rule uses your custom field to attempt the lookup table get().  You may want to add a condition and write to the audit log to confirm the custom field contains a value.

[Marc - Devoteam]

Hi @Brian Gauthier 

What do you want to do compare info.

The lookup table provides information you can to compare or set in a field.

The smart value {{Sprints.get}} aloows you to get information from the lookup table, not from a custom field.

[Brian Gauthier]

@Marc - Devoteam I'm trying to pass in the value from the custom field as a key (which is a sprint ID), and return the value (eg - S24.13 (10-09-2024))  so that I can throw that into an API. 

[Marc - Devoteam]

Hi @Brian Gauthier 

I still don't get you.

Is S24.13 (10-09-2024) a Sprint name? if so why use this for an API call, as this is not an option.

in the API you can only use sprint id.