How to set fixVersions to an unreleased product version with a releaseDate > now?

[Marcia Booth]

I currently have an automation to set fixVersions for issues whose fixVersions is empty and are transitioning from In Review to Testing. The fixVersions of those issues are set to "Next unreleased version by release date" which would normally be fine.

However, while we have issues still pending to be tested (issues for that version still in Testing status), we do not release the version in Jira. Its releaseDate remains the date the version was released, though. 

Since work continues to be done, we create a new product version and assign a target release date to it. Any new issue that gets transitioned from In Review to Testing should now use this new version. 

Unfortunately, the way the automation is set up, the version that has been released already but is still not marked as released in Jira continues to be set to new issues that have fixVersions empty.

How can I modify that automation to instead of using "Next unreleased version by release date" use the new unreleased version? Can I add a condition to filter versions with a releaseDate > today and get the earliest date?

[Bill Sheboy]

Hi @Marcia Booth 

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

• 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

Until we see those...

The short answer is your rule cannot find the next version by the next, greater date value of the version with the built-in rule actions.

A workaround could use the REST API endpoints to find the correct one.  I have not tried this for your exact scenario, so please experiment to learn if it will help.

• call the endpoint to get the project's versions using the Send Web Request action, filtered by unreleased, and ordered by releaseDate in ascending order
• when you only expect one "next, next" version, use list functions to get the correct one
• when you instead expect an arbitrary number of them, you may need to use more dynamic list searching methods to find the correct one by the date value

Kind regards,
Bill

[Marcia Booth]

Thanks for your reply. This is the current automation - when transitioning from In Review to Testing and the fixVersions is empty, edit the issue to add "Next unreleased version by release date", then add a comment

[Marcia Booth]

@Bill Sheboy I created a new automation to use Send Web Request with "Delay execution..." checked that looks like this

When I run it, version id returns blan but I do have a version for the project that is in a future date...

[Bill Sheboy]

Hi @Marcia Booth 

There is no filter() function for lists or JSON expressions in automation rules...

This is why I asked if you expect one-and-only-one result or multiple versions from the endpoint call: 

For only one, there should only be one record to use from the web response.

For multiple, dynamic searching methods are required, as I describe in this article: https://community.atlassian.com/forums/Automation-articles/Automation-concepts-Dynamic-searches-within-a-list/ba-p/2834235

FYI -- Without knowing how your team performs application releases, I wonder: if you use some form of automated release pipeline for applications, could that be used to also "release" the Jira version which is causing the challenge?  Once that happens, there would be no need for the workarounds as the next version assigned would be correct.

[Marcia Booth]

Thank you, @Bill Sheboy 

At the moment, there is only one entry that should be returned (unreleased version whose releaseDate is not null and > now) but there could be multiple in the future as the project progresses.

I will review your article to see if I can apply to this automation. Thanks.