Automating Release Notes

[Jason Bush]

I want to create an automation that sends a slack message with release notes once a version is set to "released". I don't want to use confluence and would prefer the body of the message to list the associated work items (+ their type...bug...task..etc). 

I'm stuck on how to include all the associated work items within the message. 

Here's what I have so far via Rovo and Gemini chats, but none of their suggestions are working. Surely there's a way to do this? 

Body of automated message:

Resulting Slack Message: 

[Bill Sheboy · Accepted solution]

Hi @Jason Bush 

First thing: in general, I recommend not using bots / AI-tools to answer Jira automation questions.  Such tools do not have access to your specific site instance, and thus do not have context for your Jira version, configurations, spaces, etc.

To that point, for a question like this, context is important for the community to help.  Please post the following:

• what type of space / project is this: company-managed, team-managed, JPD, etc.
• an image of your complete automation rule in a single image for continuity
• images of any relevant actions / conditions / branches
• an image of the audit log details showing the rule execution
• explain what is not working as expected and why you believe that to be the case

Until we see those...

Your message seems to use the smart value {{lookupIssues}} so did you include a Lookup Work Items action before that in the rule?

Kind regards,
Bill

[Jason Bush]

Hi Bill, 

I will try to answer as best as I can. Here's the full image. To emphasize, I only need help with the smart values in the body of the message. It should include every work item associated with the release. Everything else (triggers, etc) are configured and working. 

• It is team managed 
• Included - though at this point I just need help with the slack message body.
• Audit logs - don't think this is needed? Again just need help with smart values

[Bill Sheboy]

Thanks for that information, @Jason Bush 

It shows the rule is missing the Lookup Work Items action.  Please change your rule to add that before the message is sent:

• action: version released
• action: lookup work items, with this JQL

fixVersion IN ( {{version.id}} )

• action: send Slack message

[Jason Bush]

Thank you Bill, you're a genius. That's exactly what it needed.

With a few more tweaks it looks great. Here are the final results:

Slack Message:

[Bill Sheboy]

Awesome; I am glad to learn that helped!

[Shawn Doyle - ReleaseTEAM]

Hi @Jason Bush 

There is a way, but don't call me Shirley,

Are you branching on lookupIssues? If not it may not be getting populated.  This thread can help with what pre-reqs you need to make it work.

https://community.atlassian.com/forums/Jira-questions/How-to-perform-action-on-lookup-issues-results-in-Jira/qaq-p/2661593

If that all checks out, then I'd simplify your code to see if you can just get it to iterate thru all the issues.

{{#lookupIssues}}
<a>{{key}}</a>
{{/}}

And if that starts to work. This thread may help with making the url links in the message.

https://community.atlassian.com/forums/Jira-questions/Sending-an-automation-email-with-issue-URL-link/qaq-p/2053314

[Jason Bush]

I don't quite follow these threads sorry (pretty new to this). I've tried copy/pasting the above and it just returns blank space in the message. 


More context might help:
We have work items (tasks, bugs, etc tied) to various epics within this space. The space has a release version which is tagged on each work item. So, the release will show each work item listed.

Devs then flip this to "released" once the sprint is over. After doing so, they send manual release notes over slack like this:

"Release Notes for version ____ is live

Here are the list of bugs and fixes:

• Net 2483 - Fix fee issue 
• Net 1459 - Added new field "fee item" to employee records"

^I want to imitate this format using the Jira automation + smart value to pull the relevant cards into the message body.  I was assuming Jira had a very simple way of doing this but maybe I'm biting off more than I can chew.