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

Is it possible to return {{deployment}} values with {{{#lookupIssues}}?

Ben Ikin

Hi,

We currently have 2 automation rules that are triggering

The first is using the integration with Gitlab to transition Jira issues from 1 status to another upon a successful deployment into the 'test' environment group. This takes place overnight around 01:00 AM and is triggering on a per-issue basis. (more on that later). Inside this automation, a comment (or multiple) is added to the Jira issue which returns the following:

Deployed to Environment: {{deployment.environment}}
Deployment Name: {{deployment.name}}
Deployment State: {{deployment.state}}

Inside each Jira issue there could be 1-3 different comments with deployments if it is a multi-component issue.

The second is then running at 03:00 AM and using a lookup to return all jira issues in that particular status which then sends a webhook to create a confluence page using {{#lookupIssues}}. Inside that webhook we send a request which returns the following in a table format:

{{issueType.name}}, {{key}}, {{summary}}

These are both working fine independently.

What I'd like to do is link the events so that the 2nd automation rule can return the deployment information. Specifically {{deployment.environment}} and {{deployment.name}} that matches the specific (unique) issue returned from the {{#lookupIssues}}{{key}} which would returning the multiple {{deployment}} values associated if there are multiple.

I'd plan to add these as extra columns after {{summary}}.

As a bonus, I'd love to combine this into 1 automation where the 2nd trigger event can be when the LAST issue from the 1st automation rule finishes.

Happy to share screenshots of setup if that's helpful, but fair warning that the body of the Custom data webhook is full of formatting so not very readable.

Thanks in advance!

Accepted answers

Bill Sheboy

Hi @Ben Ikin

First thing, I believe you will still need 2 rules. As you noted, those DevOps triggers for rules often fire for each issue and so the rules cannot be combined.

Next, your first rule has access to the {{deployment}} smart value but the second rule does not: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/#--deployment--

And so your comment could be the bridge...

In your second rule, you could add a smart value, list filtering on the comments to find text matching your deployment comment(s), extract that, and use it in the custom data. If you want to try that, here are some references:

An alternative is to create a custom field specifically to store data from the {{deployment}} smart values (i.e., from rule 1), concatenating values as the rule triggers when multiple deployments happen.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Ben Ikin

First thing, I believe you will still need 2 rules. As you noted, those DevOps triggers for rules often fire for each issue and so the rules cannot be combined.

Next, your first rule has access to the {{deployment}} smart value but the second rule does not: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/#--deployment--

And so your comment could be the bridge...

Kind regards,
Bill

Ben Ikin

Thanks for the reply @Bill Sheboy

I had considered the custom fields but wanted to avoid using that method if it could be avoided, so I'm intrigued by the list filtering.

We don't currently separate out internal and external comments so I'd be searching for a particular string. Reading the documentation that seems like it should be OK but I seem to be struggling, maybe I need to take a break and come back to it later.

As there's a limit of 3, I'm working on the assumption that I can limit the filtering at the last 3 messages. Example of the 3 possible variables in environments:

Environments: React / Java / Content (all followed by /test)
Name: Deployment ## (v#.#.##)

So I'd add 3 extra columns to the table (one for each environment)

In React I'd look to filter for the text "React" and return preferrably just the specific part of the message, but I could live with displaying the whole comment.

Bill Sheboy

Sounds good; if the variables are always updated for each environment you should always have the latest deployment.

With the match() function, rules use a regular expression. Then you could use text functions after that to extract the data you need.

I have never heard of a limit on the return count for a list filter with rules, although I hypothesize it is 100 items. To limit the actual results (e.g., to 3) the rule gets more complicated fast: there is an {{index}} for list items but I do not believe it cannot be queried directly. A created variable and some shenanigans are required.

Ben Ikin

Ah that's good to know that match will find the latest one. Removes the need for a limit of 3.

Could it be as simple as something along these lines?

{{#issue.comments}}
{{ if({{issue.comments.match("React")}}, body) }}
{{/}}

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation