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

How to iterate a list to find a matching item and its index with smartvalues

Adolfo Casari

Hi,

I have a variable {{X}} with a list of strings.

Given a smart value {{Y}} (string), I need to find whether there is a matching value in the list X AND its position.

I know how to iterate X and check if Y matches any element, but I don't know how to get the index with the match.

if there is a matching, the idea is then to do {{X.get(index+1)}} and to handle the case when index+1 is out of bound.

Thanks for your help!

NOTE: I am trying this:

Result: {{#NombresdeTareas}} {{#if(equals({{.}}, issue.summary))}} {{index}} {{/}} {{/}}

but fails with this error:

Could not extract smart value parameter: {{.: Result: {{#NombresdeTareas}} {{#if(equals({{.}}, issue.summary))}} {{index}} {{/}} {{/}}

Accepted answers

Bill Sheboy

Hi @Adolfo Casari

Just to confirm, is your {{X}} a created variable or an issue field? If it is a created variable, you would need to split it into a list before it can be iterated upon.

For the other part of your question, I am assuming you are using a created variable...

Created variables are text, and have no object type or attributes. And so when split a value is just the {{.}} as you have shown. However that cannot be referenced in the smart value functions. Instead many of the functions are implemented to handle that case without passing the value.

For example...

action: create variable
- name: varMyVariable
- value: red,green,blue,alpha
action: log a search for a value, "blue"
- {{#varMyVariable.split(",")}}{{#if(equals("blue"))}}found {{.}} at {{index}}{{/}}{{/}}

A complication in your scenario is that once inside of an iterator, only data at that scope and below is visible. That means that for your iteration on NombresdeTareas, the issue summary is not visible.

One work-around for that is to use the match() function with a regular expression on the variable instead of a conditional inside of the iterator:

If you do need the index value from the list, would need to store the index with the value, and include that in your match expression.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Adolfo Casari

Just to confirm, is your {{X}} a created variable or an issue field? If it is a created variable, you would need to split it into a list before it can be iterated upon.

For the other part of your question, I am assuming you are using a created variable...

For example...

action: create variable
- name: varMyVariable
- value: red,green,blue,alpha
action: log a search for a value, "blue"
- {{#varMyVariable.split(",")}}{{#if(equals("blue"))}}found {{.}} at {{index}}{{/}}{{/}}

One work-around for that is to use the match() function with a regular expression on the variable instead of a conditional inside of the iterator:

If you do need the index value from the list, would need to store the index with the value, and include that in your match expression.

Kind regards,
Bill

Adolfo Casari

Hi @Bill Sheboy

ust to confirm, is your {{X}} a created variable or an issue field? If it is a created variable, you would need to split it into a list before it can be iterated upon

It's a created variable.

A complication in your scenario is that once inside of an iterator, only data at that scope and below is visible. That means that for your iteration on NombresdeTareas, the issue summary is not visible.

Yes, I found out that. I got an exception error when using issue.summary in the iterator. Any hope for that limitation to get fixed in the future? It's a very bad thing not being able to use any issue fields inside an iterator.

If you do need the index value from the list, would need to store the index with the value, and include that in your match expression.

So your saying red-1,green-2,blue-3,alpha-4 right? Can use match with a list? I don't see that option here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-lists/

Thanks a lot for your help.

Adolfo Casari

I tried your suggestion but seems that I can't use issue.summary inside the match. The idea is to match the current issue summary againts a list of predefined issue summaries, so I can create the next issue in the list.

Bill Sheboy

I am just a Jira user, and so have no visibility to Atlassian changing the scoping behavior for iterators.

Regarding using the index values with the list, first you build the list with an iterator storing in a variable, as you showed for my example. Then match on the value, such as "(blue*)". And finally separate out the value with text functions to get your index.

On your next post about using a field like {{issue.summary}} in a match's regular expression, the trick is to first create a variable with the expression, and then use that in the match:

action: create variable
- name: varRegularExpression
- value: .*({{issue.summary}}).*
action: log on the match
- {{varMyVariable.split(",").match(varRegularExpression)}}

Please adjust the expression / grouping as needed for your scenario.

Welcome!

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

Quick Links

Find more posts tagged with

jira-cloud

automation