Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-5773

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

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      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

      Attachments

        Issue Links

          blocks

          Suggestion - JSWCLOUD-6036 Get Sprint information for Issues assigned to planned (not started) Sprints

          • Closed
          is duplicated by

          Suggestion - JSWCLOUD-5923 need to be able to search on the upcoming sprints to use in filters

          • Closed

          Suggestion - JSWCLOUD-6341 Allow the use of "issueid in futureSprint('<sprint name>', <rapid board name>')" to query issues in future sprint

          • Closed
          is related to

          Suggestion - JSWCLOUD-4949 Ability to search for issues based on sprint name

          • Closed
          relates to

          Suggestion - JSWCLOUD-15265 JQL - Ability to search for next future sprints

          • Gathering Interest

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: