nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Karen West_p0b3ij

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:

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.

Accepted answers

Rustem Shiriiazdanov _Actonic_

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

All comments

Rustem Shiriiazdanov _Actonic_

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

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

Regards,

Rustem

Karen West_p0b3ij

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_

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.

Karen West_p0b3ij

Thank you so much for your help @Rustem Shiriiazdanov _Actonic_ . I had a play around with your suggestion and adapted it as follows to suit my needs:

project = DIG AND statusCategory = Done AND fixVersion WAS IN ("2025.02.16") and fixVersion not in ("2025.02.16")

Rustem Shiriiazdanov _Actonic_

Hi @Karen West ,

You are always welcome!

I would also suggest you to explore what marketplace apps like "Script Runner" offer for advanced JQL features to implement more complex querying. I like Script runner especially because with that app you can configure any crazy query, save it as a filter, and use in Jira directly, without necessity to open their app.

Regards,

Rustem

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

automation