Plugin that allows you to manage versions AND query for issues between versions??

[Alexandria _Lexi_ Codd]

ive been using the poduct since about 2018 and like many of us have always struggled with the unreliable jql for 'issue in version > X and < Y" to find issues fixed between releases. i was hoping moving to cloud would give us more options, but i'm still not seeing anything promising. i want to be able to go to jira and get this list without having to export to excel and doit that way.

for those who havent fought with it before, no, it doesnt really query based on the position the version is in your list, no it doesnt do it based on date either, i have put in many a ticket in with attlasian over the years and it just plain doesnt work reliably. you may get expected results here and there which makes it very confusing, but they dont promise you will always get what you are looking for.

i saw "version manager" but AI said they dont say they support this querying. has anyone used it and found that to be incorrect, or has anyone found anything that does work?

[Prosper Agwegiokhe]

Hi @Alexandria _Lexi_ Codd,

Welcome to the Atlassian Community!

My name is Prosper, a support engineer at Appfire, and I’m here to help.

If you are open a plugging suggestion, I recommend trying our App JQL Search Extension for Jira.

We have several helper functions you can use for finding issues between version release date for example: 

fixVersionReleaseDate < now()

This query returns issues with a release date earlier than today.

For more details about these queries, feel free to refer to the documentation, and don't hesitate to reach out to our support team if you have any further questions.

We’d be happy to assist you!

Best regards,
Prosper.

[Alexandria _Lexi_ Codd]

this may work for us, thank you, will try this out

[Hannes Obweger - JXL for Jira]

Hi @Alexandria _Lexi_ Codd

do your fix versions follow a particular naming pattern? And/or do they have a meaningful release date set?

If either of these is true, your use case should be easy to solve using the app that my team and I are working on: JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also

• comes with a long list of so-called smart columns that aren’t natively available, including the fix version release date (along with many other version-related smart columns), and

• allows advanced text filtering on your issue's fix version names, e.g. based on regular expressions.

Depending on your data shape, these should allow filtering your issues by fix version ranges. E.g., this is how it could look based on the fix version release date:

As you can see above, you can easily sort and filter by your fix version release date, and also use it across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

All this just works - there's no scripting or automation whatsoever required.

If a naming-pattern-based approach would be a better fit, I'm happy to elaborate on that, too!

Any questions just let me know,

Best,

Hannes

[Alexandria _Lexi_ Codd]

this looks very promising, will trial this out with my release manager. we do use semantic versioning

[Kit Friend]

I can't find a good fix for this either to be honest. 

Of the options, I feel like using Automation to create some kind of searchable/indexable tag would probably give you the best outcome. 

----

Sense check from GPT: 

You're not alone in your frustration! JQL's handling of versions and the lack of a robust, out-of-the-box solution for querying issues between specific versions is a long-standing limitation many of us have faced. Unfortunately, as you've discovered, there's no reliable "issue in version > X and < Y" functionality in Jira Cloud natively, and Atlassian hasn't prioritized fixing this over the years.

Why JQL Struggles with Version Ranges

The crux of the problem is that Jira doesn't inherently understand the sequential relationship between versions in the way you're expecting. It doesn't treat versions as ordered by release date or rank them consistently. Even when using fixVersion or affectedVersion, you may find inconsistent or unreliable results because these fields don't support true range-based logic.

Options to Address This Problem

1. Third-Party Apps

• Version Manager for Jira (by Decadis): While Version Manager doesn't explicitly advertise support for querying issues between versions, it does allow you to create structured version hierarchies and associate versions with release dates. Some users report success in filtering issues between versions indirectly by using custom version management. It's worth testing the free trial to see if it works for your case.
• ScriptRunner for Jira: With ScriptRunner, you can extend JQL functionality by creating scripted fields or advanced queries. A common solution is to script a custom JQL function that calculates issues with fixVersion between specified versions based on release date or version order.
• JQL Search Extensions for Jira: This app provides enhanced JQL functions, and while it doesn’t directly solve the "between versions" problem, it might give you workarounds for more precise filtering using dates or other metadata.

2. Custom Fields for Date-Based Filtering

• If you're tracking version release dates, consider setting up custom fields or automation rules that stamp issues with the version's release date or a range. This allows you to use date-based JQL like:

  issueFunction in dateCompare("releaseDate > '2023-01-01' and releaseDate < '2023-12-31'")
  

3. Export to Excel or BI Tools

• I know you’d prefer a solution directly within Jira, but exporting remains a practical fallback if no better options work for you. Alternatively, connect Jira to a business intelligence tool like Power BI or Tableau for dynamic querying on version ranges.

4. Automation Rules

• Use Jira automation to label issues when they transition to a specific release or version. For example, when an issue is assigned fixVersion, automatically add a label or custom field indicating the release sequence. Then, you can query those labels.

5. Create and Use Ordered Version Data

• If you're open to some initial manual setup, you can maintain a custom field (e.g., "Version Order") and automate or script its updates based on version release dates or a predefined sequence. This allows querying based on your own defined version order.

---

Recommendations

• If you're willing to try apps, ScriptRunner or JQL Search Extensions are your best bets for adding flexibility.
• For a no-additional-cost solution, automation rules to pre-tag issues with a release range (or corresponding dates) are likely the most reliable workaround.
• Keep voicing your concerns to Atlassian—these community requests do sometimes influence their roadmap (even if it takes years).

Let me know if you'd like help setting up any of these approaches!