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

Using triggerIssue.url in smart value list

Mikko

Hello

I'm struggling with smart-value lists when using non list type fields in it.

Automation I'm working with is triggered when value changes for fixVersion

I gather a bunch of issues using branching with jql - this works ok.

My goal is to edit each found issue and add a (smart-)link to the trigger issue in the description.

However the links are emtpy and render as [|]

I've been trying to edit the description like this:

{{issue.description}}
New {{#triggerIssue.Impacts}}{{.}}
[{{triggerIssue.summary}}|{{triggerIssue.url}}]{{/}}

triggerIssue.url and summary work if I log them by themselves in the branch

(additionally if I add the "|smart-link" it says Unsupported content ?, because of the missing link I suppose)

Is there perhaps an alternative to adding the trigger issue as a smart link in the description? For lookup issues it works just using {{lookupIssues}} and it links them all as smart links.

Thanks in advance!
/Mikko

Accepted answers

All comments

Sergei Troshin_usua2u

Hi @Mikko and Welcome to Atlassian Community!

There is no need to use text formatting. I succeed with simple template:

{{issue.description}}
New {{triggerIssue.key}}

Btw, this template works as well:

{{issue.description}} 
New: [{{triggerIssue.key}}|{{triggerIssue.url}}]

Try out my simple template and if you encounter any difficulties, feel free to ask me, and I'll do my best to help.

Mikko

Doesn't work when it is part of a list. The impacts field is a multiselect checkbox so there can be multiple values added at once.

Case here is that I want it to add a phrase

New <impact_value>
<link_to trigger_issue>

for each impact that was added.

So if there are multiple impacts added it would add them in one go and show as

New impact1
<link_to trigger_issue>

New impact2
<link_to trigger_issue>

But maybe I'll just change the way it's shown and list all impacts with just one link to the issue.

New impact1, impact2 ... 
<link_to trigger_issue>

Thanks anyway!

/Mikko

Bill Sheboy

Hi @Mikko

What is the type of your Impacts field?

What are the contents of your Impacts field? In your expression, it seems you are treating the field as if it is a list of issues, which I do not believe is a field type.

Kind regards,
Bill

Mikko

The impacts field is a multiselect checkbox.

The impacts field is not the culprit. It was showing the link to the trigger issue which is not appearing.

But I resolved it by first listing all impacts and then showing the link, outside of the impacts list.

/Mikko

Sergei Troshin_usua2u

Hi @Mikko again

Hope you're doing well!

I didn’t consider your Impact field at first because you initially described the issue as a problem with rendering the smart link for triggerIssue in the description. I provided solution templates based on that. But now you’re talking about rendering the Impacts field, so I’m not really sure what the actual problem is. 😕

By the way, if you need to include the Impact custom field value from triggerIssue in the description, it can only be done using comma separation. Use this template:

{{triggerIssue.customfield_10055}}
New: [{{triggerIssue.key}}|{{triggerIssue.url}}]

Replace 10055 with the correct custom field ID for your Impact field.

Mikko

The actual problem was:

Issue A is updated

I need to update Issue B with the textual representation of the Impact values in Issue A in the description field.

For that I tried looping the impacts as you would with any list type value using

{{#triggerIssue.Impacts}}{{.}}{{/}}

which is working ok. That prints all the impacts selected on Issue A onto issue B description field.

However I wanted to have the link to Issue A after each new impact, to do I tried adding the link after the {{.}} part, but didn't succeed.

But as said, I went around the problem by printing all impacts first and the link after them only once.

Bill Sheboy

The root cause of the original symptom you note is:

Once inside of an iterator, only data from that scope and lower is visible; this is a known, long-standing limitation of rule iterators
And so the trigger issue's summary and URL are not visible

Providing the repeated information one time is a better solution for your scenario; well done!

When there is variable information instead, the solutions [when possible] are more complicated, often require "flattening" the list into a variable, and using a text functions and regular expressions.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud