Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

When Jira issues are updated after the FixVersion has a status of released

Karen West
Contributor
November 28, 2025

Hi,

I'm new to automation and am trying to resolve a problem where Jira issues are added to or removed from a release after it has been released, which results in the release notes that I create using my Rovo agent to be out of date. 

I tried to create an automation rule with Rovo to alert me via email daily when Jira issues with a fixversion that has been released is updated. The JQL that Rovo generated failed, as you can see below:

automation-error.png

I have updated it as follows:

project = "DIG" AND updated >= -1d AND fixVersion IS NOT EMPTY AND text ~ "Digital Banking"

But I only want to know about updated issues where the fixversion is a released version. How can I do that, assuming it's possible?

NOTE: I cannot use a JQL Work Issues macro for the release notes pages in Confluence, which automatically update when issues are updated, as they are customer-facing and our customers do not have Jira access.

2 answers

0 votes
Karen West
Contributor
November 28, 2025

Thanks for your response @Rustem Shiriiazdanov _Actonic_ that should help with part of the problem, where issues are removed from releases. I shall try your suggestion.

Rustem Shiriiazdanov _Actonic_
Atlassian Partner
November 29, 2025

You are always welcome @Karen West! Let us know if it works, that's very valuable case you have here, and the resolution could help many people in the community.

0 votes
Rustem Shiriiazdanov _Actonic_
Atlassian Partner
November 28, 2025

Hi @Karen West

 

If your Team is consisted in preserving issues Statuses, but inconsistent in keeping issues tied to fIxVersion, you may try this:

project = PRJ AND statusCategory = Done AND fixVersion WAS IN releasedVersions() AND fixVersion IS EMPTY

 

That should issues which are marked as done (statusCategory considers all Done/Complete statuses if they are defined correctly in the worklogs regardless of their names), and the fixVersion was in some released versions, but now is empty. I just tested it with my project - it works ok. But I would suggest avoiding using it with multiple projects. 

 

If your teams tends to change fixVersion "ABC" to fixVersion "XYZ" the situation could require more complex logic, I am afraid. 

 

Regards,

Rustem

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events