Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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!

1 answer

1 accepted

1 vote
Answer accepted

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

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

Like Bill Sheboy likes this

Awesome!  I am glad to learn that helped you.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

102 views 0 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you