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
4,300,109
Community Members
 
Community Events
165
Community Groups

Automation - when version released post release notes to slack

Spending some time setting up JIRA Automation which will save many man hours! Very exciting new feature.

 

Aiming to create a rule which 'When: Version released' it posts a message to our #releases slack channel.

 

Is it possible to retrieve the release notes in text format within the 'Send Slack message' actions Message box?

 

 

2 answers

1 accepted

3 votes
Answer accepted

Hi @Nick Phillips 

Yes, you can do that.

Trigger on the version release and then use JQL to get the associated issues, if you want to include those.  To see what is available for the version smart value, please see:

https://support.atlassian.com/jira-software-cloud/docs/smart-values-general/

If you cannot see what you want, consider using the REST API to grab an example version and see if other attributes are available:

https://support.atlassian.com/jira-software-cloud/docs/find-the-smart-value-for-a-field/

 

Best regards,

Bill

@William Sheboy  

For the JQL for the associated issues, what function can I use to query for only the version which was released, or does the trigger sort that out for me?

Hi @Alex Romano 

The trigger provides the version that you use in the query.  Here is what worked for me in a test...

  • Trigger: version released
  • Action: lookup issues, using the query below.  Note the quotes around the version in order to handle any version names which have embedded spacing.
project = myProject AND fixVersion = '{{version.name}}'
  • Action: add however you want to send the notification to provide the list.  I tried an email including the following to build an HTML list of the looked up issues.
Release {{version.name}} included these items:

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

 

Best regards,

Bill

Like # people like this

worked like a charm.  Thanks @Bill Sheboy 

Like Bill Sheboy likes this

Hi @Joey Klein  -- Welcome to the Atlassian Community!

I am glad that worked for you.

__Bill

On release, I am trying to post a comment to the JIRA released but on saving the below it throws an error. Any clues?

Capture.JPG

Hi @Avril Pinto -- Welcome to the Atlassian Community!

What is the error message that shows next to that trigger?

Best regards,
Bill

I'm trying that same content in an email content section.

 

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

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

 

I get the first line "Release..." but not the list.  Any ideas?

Hi @Joe Miller 

Please post an image of your complete rule and the audit log showing the details where the rule did not work as expected.  That will provide context for the community to comment.

Without that information, I can hypothesize, either:

  1. You are using Lookup Issues but did not first call the Lookup Issues action with JQL to gather the issues...or...
  2. You are using Jira Server/Data Center and those do not support the Lookup Issues action.  In that case, try using the Bulk Handling features of scheduled triggers and branches, and use the {{issues}} smart value rather than {{lookupIssues}}

Kind regards,
Bill

Worked.  It was the lookup.  How would I make this a global automation if I'm referencing project?

Joe, I am glad to learn that helped.

Global/multi-project rules may be created by a site admin, and they can reference all or specific projects.  Some things to note if you use such rules:

  • There are limits on the number of rule executions per month for global/multi-project rules.  (Executions are essentially unlimited for project-scope rules.)  Please discuss this with your site admin to learn your limits so you do not run out.
  • You noted releases (versions) in your first post, and those are defined at a project level.  Please ensure your rule can run in different projects, and does not assume something about releases which is only valid for one project, such as the naming convention.
  • Finally, are you using company-managed, team-managed, or a mix of projects?  The differences in the project types can impact rules, such as for status information.  Please check for those things and modify your rule accordingly.

Thanks,
Bill

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

63 views 1 3
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