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; } } }

Specifying a field value to be retuned for a Smart Value lookup

Keith Vedol_139vux

Hi,

I am working on a release notification email that includes items that are separated by categories. Is there a way to return only the value specified for the smart value provided? For example, if the category values include:

Bug
Improvement
Feature

Would there be a way to specify which one to return? Currently it returns all with the following:

{{#lookupIssues}}{{customfield_10530}}

..and it would be nice to have it get the specified value instead of the entire list to separate the categories based on the email template being used which has separated scetions based on the issue category.

I have tried many functions listed in some of the documentation though none have worked thus far.

Any advice would be appreciated. Thanks.

Accepted answers

All comments

Bill Sheboy

Hi @Keith Vedol

When you have known criteria for your groups, such as Issue Type, there are at least two ways to do this:

Use smart value, list filtering to get the detailed issues meeting your criteria, while only calling Lookup Issues once. Please look here for more information: https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588
When you need both the issue details and summation for the selected issues, try calling Lookup Issues with different JQL for each group, and store the results you need in a Created Variable for use later in the rule, such as in your notification email.

Kind regards,
Bill

Keith Vedol_139vux

Hi @Bill Sheboy

I tried one of the examples in the documentation you linked me to with changes to look for the custom field value and no results are returned:

{{#issue.customfield_10530}}
{{ #if(customfield_10530, "New Feature")}}{{key}}{{ / }}

and another (exists and non-exists):

{{#issue.customfield_10530}}
{{#if(not(exists(name.match("(/New Feature/g)"))))}}{{key}},{{/}}{{/}}

{{#issue.customfield_10530}}
{{#if(exists(value.match("(/New Feature/g)")))}}{{key}},{{/}}{{/}}

I have replaced 'name' with 'value,' and 'defaultValue' to no avail.

I would just like the issues that contain this value in the custom field returned as a list and it is proving to be quite the task to do so.

The documentation only discusses how to return a comment body, but doesn't go into detail of how to return different values such as key, summary, description, etc.

Is there something I am missing here? Also I think the documentation could be updated to provide better examples for those who are newer to using smart values. Thanks.

Also, for point 2, do you mean having 3 {{#lookupIssue}} actions in one rule with one being for each category such as: (ex. fixVersion = '{{version.name}}' AND "Category[Dropdown]" = "New Feature" ORDER BY cf[10530] ASC, key ASC) and so on?

And if so, after each Lookup component I would need to add a Create Variable component?

Regards,

Keith

Bill Sheboy

First thing, it is helpful to use this how-to article to confirm you have the correct smart values for your fields: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Next, please try using the filtering on the lookup issues results, not on the individual issue. Something like this for some HTML in an email with keys and summary as URLs:

Here is the list:
<ul>
{{#lookupIssues}}
{{#if(equals(customfield_10530.name,"New Feature"))}}<li><a href="{{url}}">{{key}} - {{summary}}</a></li>{{/}}
{{/}}
</ul>

And...you should be able to reference any of the fields this way.

For option #2, yes...You would call lookup issues with different JQL, storing the results in a created variable as HTML, and then just include those in the email.

Keith Vedol_139vux

Hi @Bill Sheboy

The first option worked as I am now able to separate them accordingly (Thanks!). Is there a way to return a string if no issues were found for that value as opposed to being blank (ex. "No items matching that value were found.")

John Funk

Hey @Keith Vedol - did you get this solved?

Welcome!

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

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

cloud

jira-software

jira-software-cloud

smart-value