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

Comparing a branch issue field value with a list of trigger issue values.

Vitor Prado_vvjzs9

Hi! I'm using Automation and Smart Value in Jira Data center. I'm running an automation in a branch for a related issue of the trigger issue, and I want to go through all the related issues of the trigger issue and comparing a specific field value to a value of another field of the branch issue. So far I'm able to go through to list of the trigger issue related issues, but I can only compare it with a given string, and I don't know if its possible to refer to the branch issue field.

This is what I got working:

{{#triggerIssue.issuelinks.outwardIssue}}
{{equals(customfield_10600, "0010")}}
{{/}}

Instead of using the given string "0010", I wanted to use a value from a field of the branch issue, I know I can refer to it using "issue.customfield_10601", but I can't use it inside the trigger issue list since it would be out of context. Is there any syntax that would work for this case?

Thanks!

Accepted answers

All comments

Mark Segall

Hi @Vitor Prado - Are you only looking to take action on linked issues where customfield_10600 = 0010? If so, you could do something like this:

BRANCH (Related Issues)
CONDITION: JQL
- Your Custom Field = 0010
ACTION: Whatever you're trying to do

If I'm off base, please share a screenshot of your rule so I can better understand what you're trying to accomplish.

Vitor Prado_vvjzs9

Hi @Mark Segall, thanks for the reply and sorry for taking long to get back.

No, customfield_10600 could have different values. What I'm trying to accomplish is, between all the related issues to the trigger issue, I want to compare customfield_10600 and customfield_10601, if they match values, I want to link those issues. I'm doing this so I can set dependencies for further date automation. Since there are over 30 issues on my "template", I thought I could use a custom field to id the issue (say issue "0010") and another custom field to inform which issue it depends on.

What I have so far, is branching each related issue from an automation on the trigger issue (for example, JQL = issue in childIssuesOf("{{triggerIssue.key}}") AND cf[10600] ~ "0020"), and editing it with Smart Values to set the link, as the following example:

{{#triggerIssue.issuelinks.outwardIssue}}
{{#if(equals(customfield_10600, "0010"))}}
{"update": {
"issuelinks": [
{
"add": {
"type": {
"name": "Blocks"
},
"inwardIssue": {
"key": "{{key}}" 
}
}
}
]
},
"fields": {
"customfield_10209": "{{customfield_10210}}"
}
}
{{/}}

But I don't want to specify the id (customfield_10601) of the dependent issue on the code, I wanted to call the value from customfield_10601 of the branched issue, with the advantage of changing the custom field value when needed, rather than the smart value code.

Mark Segall

Sorry I'm still not quite following what you're trying to do. Is there anyway you can share a screenshot of the rule so I can see this all in context? It would really help me wrap my brain around it.

Also, you said you're on Jira DC. Am I correct that there is still no option for Lookup Issues as an Automation component?

Vitor Prado_vvjzs9

Unfortunately Lookup Issues haven't been implemented on Jira DC yet.

I'll try to be clear and upload some screenshots.

From the very beginning, I'm trying to create an issue template with automation, where there'll be a hierarchy with a main parent issue and several child issues (I'm linking them to the parent both using the native parent-link field and relating them so I can go through them with smart values). So the firs part of the automation, which is ok, is having the trigger upon the creation of the parente issue, then creating each of the child issues (they'll have different summaries and other information on specific fields), here is an example:

jira 4.png

The custom field "ID" (customfield_10600) is where I'll set a specific id for the issue, and the custom field "Dependências" (customfield_10601) is where I'll tell which issue ID the issue should be linked to. I chose to refer to the child issues with an ID, since issue keys wouldn't work for this case, and summary is more susceptible to changes.

After creating all the child issues, I need to set the links between specific child issues, that will work kind like dependencies, so I can later set and change dates automatically based on theses links. One option would be filtering each child issue in different branches, and instead of referring to the custom field "DEPENDÊNCIAS", I would just compare the ID of all issues related to the trigger to a given ID, and get that issue's ID to create the link, like this (the additional fields has the same script structure I sent earlier) :

jira 5.png

That's what I have so far, and it works, but I need to repeat it as a branch for each child issue. Rather than doing this, I thought it would be possible to create a single branch for all the related issues (child issues), and then again, with the smart values/json script, going through all the related issues to check the custom field "ID" and see if it matches the custom field "DEPENDÊNCIAS" of the branch issue.

Please, let me know if it's a bit clear now, and thanks for the attention!

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server

automation

smart-value