Version auto release

[Emerson]

I already have an automation that creates a new version when the previous one is released. And I wanted to increase the automation to generate the release notes automatically. Also, I would like the version to be released automatically when all items within it are in "Released" status.

[Bill Sheboy · Accepted solution]

Hi @Emerson 

It seems you already have an automation rule.  For questions like this, please post images of your complete rule and the audit log details showing the rule execution.  Those will provide context for the community to offer suggestions.  Thanks!

What have you tried thus far to improve your rule to the new needs?  What is not working as you expect?

Kind regards,
Bill

[Emerson]

Hi @Bill Sheboy 

There's my rule. Works really good, but still need some manual actions.

[Bill Sheboy]

Thanks for that information. 

What do you mean by "manual actions"?

From what you have described, you will need at least two different rules:

1. Triggered on issue transition to Released, check if all other issues in the release are complete, and then release the version.
2. Triggered on version released, do what you are currently doing, and somehow create release notes.  You are unclear what that means.  Within a rule, you can use an email to do that, if you wish.

Please note: because the second rule can be triggered by the first one, you will need to enable the "Allow Rule Trigger" option in the details section of rule #2.

[Emerson]

Manual actions:
1- The creation of version notes within the version itself is done manually;
2- The release of the version is also done manually.

The image below is of the Release Notes screen within the version. I want it to be automatically created and populated with the issue fields I choose.

[Emerson]

Tried a basic automation and returned this:

[Bill Sheboy]

First thing, there is no built-in way to create release notes as you are doing.  I suggest investigating if there is a REST API call to do so from a rule.

Next for the error you show, your condition on Issues Fixed In Version only works for a version-related trigger.

Instead you would need to use a Related Issues condition, testing against the version which is in the trigger issue:

project = yourProjectName AND status != Released AND fixVersion = {{triggerIssue.fixVersion}}

Remember you are confirming all the issues in the release are done, and so your condition would be "None Match Specified JQL".

[Emerson]

I tried a bunch of stuff to see what happens, but none of the worked.

Your JQL returned the same error as my last print.

It's really weird that it's that complicated... it's just a status check and update.

[Bill Sheboy]

My mistake as the smart value name is plural.   Please try this, ensuring that you use your project name in the JQL:

project = yourProjectName AND status != Released AND fixVersion = {{triggerIssue.fixVersions}}

If that does not work, please post images of your current rule and the audit log showing the details of the rule run.

[Emerson]

Born and raised to bring joy and less manual work. Many many thanks!

[Aftab_Akhtar]

Hi @Emerson  would you be able to provide a screenshot of your rule to create a new version when the previous one is released please?