Hi All,

Many thanks for your votes and comments on this issue, I wanted to provide an update: this is now fully implemented as of JIRA Agile 6.3. Sprints are no longer mere markers in the backlog (they actually contain issues), and you can query them by using "sprint = " JQL. Read more on our release notes: https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.3+Release+Notes

Kind regards

Tom Kotecki
Product Manager, JIRA Agile

Hi Michael,

I've just tested this out and it seems to be exactly what we needed!

Thanks,
Petru

Hi everyone,

Please note that the "Agile Issue Panel" part of this story has been implemented as of JIRA Agile 6.3. You can now see when issues are assigned to future sprints.

Please let us know what you think.

Regards,
JIRA Agile Team

Preliminarily assigning stories to upcoming sprints is a key feature that our POs do to clarify their backlog and do cross-team synchronization. So defining the names and dates for upcoming sprints together with the ability to assign stories to those is key. All this is no problem when using FixVersion in Classic Mode. Without these options, the new RapidBoards will not be acceptable by our teams.

We really need the upcoming sprints to be associated with the Sprint custom field. Then we can do something like "Sprint in futureSprint()"

Our release manager as well as our level 2 support team wants to be able to check if a story or defect is scheduled in a sprint across 50+ boards, so unfortunately Scriptrunner does not help here (I cannot even write a custom JQL function, because GH code does not store the upcomming sprints in a format that can be queried (yet))

fabian9; As a work-around, i would suggest selecting the stories in the upcoming sprint (with CTRL/SHIFT+click), right mousebutton, view in issue navigator.
Or Jamie Echlin's excellent Script Runner plug-in, but you can't use that if you're an OnDemand customer.

I am trying to search for issues that are in future sprints but GH does not allow to do that:

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:

In addition, there seems to be not ability to search for scope changes (e.g. to easily find / report how much teams have added after the sprint started or to e.g. calculate how much of their original commitment they have achieved.

I like the idea of a futureSprint() function we could use to further analyze sprint content before we commit to it. Existing reports and gadgets could be used to answer questions about that sprint might look like (along the lines of GHS-5774) - helping us to know when we're about to overcommit based on a scarce resource at a more granular level than what Greenhopper will currently tell us.

Hi Shaun,

Thanks for the fast reply! The new GH board with the artifact “Sprint” does replace the previous “Version” based sprint divider. The bad thing with the old way is just that, it was really cumbersome to do re-planning of the backlog when sprint velocities changed and the content of ~5-10 sprints needs to be pushed forward. The new board solves that problem perfectly with the drag and drop feature of the content in sprints. Looking at Scrum from a sales/commitment point-of-view one important part is the release planning based on the backlog and sprint velocity, e.g. a product owner need to be able to answer delivery date questions in ways such as: “Based on the current team velocity and the current backlog priority your feature X will start to be implemented in three sprints and ready within 4 sprints…”.

With only one team backlog we can just look at the Plan-view of the board but a normal situation for us is that a customer feature requires work done by many teams and hence distributed over several team-backlogs. This is the reason why we would like to be able to ask an Issue, “In what sprint are you?”. The name of the sprint is suffixed with the start/end-week numbers so if we have a top-level customer requirement and it is broken down in many user stories distributed over multiple backlogs it would be excellent to be able to see the assigned sprint names in the issue browser for each user story.

Thanks,
Petru

Hi petru.dumuta,

Just to clarify, the future sprints shown in the backlog do not actually exist yet, that is, they're not real sprints and none of the issues shown inside that 'potential' sprint have been modified in any way. As a result there is no JQL way to query anything about the issues because nothing has been changed. The future sprints you see in the backlog are actually just 'ranked' items, they are stored in the linked list of all of the issues in the system that represents rank.

In the future we could potentially do something in the issue navigator like "project = x and rank > futureSprint("Future Sprint 1", "Board Name") and rank < futureSprint("Future Sprint 2", "Board Name")" but we're unlikely to be able to implement this specific feature (i.e a REST endpoint or showing the information directly in the JIRA view issue page).

Thanks,
Shaun