• Icon: Suggestion Suggestion
    • Resolution: Fixed
    • None
    • Navigation - Filters
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Often I want to see the issues relating to the next issue to be released. Similar to the dashboard, we should be able to sort and save filters on the next released version.

            [JRASERVER-1357] Allow filter by "Next Unreleased Version"

            Ariel Porath added a comment - - edited

            Is there any chance to bring this back? It's been 19 years and people still need it today.

            Just give us nextUnreleasedVersion() JQL function.

            It will help us a lot and save years of manual work.

            If there is a way we can help open source it will be cool.

            Ariel Porath added a comment - - edited Is there any chance to bring this back? It's been 19 years and people still need it today. Just give us nextUnreleasedVersion() JQL function. It will help us a lot and save years of manual work. If there is a way we can help open source it will be cool.

            If you name your versions carefully, this can work - e.g., 2018_01.1

            david greenfield added a comment - If you name your versions carefully, this can work - e.g., 2018_01.1

            I know this is old and dead thread but for future people reviewing it from google.

            This function appears to use the order of the "Versions" in the list NOT the dates associated with them. Also note the list earliestUnreleasedVersion() function expects the next list to be ordered with the old/next versions on the bottom of the list with future versions on the top. (I.E. From top to bottom: Release 6 -> 5 -> 4 -> 3 -> 2 -> 1 NOT Release 1 -> 2 -> 3 -> 4 -> 5 -> 6)

            Matthew Forman added a comment - I know this is old and dead thread but for future people reviewing it from google. This function appears to use the order of the "Versions" in the list NOT the dates associated with them. Also note the list earliestUnreleasedVersion() function expects the next list to be ordered with the old/next versions on the bottom of the list with future versions on the top. (I.E. From top to bottom: Release 6 -> 5 -> 4 -> 3 -> 2 -> 1 NOT Release 1 -> 2 -> 3 -> 4 -> 5 -> 6)

            Thanks Wim, you are correct. This issue has slipped under our radar. I will close this issue as fixed.

            For those interested an example JQL would be simply:
            fixVersion = earliestUnreleasedVersion("JIRA")

            Roy Krishna (Inactive) added a comment - Thanks Wim, you are correct. This issue has slipped under our radar. I will close this issue as fixed. For those interested an example JQL would be simply: fixVersion = earliestUnreleasedVersion("JIRA")

            Wim Deblauwe added a comment - Is this not already covered: http://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-earliestUnreleasedVersion

            Dave Myron added a comment -

            Is there an existing nextUnreleasedVersion JQL function? The list at the link in Scott Farquhar says it's the complete list, so I'm assuming no. What is returned by functions? Can we use array notation to grab the first (ala unreleasedVersions()[0] ... I doubt it)?

            Would someone with JQL function-writing experience whip up an official version?

            Dave Myron added a comment - Is there an existing nextUnreleasedVersion JQL function? The list at the link in Scott Farquhar says it's the complete list, so I'm assuming no. What is returned by functions? Can we use array notation to grab the first (ala unreleasedVersions() [0] ... I doubt it)? Would someone with JQL function-writing experience whip up an official version?

            Would be great to avoid having to update my filters after each release

            Wim Deblauwe added a comment - Would be great to avoid having to update my filters after each release

            Walden,

            Thanks for throwing your weight behind this. I suggested to the development team that they develop 'functions' for JQL, and it was this particular use-case that I had in mind for functions.

            I'm afraid that this isn't currently scheduled, but if you have some basic java skills, you may be able to write something over a weekend?

            http://confluence.atlassian.com/display/DEVNET/Plugin+Tutorial+-+Adding+a+JQL+Function+to+JIRA

            Sorry I can't be of more help - perhaps someone in the community could jump in here?

            Scott Farquhar added a comment - Walden, Thanks for throwing your weight behind this. I suggested to the development team that they develop 'functions' for JQL, and it was this particular use-case that I had in mind for functions. I'm afraid that this isn't currently scheduled, but if you have some basic java skills, you may be able to write something over a weekend? http://confluence.atlassian.com/display/DEVNET/Plugin+Tutorial+-+Adding+a+JQL+Function+to+JIRA Sorry I can't be of more help - perhaps someone in the community could jump in here?

            Walden added a comment -

            Let me add my voice too. This would be a great enhancement. In my mind it could start as simple as a JQL function called NextUnreleasedVersion() that we could use in our where clause. It could grow from there to be more, but don't let the perfect be the enemy of the good.

            Walden added a comment - Let me add my voice too. This would be a great enhancement. In my mind it could start as simple as a JQL function called NextUnreleasedVersion() that we could use in our where clause. It could grow from there to be more, but don't let the perfect be the enemy of the good.

            Adding further - when development teams are working in iterations/sprints it would be useful to display the next major/master release ignoring the iteration releases

            Reena Patel added a comment - Adding further - when development teams are working in iterations/sprints it would be useful to display the next major/master release ignoring the iteration releases

            Jeff Lamb added a comment -

            Adding to this request, I'd like to see "Last released version" as an option as well.

            Jeff Lamb added a comment - Adding to this request, I'd like to see "Last released version" as an option as well.

            We are also interested in this feature.
            We have a portalpage showing a pie chart for each unresolved version. Therefor we need filters including the specific version. When a version is released we need to edit the filter so it filters for the new unreleased version.

            Is there any other posibility to show pie charts for the next versions.
            For example a pie chart plugin that accepts 2 dimensional data, showing number of second dimenstion pie charts?

            Frank Jahnke added a comment - We are also interested in this feature. We have a portalpage showing a pie chart for each unresolved version. Therefor we need filters including the specific version. When a version is released we need to edit the filter so it filters for the new unreleased version. Is there any other posibility to show pie charts for the next versions. For example a pie chart plugin that accepts 2 dimensional data, showing number of second dimenstion pie charts?

            osolage added a comment -

            I too have wanted this feature. I think it would be very helpful in presenting to product owners the list of enhancements/bug fixes that the development team is proposing or working on. I also think this kind of filter would work very well when displaying a list of jira issues in confluence.

            osolage added a comment - I too have wanted this feature. I think it would be very helpful in presenting to product owners the list of enhancements/bug fixes that the development team is proposing or working on. I also think this kind of filter would work very well when displaying a list of jira issues in confluence.

              Unassigned Unassigned
              scott@atlassian.com Scott Farquhar
              Votes:
              18 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: