Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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

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:

* {{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?


3 answers

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:



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.

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.

Reposted as comment

0 votes

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

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

Kind regards,

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. 

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.

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

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Atlassian Automation

Jira Automation: Sum Up Story Points Roundup (Initiatives -> Epics -> Story/Tasks -> Subtasks)

Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...

3,100 views 10 9
Read article

Atlassian Community Events