Feasibility of Automating Release Notes with Jira Automation and Rovo

[Fabricio Riveros]

Hello team, good morning. I hope you’re all doing well.

I’m reaching out to ask about the technical feasibility of a client request related to Atlassian Rovo.

The requirement is to automate the generation of Release Notes. Specifically, the client is looking to use Jira Automation together with a Rovo Agent to analyze the issues associated with a deployment in order to:

Automatically generate a release notes document, or

Add a dynamic comment that can be updated/edited as new tickets are added to the deployment.

Could you please confirm whether you have already worked with the “Run Rovo Agent” action for use cases like this, particularly for automated content generation?

Thank you in advance for your guidance.

[Marc -Devoteam-]

HI @Fabricio Riveros 

Welcome to the community.

This is an ootb function when you have Confluence and Jira.

When releasing a version in Jira your are asked if release notes need to be created.

Also see https://support.atlassian.com/jira-cloud-administration/docs/create-release-notes/ 

[Sujeet Pathak]

Hi @Fabricio Riveros 

If you are open for marketplace apps you may try our app - Free:(AI powered) Automated Release Notes & Reports for Jira

It provides you an end-to-end solution to publish release notes and reports to confluence from Jira. You can automate this entire activity through in-built automation rules in this app and it supports the confluence's new cloud editor giving you full flexibility on editing look and feel of your content. You can even append/prepend the content to existing pages and create new pages under specific parent page/folder.

P.S. I am part of the team that has build this app.

Best,
Sujeet

[Bill Sheboy]

Hi @Fabricio Riveros -- Welcome to the Atlassian Community!

Short answer: As there is no public REST API endpoint to create a release notes page in one step (e.g., as the Jira feature does with code), I recommend experimenting with Rovo to learn if it can create the page from a prompt...and with a second prompt, create an automation rule for the updates you describe for the comments.

With no public endpoint to create the release notes, pre-Rovo workarounds to automate creating the notes were:

• Use a marketplace app
• Create an automation rule which creates the Confluence page, perhaps using a template, and then update the page content for the specific instance data using endpoints and the Send Web Request action.  Please note, some features of versions / releases are not accessible to endpoints and thus could not be added to the release notes (e.g., related work information).

A more advanced workaround would be creating your own Forge app for an automation rule action to make the page and changes with the endpoints.  Then use the new action in a rule.

Kind regards,
Bill

[Fabricio Riveros]

Good morning,
I hope you are doing well.

I need some guidance with the following question:
Do you know how I can identify a field that appears in Releases in Jira?
This field is located just below the Release name.

The requirement is to be able to write a rich text message into that field from an automation rule.
I need to identify it either visually from Jira custom fields or through the API.

Specifically, I need to know its name or ID so that the automation can send the text returned by the Rovo agent.

As additional context, the idea is to use the Rovo Release Notes agent to generate a summary of the work items included in the Release, and then write that generated summary into this field, which currently appears to have no visible identification.

I am attaching a screenshot of the field.

Thank you.

[Fabricio Riveros]

[Marc -Devoteam-]

Hi @Fabricio Riveros 

This is not a field in Jira this is the description of the version.

So by using the get version API endpoint, you can get the information that is set in this option.

[Sujeet Pathak]

Hi @Marc -Devoteam-  AFAIK, this new rich text description field of version description is not yet supported in the get version API endpoint. This API currently only support the legacy plain text version description field.

[Bill Sheboy]

Hi @Fabricio Riveros 

That is the "section" information, and it is not available with the REST API.  Here is the suggestion to add that and the remainder of the new version data to the endpoints:

https://jira.atlassian.com/browse/JRACLOUD-87059