Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-5773

Ability to use the Upcoming Sprint value or name in JQL searches

XMLWordPrintable

    • 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.

      I'd like to have the ability to use the notion of Upcoming sprint in JQL searches.

      For instance, I have planned 2 sprints ahead of the current open sprint. I'd like to be able to filter separately the issues planned in upcoming sprints 1 & 2, using the advanced search. I would use this search query to create swimlanes in Kanban boards or create structures within the Structure plugin.

      Note that future sprints don't have a date so autocomplete needs to be revisited.

      Workaround via database:

      https://confluence.atlassian.com/display/JIRAKB/How+to+find+issues+from+non-started+sprints

        1. planned_sprints_search.png
          planned_sprints_search.png
          29 kB

            [JSWSERVER-5773] Ability to use the Upcoming Sprint value or name in JQL searches

            Steven F Behnke added a comment -

            This feature is not documented on the JQL Advanced Search - Functions page.

            Steven F Behnke added a comment - This feature is not documented on the JQL Advanced Search - Functions page.

            Erdal Kurt added a comment - - edited

            still it would by easyer an more usefull to have somthing adequate to "FutureSprints()"
            something line and sprint in ("nextSprints()")
            this mwould help in case of multiprojects with different sprint ids an sharing ressources

            Erdal Kurt added a comment - - edited still it would by easyer an more usefull to have somthing adequate to "FutureSprints()" something line and sprint in ("nextSprints()") this mwould help in case of multiprojects with different sprint ids an sharing ressources

            Louella Chang added a comment -

            Thank you! I guess I just have to wait for my organization to install the update.

            Louella Chang added a comment - Thank you! I guess I just have to wait for my organization to install the update.

            Normand Carbonneau added a comment -

            Louella, they delivered that functionality already. It is now working.

            Normand Carbonneau added a comment - Louella, they delivered that functionality already. It is now working.

            Louella Chang added a comment -

            I need this functionality too. I created a Confluence page to display the status (e.g., completeness) of issues slated for the next sprint. I use it for backlog grooming and sprint planning. So every time I start a sprint, I can more easily determine what needs to be completed to start the next one. Since I use this regularly, I would prefer having this functionality rather than using the work-around which requires me to change my filter with each sprint start. Please re-open this ticket.

            Louella Chang added a comment - I need this functionality too. I created a Confluence page to display the status (e.g., completeness) of issues slated for the next sprint. I use it for backlog grooming and sprint planning. So every time I start a sprint, I can more easily determine what needs to be completed to start the next one. Since I use this regularly, I would prefer having this functionality rather than using the work-around which requires me to change my filter with each sprint start. Please re-open this ticket.

            Rene Rath added a comment -

            got another workaround: looks like you cannot JQL-query by sprint-ID, but by sprint name. If you have given an un-started sprint a name, the JQL-command "sprint" works: e.g. if you have a sprint named "SprintNumber7", this JQL-Command should work: sprint in ("SprintNumber7")

            (found here: https://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-Sprint)

            Rene Rath added a comment - got another workaround: looks like you cannot JQL-query by sprint-ID, but by sprint name. If you have given an un-started sprint a name, the JQL-command "sprint" works: e.g. if you have a sprint named "SprintNumber7", this JQL-Command should work: sprint in ("SprintNumber7") (found here: https://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-Sprint )

            Nabil Sayegh added a comment - - edited

            The workaround page is 404

            Nabil Sayegh added a comment - - edited The workaround page is 404

            MicahF added a comment -

            @gailpark: https://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-Sprint

            MicahF added a comment - @gailpark: https://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-Sprint

            gailpark added a comment -

            Please can you advise when this functionality will be released - I see from the ticket it is resolved.
            Thanks

            gailpark added a comment - Please can you advise when this functionality will be released - I see from the ticket it is resolved. Thanks

            Matt McClure added a comment -

            pschaff,

            The link in your "Database workaround" comment is Not Found. Do you have an updated link?

            Matt McClure added a comment - pschaff , The link in your "Database workaround" comment is Not Found. Do you have an updated link?

              Unassigned Unassigned
              b3fde8644c21 Jérémie Skornik
              Votes:
              143 Vote for this issue
              Watchers:
              128 Start watching this issue

                Created:
                Updated:
                Resolved: