How to add Release Notes via Smart Values to an automated email send upon version release?

[Desislava Dimitrova]

Hello,

I have an active automation rule, which sends an email every time a new Version is marked as Released.

Is there a way to add the release notes directly into the automated email using automation/smart values? 

Looking forward to your replies! Thanks!

[Bill Sheboy · Accepted solution]

Hi @Desislava Dimitrova  -- Welcome to the Atlassian Community!

I know of two ways to do what you ask, depending upon whether or not you need the issue information in the email and your recipients have Jira access:

1. If your recipients have Jira access, you could just send them a link to the specific release page, substituting in your information for company, project, and version: myCompany/browse/myProject/fixforversion/{{version.id}}
2. Use a Lookup Issues action to gather the issues and then iterate over them to send the details.  To do this please try:

Release Report rule:

• Trigger: when version released
• Action: lookup issues on JQL with fixVersion = '{{version.name}}'
• Action: send email with some markup for the list, substituting in your company URL and project name.

Release {{version.name}} included these items:

<ul>
{{#lookupIssues}}
<li><a href="{{url}}">{{key}}</a>: {{summary}}; {{assignee.displayName}}</li>{{/}}
</ul>

Link to the version is:
myCompany/browse/myProject/fixforversion/{{version.id}}

Please see the Lookup Issues documentation to learn the fields available for you to include.

Best regards,

Bill

[Desislava Dimitrova]

@Bill Sheboy Point 2 was the most applicable in my case, and I succeeded! Thank you for the helpful information!

[Bill Sheboy]

Awesome!  I am glad to learn that helped you.

[aagrawal]

Hi,

This is very useful.

A question though :

In the mark up how can I put two different lists based on issue type.

Example :

I would like to have two sections :

1) New Features

2) Bug fixed.

[Bill Sheboy]

Hi @aagrawal -- Welcome to the Atlassian Community!

In the future, I recommend adding a new question and adding a link to this related post.  That will get the most people looking at it to offer help.  Thanks!

Are you using Jira Cloud or the Server/Data Center version?

Only Jira Cloud supports Lookup Issues, and you may only use one lookup at a time.  So two possible work-arounds I can think of for the sections are:

1. Include all the issues you want in the lookup, and then use conditional logic in the email body to selectively list what you want: https://support.atlassian.com/jira-software-cloud/docs/smart-values-conditional-logic/
2. Include the New Features in your lookup JQL, format and save the results in a created variable, and repeat for other sections.  Then include those created variables as the sections in the email body.

Kind regards,
Bill

[aagrawal]

I tried with first option , it worked as expected. Thanks.

for everyone benefit , here is the code :

<ul>
{{#lookupIssues}}
{{#if(equals(issuetype.name,"Story"))}}
<li><a href="{{url}}">{{key}}</a>: {{summary}}:{{issuetype.name}}</li>{{/}}
{{/}}
</ul>

[Sohail Alam]

Hi @Desislava Dimitrova  & @Bill Sheboy . I put this automation rule but it did not work. Could you please help me?

[Trudy Claspill]

@Sohail Alam 's question is being addressed in this post:

https://community.atlassian.com/t5/Jira-questions/Can-we-create-automation-rule-for-Release-notes-after-the-Sprint/qaq-p/2481856