Not Having Success automating Release Notesa

[Steve Binney]

When I follow the example here

https://community.atlassian.com/learning/lesson/automate-release-notes-generation-with-rovo

When I run a release, I get this output on my page:

I can help you generate release notes, but I’ll need a bit more info to get started:

• I need to know which Jira project you’re referring to, or you can paste a link to the Jira search or board that contains the issues you want to include in the release notes.

• By default, I’ll look for all issues that have been moved to “Done” in the past two weeks, but you can specify a different time period or status if you’d like.

• I can analyze up to 20 issues at a time, so if your release includes more, please narrow down your search or let me know which ones to focus on.

Could you please provide the Jira project key, a link to the relevant Jira search, or clarify which issues you want to include? Once I have that, I’ll confirm the details with you before generating your release notes!

-----------

I then tried to add a condition to tell it the project and validation fails and the rule does not execute - I also tries to add JQL for the search and that fails.  Any ideas?

[Trudy Claspill · Accepted solution]

Hello @Steve Binney 

If the rule is scoped to a single Space, why do you need a condition for checking the Space? There is no reason to have the Condition within the Trigger; that is not specified as part of the example.

Where in the rule have you added the JQL? Can you show the details of the rule with that change made?

[Steve Binney]

I added that becasue the generated output asked for it

I can help you generate release notes, but I’ll need a bit more info to get started:

• I need to know which Jira project you’re referring to, or you can paste a link to the Jira search or board that contains the issues you want to include in the release notes.

• By default, I’ll look for all issues that have been moved to “Done” in the past two weeks, but you can specify a different time period or status if you’d like.

• I can analyze up to 20 issues at a time, so if your release includes more, please narrow down your search or let me know which ones to focus on.

Could you please provide the Jira project key, a link to the relevant Jira search, or clarify which issues you want to include? Once I have that, I’ll confirm the details with you before generating your release notes!

Here is the rule:

[Trudy Claspill]

I believe you need to update the prompt to the agent. Not add a condition to the rule.

I created the same rule as in the training with the same prompt and got the same content you specified in the Confluence page that was created.

I then changed the prompt in the User Rovo Agent action to:

Generate release notes for this released version {{version}}

{{version}} is the smart value within the rule that refers to the Version that triggered the rule.

The information in the content of the page changed, because the prompt gave the agent clarity on the version for which I wanted it to generate release notes.

So, to reiterate, you need to update the prompt in the Use Rovo Agent action to provide more specificity. You do not need to add conditions to the rule.

[Steve Binney]

It works!  Thank you.

[Trudy Claspill]

You're welcome.

If my responses helped you solve your challenge please consider clicking on the Accept Answer button directly above my first reply.

[Steve Binney · Accepted solution]

 REmoved

[Bill Sheboy]

Hi @Steve Binney 

What is the scope of your rule in the details at the top?

I hypothesize the rule is global (or multiple-space) scope, and as a result the action cannot uniquely identify the correct space for the version...even though it is specified in the trigger.  In that case, try changing the rule to a single-space scope and re-testing.

Kind regards,
Bill

[Steve Binney]

Rule is part of Sandbox Space so it is not global.  It seems that any condition that I add to the rule generates a warning and the rule does not execute.  I then tried to add this JQL rule

project = FOO AND statusCategory = Done AND resolved >= -2w ORDER BY resolved DESC

Same thing - Validate generates a component warning and the rule does not execute when I release a version

[Laim Leon]

It seems your automation needs a clear scope and trigger. Make sure the project, version, and JQL are correctly set, and the trigger (like “Version Released”) actually fires. Once Jira knows which issues to include, it can generate release notes automatically🤗.