• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 1
    • 4
    • 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.

      Problem Definition

      Currently, in Jira there is an option to search for future Sprints by name, however the customer would want to have ability to search for next Sprints

      Suggested Solution

      Add possibility to query for something like:

      project = "XXX" Sprint in ("nextSprint() + 2")
      

      Workaround

      Search for issues in future Sprint by name

          Form Name

            [JSWSERVER-15265] JQL - Ability to search for next future sprints

            Justin HP added a comment -

            +1

            Justin HP added a comment - +1

            +1

            +1

            +1

            +1

            +1

            cbertelson added a comment -

            This would be VERY useful!

            Confluence is my best option for keeping stakeholders updated on their BI requests.  We use multiple sprints as scheduling 'buckets'.  Futuresprints() vs opensprints() does not offer the flexibility I need to display the issues by sprint.  If the stakeholders have something easy to read, they wouldn't have to ask me!

            cbertelson added a comment - This would be VERY useful! Confluence is my best option for keeping stakeholders updated on their BI requests.  We use multiple sprints as scheduling 'buckets'.  Futuresprints() vs opensprints() does not offer the flexibility I need to display the issues by sprint.  If the stakeholders have something easy to read, they wouldn't have to ask me!

            It is definitely more a must have than a nice to have! Cloud or Server both deserve this enhancement 

            Thanks

            Beatrice.Dutoit added a comment - It is definitely more a must have than a nice to have! Cloud or Server both deserve this enhancement  Thanks

            Kevin Martin added a comment - - edited

            this is one of many frustrating gaps in the product. a capability to pass parameters like futuresprints(rank, 2) to get top next 2 ranked future sprints would greatly enable a dashboard that can show if we have hit our target of 2 future sprints of 'ready' work before sprint planning. as it stands, the potential noise of all future sprints is too much to be useful.

            alternatives like a readiness or workflow of the future sprint, ie sprint 'ready' vs 'planning', could also meet the need to examine future sprints

            Kevin Martin added a comment - - edited this is one of many frustrating gaps in the product. a capability to pass parameters like futuresprints(rank, 2) to get top next 2 ranked future sprints would greatly enable a dashboard that can show if we have hit our target of 2 future sprints of 'ready' work before sprint planning. as it stands, the potential noise of all future sprints is too much to be useful. alternatives like a readiness or workflow of the future sprint, ie sprint 'ready' vs 'planning', could also meet the need to examine future sprints

            This would be VERY nice.

            I cannot find an issue for CLOUD, does that not exists yet? Anyways, we would need it on CLOUD.

            Stine Søndergaard added a comment - This would be VERY nice. I cannot find an issue for CLOUD, does that not exists yet? Anyways, we would need it on CLOUD.

              Unassigned Unassigned
              mgocevska Maja (Inactive)
              Votes:
              73 Vote for this issue
              Watchers:
              46 Start watching this issue

                Created:
                Updated: