Is there a way to automate release notes for approved JIRA issues into a confluence space

[Zara Imam]

My team has a JIRA board where we approve all upcoming product releases. How can I make it so that each week, a summary list of all issues in "Approved" status on the board are published to a new Confluence page within a linked Confluence space? Is there an automation feature that can do this?

I am essentially looking to create an archive of weekly approved releases, and eventually create a repository of all the release notes and any related documentation (like a user guide for a specific release that I can then add to a page). 

Going further - is there a way to also automatically send the weekly list of Approved issues and their summaries out to an email list or distribution group?

[Jens Schumacher - Released_so]

Another option you can look at is Released. Instead of just publishing the content of the Jira tickets, Released actually writes release notes with AI for you.

Although there is still a manual step involved (right now), it only takes a couple of minutes to publish the updates and the post can also be sent out via email. 

You can publish to Confluence, or a private/public portal like this: https://released.releasedhub.com/released/changelog


Disclaimer: I'm one of the founders. 

[Sascha Reuter]

Released is pretty much the de facto standard for doing this in a simple yet elegant way, see their example. Kudos to you @Jens Schumacher - Released_so and the whole team!

[David Nickell]

Hello. Yes :-)    

You can use a filter subscription to get a list of issues on a schedule.

In so far as saving in confluence ... 

• I know you can display filter results as a widget on a confluence page
• I assume you can use Confluence Automation to create a copy of that page as a weekly archive though I have not done it myself.  
• I have used jira automation to create a confluence page using a set of rules / triggers.  So I assume my comment above re: confluence automation is certainly worth looking ar as a starting point.

If all else fails, I like Power BI pulling data through the REST API on a schedule (like 4x a day).  But that is probably over architecting the solution and I suspect your needs can be addressed with Jira and confluence directly.

[Zara Imam]

Hi! Thank you so much :) this is exactly what I was looking for!

[Armin Meyer _Seibert - Coderay_]

I just add some details to Davids excellent points.

You asked for "Release Notes" and therefore I want to recommend to use the concept of Release in Jira if applicable to you. This is the built in entity to mark issues for a specific release and the entity can be used as an trigger for automations. Beside of the structured release information for individual designed post processing the creation of "Release Notes" for Confluence is integrated in the process of finishing a release. Once you finish a release you can freely choose under which parent page in confluence the release notes should be created.

Your stakeholders you want to inform can be added as watchers for the relevant section in confluence and will be notified when a new release note is published.

For more individual handling I also recommend confluence automation and jira automation that are built in.

As a product developer I want to add that our solution Autopage can add some spice in such use cases and is fully integrated with Jira Automation and builds a bridge between Jira and Confluence.

[David Nickell]

one possible issue came to mind after my answer -- if you clone the Confluence Page and it still has the Filter Results widget, it will continue to display the current results no matter when the page was generated.  I think the way to resolve this is look to automation for the creation of a PDF from your confluence status.  And if you think about it, you wouldn't want anything to change on your weekly report.  So --look at automation for creation of a PDF (as opposed to re-cloning the Confluence Page)