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

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

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

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

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.

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)

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

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

pschaff,

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

(I agree that future sprints need to be first class citizens, and have no problem with giving them a date, as long as it's changeable.)

Future sprints do not need a date. Sprint 10 starts immediately after Sprint 9, no matter when Sprint 9 ends.

Future sprints should really have a date. Otherwise how can we know when they will occur?

I realize that it can be inferred from the Sprint number, times the sprint length, relative to the progress of the current sprint etc, but quite often people looking at the future sprints will be non-Development people and won't be involved in the day-to-day making that kind of calculation tricky. This is particularly important for when you have a story which needs to be delivered for a particular external milestone, a pretty common use case in Enterprise software.

Or when you are elaborating out the expected sprints in a year long project and you want to see what date Sprint 10 will leave you with.

It can be worked around in a limited fashion by encoding the start date into the sprint names, but it would be much better if the future sprints were first class citizens like the active and historical ones are and provided the dates.

This is in response to the comment in the description that future sprints have no date.

Same problem here.

One question, if I want to store the future sprint value so I can query for it later, do I have access to an identifier other than the future sprint name (that changes a lot)?

Thanks, Viðar

I tried to access that link without success. Is that link for Atlassian staff only?

Database workaround

In case anyone wants to retrieve this information via database, here is a KB for it:

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

I would be very interested in Thomas Jespens solution using the scriptrunner ("I have to use the scriptrunner plugin to semi-automatically insert sprint names into the extract.")
Is there a way to communicate this solution to me/to the board?

Thanks

Same here, we do exports of the backlog and I have to use the scriptrunner plugin to semi-automatically insert sprint names into the extract. This would be much easier with future sprints shown in the already present sprint field.

Best regards
/Thomas Jepsen

From: Andreas Walsh (JIRA) jira@atlassian.com
Sent: 20. juni 2013 03:32
To: Thomas Jepsen
Subject: [JIRA] (GHS-5773) Ability to use the Upcoming Sprint value or name in JQL searches

https://jira.atlassian.com/s/en_UKkdyw0-1988229788/6097/9/_/images/icon-jira-logo.png

https://jira.atlassian.com/secure/useravatar?avatarId=10612Andreas Walsh<https://jira.atlassian.com/secure/ViewProfile.jspa?name=andreaswalsh> commented on [Story] GHS-5773<https://jira.atlassian.com/browse/GHS-5773>
Ability to use the Upcoming Sprint value or name in JQL searches<https://jira.atlassian.com/browse/GHS-5773>

I strongly second this need for future sprints to be first class citizens.

I just had a request from the Documentation Team on what sprint will a particular story be delivered. I was going to tell them to just open the story and they would see the sprint. But of course they don't see it because the sprint is not active yet.

Not only that but I can't even say "click the 'View on board'" link as they then don't know which of the 10-15 boards that contain that story is the magical one which contains the future sprint.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

I strongly second this need for future sprints to be first class citizens.

I just had a request from the Documentation Team on what sprint will a particular story be delivered. I was going to tell them to just open the story and they would see the sprint. But of course they don't see it because the sprint is not active yet.

Not only that but I can't even say "click the 'View on board'" link as they then don't know which of the 10-15 boards that contain that story is the magical one which contains the future sprint.

As per my earlier post, for planning our requirements is to be able to access all future sprints. As well as JQL searching we need it built in as a column - so that we can export a view of what is coming up in all future Sprints. In other words future Sprints numbers should have all the support that past Sprint numbers have.

It's great that this is being addressed. Please don't forget that querying on the backlog is just as important for many users as the future planned sprints!

I second Fabian's question.

How I understand the original request, is that there is a need to see the "next" upcoming sprint (i.e. next single sprint if their are multiple planned/upcoming), a JQL function similar in vein to earliestUnreleasedVersion() https://confluence.atlassian.com/display/JIRA052/Advanced+Searching#AdvancedSearching-earliestUnreleasedVersion

The current available functions for sprints do not return this information (openSprints(), closedSprints()).

npetrov, is the function futureSprints() going to work like this?

sprint in futureSprints()

I just want to avoid confusion about what has been implemented and what this actual request is about.

Thank you for addressing this!!

Can you provide any target date for when this would get released?

Thanks and regards,

Gail Park

on GHS-8662-sprint-buckets

no changes necessary to work, developed futureSprints() jql function as part of this story.

Hi All,

Many thanks for your comments and votes on this issue, I wanted to provide an update. We recognise this as a missing feature in the new boards and plan to address this within the next 6 months.

Kind regards

Tom Kotecki
Product Manager, GreenHopper

To me, the current functionality is a big step backwards. Sprints are a key aspect of planning and to make it this difficult to slice and dice a backlog is extremely poor functionality.

We too need this feature. We use workload graphs to make sure we don't overload the teams from an hours perspective (as we sometimes look from a role perspective and can't rely on the simply total in the burndown). Unfortunately the query for the graph only works if the sprint is active, which means we have to "start" the sprint before/during our planning session. It's not uncommon for us to move stories in or out of a sprint during the planning session based on team conversations. We don't consider the work in the sprint committed until the planning session ends. This means that since we had to start the sprint at the start of planning (to use the workload graph), the sprint report is nearly useless to us as there are many items listed as "removed from sprint" that were moved on the planning day. Similarly, point changes made during planning are not reflected because they changed after the start button was selected.

In other words, lack of this feature means for us we either can't do capacity planning for a sprint within JIRA or we can't rely on the sprint report. It would be great to do both.

Useful, but if I understand Jamie's comments he is saying he does not do this via JQL and he himself is expecting Atlassian to expose it in JQL at some point.

As has been pointed out past and current Sprints ids are accessible. So it would be great if future sprints were available in the same field so they could be used out of the box with all the existing searching and reporting tools. Currently I am duplicating the Sprint# in the Fix Version field and manually sync'ing the two up every week.

If Atlassian could let us know if an enhancement is planned. If not I may consider ScriptRunner.

You guys should have a look at this JQL function of Jamie's infamous ScriptRunner plugin:

inSprint(board name, sprint name)

Example:

issueFunction in inSprint("My board", "Sprint 1")

Finds issues in the given sprint. This works for sprints that are not yet started, active, and completed sprints.

Source:
https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions#ScriptedJQLFunctions-Agile

With the release tags we tag everything in upcoming sprints and active sprints that form part of the next release. This means you can report on what is planned for the next release and can track work in the current sprint. I agree it would still be nice to report on what stories are in which sprints even if they are not yet active, maybe this could be seen on the release report.

A feedback from Atlassian would be more than appreciated.

Thanks.

My team will not use the new Greenhopper boards until this issue is resolved. It makes Sprint the cultural change in Sprint planning to great.

This is driving me nuts. Please implement a way to query for stories in future sprints and backlog. I don't understand why can't I just get a filtered search for everything only in a future sprint or the backlog. Seems extremely important for planning. I am not sure what fixVersion is or what is 'classic board', but I am just switching from another tool, and as a PM this renders Greenhopper useless.

This feature is actually quite important. Upcoming sprints are only visible in the Agile Board in which they were created and are not visible in Jira.

That means that if I open a Story in Jira and it is scheduled for an upcoming sprint I can't see that. So I don't know whether it's scheduled or not.

Taking it a step further let's assume that I have an inkling that it has been scheduled. When I click on View on Board I have to know which of the multiple boards it has been created on. Not only that but I can't just pick my preferred Board. I have to know which one it is in.

This also means that I can't see multiple teams' planned sprints together. If I have one team for a product in location A and another team for the same product in location B then they will likely have their own Agile Boards which they use for planning. However, if I want to see on overview of the upcoming sprints across both teams and their boards it's currently impossible.

For all these reasons this is really quite an important piece of functionality. As Classic Boards are going to be deprecated features like this really need to be put in place.

We desperately need this feature to facilitate planning & forecasting. The workaround of manually updating/maintaining the "fixVersion" is painful, I would like the "Sprint" field to update automatically even if the Sprint isn't active so I can query on this field & export reports to Excel for Backlog Status reporting.

I would like to see something like:

sprint in plannedSprints()

It is really a missing key-feature in GH. Currently, for each version we plan, we create a new board (we named them "Roadmap for version X.Y.Z). Each board contains several sprints (one or more "main sprints" for feature development and planned bug fixes, followed by QA/Post QA sprints). Everytime a sprint is started, the developers switch to a new filter "project = OPENFLEXO AND Sprint = "1.5.1" ORDER BY Rank ASC" and the filter of the board is something like this: project = OPENFLEXO AND (Sprint = "1.5.1" or sprint = EMPTY OR sprint not in openSprints()) ORDER BY Rank ASC

Now, when I do the preparation of the boards, I would like to create all the related filters at once and not having to recreate new filters everytime a new sprint is started.

We also would love this feature to added. It helps with resource planning.

We also need this feature! Putting this data into a Gantt Chart makes it easier for our project manager to visualize the progress. Including the backlog would also be a nice feature.

We also need this feature!

We also need this feature. We would like to be able to do queries against a sprint that we are in the process of planning/sizing to see the number of issues/points with certain components and also to see the distribution of assigned issues across developers before actually starting the sprint.

We also need this feature.
Would be a great support for requirement engineering, where you could see on a kanban board how far in reparation the stories are for the upcoming sprints! E.g. a swimlane for each upcoming sprint, would work like a dream!
Hope to get this soon.

The problem is, with JIRA on-demand, you can't install plugins.

You might want to consider using jamieechlin's wonderful plugin; The Script Runner.
As Jamie states here this plug-in should support searching in upcoming sprints.

This is a needed feature indeed. It is important to be able to filter / search issues based on their sprint - regardless of whether it is upcoming or past sprint.

We also need this.

We need this to help us see the division of labor before we kick off the sprint. Seeing the total hours / story points is useful. But what's a lot more useful is looking at a Workload Pie dashboard item and seeing how many hours each individual developer is being dealt. Then we can decide to remove/add tasks to the sprint as necessary.

If I drag a story from one sprint to another of from first release to sprint, FixVersionm, as I know, will not get automatically updated. I tried to search through JQL for epic but there is a discrepancy.

RE: Release Planning: Although I too would love to see this functionality I'm not sure it's completely necessary for release planning. The concept of FixVersion is still valid at the release level and the Classic Planning Boards are still really good for that purpose. You shouldn't have to plan out every sprint before you size a project. Simply setting the FixVersion to the appropriate release in each Epic or Story and doing your story point estimates should get what you need from the Classic Planning Board.

We really need this one for reporting to count all story points that will be included in first release.

This affects us too. We just wanted to do an spreadsheet export of two specific oncoming sprint. Would be awesome!

This is exactly the feature we need too! I need to run a query to filter stories by forthcoming sprints including the backlog which can then be exported to spreadsheet. I realise that the backlog is a dynamic list, but we need to capture and communicate at certain times. Allocating SprintIDs to forthcoming sprints and the backlog would allow filtering that way.

Searching by name would be a bad idea since it gives you no flexibility. Let me describe our use case and the reason I filed this as an issue with Atlassian support:

I tried to search for issues that are in future sprints but I was not able to find a solution.

sprint in openSprints()

Only finds issues that are in an active sprint.

sprint not in openSprints()

Finds all issues from former and future sprints.

I am asking for a query that returns all issues that associated to planned sprints. After some more research, it turns out that they actually have no value for the Sprint custom field associated and future planned sprints are defined via a marker value. Thus it will be difficult to identify the issues associated with them. Please discuss the matter with a developer and let us know if there is a way to identify them. A workaround would be acceptable.

This screenshot should clarify what we want to achieve:

@Tom Corcoran - No. This issues addresses 'upcoming sprints' which technically don't have a sprintID yet.
The issue you link to assumes you have started (multiple) sprints already and want to search those.

If searching by name is indeed the way to go, then this issues might be considered duplicate. Untill no solution is given, its not duplicate

@Alyssia Byers - is this not a duplicate of GHS-4949 ?

This is something we're trying to do as well. Filtering upcoming sprints makes it a lot easier to get the total estimate of pre-assigned tasks. Now this is not possible.