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

Smart Values- #lookupIssues does not work with for pull request information

Chris Drylie_slfwpj

Hi all,

So basically we have automation setup that will send an email on a schedule each week, this is working fine a part from we want to include some information about pull requests, titles, url etc.

So in the send email body we have the following:

{{#lookupIssues}}
* {{key}} | {{summary}} | {{pullrequest.url}}
{{/}}

Key and summary display fine, but pull request URL does not display at all, is this not supported or is there a better way to do it?

Also bonus questions does anyone know how to get pull request ID?

Accepted answers

All comments

Bill Sheboy

Hi @Chris Drylie -- Welcome to the Atlassian Community!

Smart values are usually case-sensitive, so please try: {{pullRequest.url}}

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/#pullRequest.url

Kind regards,
Bill

Chris Drylie_slfwpj

Hi Bill

Thanks for replying and the welcome .

Gave it a try and the same result, everything else displays, juts not the Pull Request URL.

Bill Sheboy

Interesting... After the Lookup Issues action, please try writing this to the audit log and see what happens:

{{lookupIssues.first.key}} : {{lookupIssues.first.pullRequest.title}} -- {{lookupIssues.first.pullRequest.url}}

That will confirm if the development fields work for a Lookup Issues action, and give you a key to go confirm manually if the issue view does show the PR information.

Chris Drylie_slfwpj

Shows the Key but nothing for pull request info. I wonder if it is because Pull Request is in the development section in Jira.

Charlie Gavey_7xt8u8

Hi @Chris Drylie

Which trigger are you using for this rule? It's worth noting that the pull request smart values are only supported when using the Pull request created, Pull request declined and Pull request merged triggers.

You can read more about this here:
https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/

Cheers,

Charlie

Chris Drylie_slfwpj

Hi Charlie,

That's disappointing,

We are triggering on a schedule that runs a JQL to pull all jobs for the week that has been merged.

We then wanted to show Job number, description, Pull request url to help smooth out our release note process.

Nick Caplan_8dfp6z

Reposted as comment

Nick Caplan_8dfp6z

We have a very similar requirement...

We want to send a notification (email / Slack) when a fix version gets released, including:

Version name
Issues within version
Pull requests for each of those issues

The first two seem to be doable but I can't seem to find a way to do the third when the trigger is Version Released.

Welcome!

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

Quick Links

Find more posts tagged with

automation

smart-value