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

Trying to have issue key as link in subject line of email from automation.

Jason Chayer

When I create an issue, I am wanting to send out an email. With this, I want the issue key to be in the subject line, and I want that issue key to be a link to the specific issue in Jira.

I have tried ...

<a href="{{issue.url}}">{{issue.key}}</a>

But to no avail

Accepted answers

All comments

Laurie Sciutti

Hi @Jason Chayer ~ try this: {{createdIssue.url}}

Jason Chayer

@Laurie Sciutti - unfortunately this did not work. It actually is not even pulling the issue key any longer.

Bill Sheboy

Hi @Jason Chayer

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!

Kind regards,
Bill

Jason Chayer

@Bill Sheboy - I am not in front of my automation rule to get an image, but below is what the rule is.

When: Issue created

Then: Send email

To: email address

Subject: Critical issue created {{issue.key}}

Content: all the information I have in here pushes correctly to the email

That is it. It is a pretty straightforward automation.

Where I am having an issue is the Subject Line, specifically {{issue.key}}.

When I receive the email, the subject line contains the issue key; however, I need that to be a link where I can click.

Bill Sheboy

Depending upon your email tool's formatting, the URL or HTML version of it should work.

There is a known issue where the Issue Created trigger can fire so quickly that some issue data may not be available when the rule starts. This can lead to unexpected behavior (like empty fields) or rule errors.

The work-around for that is to add the Re-fetch Issue action immediately after the Issue Created trigger. This will slow the rule down a bit, reloading the issue data before proceeding to the next step. Please try adding that and re-test.

If that does not work, please try posting those image of your complete rule, the send email action, and of the audit log details showing the rule execution.

Ramiro Justet

Hi Jason,

try replacing {{issue.url}} with this expression:

https://tu-jira-instance.atlassian.net/browse/{{issue.key}}

setting the instance name to your particular instance.

Regards

Ramiro Justet

<a href=“https://tu-jira-instance.atlassian.net/browse/{{issue.key}}”>{{issue.key}}</a>

SilkeS

This topic is now closed as the discussion has become outdated. If you have more questions or want to continue the conversation, feel free to start a new topic. For more details on why we close older threads, check out our Rules of engagement - Atlassian Community .

Thank you for your understanding!

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-software-cloud

automation