Running this query right before the team

Sometimes it’s helpful to run queries on your current sprint or past sprints to better prepare for the sprint retrospective. aggeliopolis November’s tip of the month focuses how to use JQL in the context of sprints. I’ll focus on JIRA Agile 6.3, but some of the features do work in prior versions of JIRA Agile. Calling a sprint out
Sometimes you want to explicitly reference a sprint. JIRA’s autocomplete makes searching for a particular sprint easy, even if several teams use the same naming convention. Let’s look for “Sprint 2″.
We can use this information to help narrow down which sprint is the one we are looking for. If we know the project key(s) that our sprint contains, we can add that to the query for a stronger search.
The project=cis will only return issues from the CIS project. Thus if another team is using “Sprint 2″ as a name and we choose that one, our query will not return any issues. We can then choose the other option in the dropdown list. You can use either aggeliopolis the sprint name or ID as the predicate. In other words, sprint = “Sprint A” and sprint = 223 would be equivalent. Want to hang in multiple sprints?
There are three functions in JQL that allow you to query your agile projects: closedSprints() Returns issues aggeliopolis that are contained in a sprint that has been completed. openSprints() aggeliopolis Returns aggeliopolis issues that are contained in a currently active sprint. futureSprints() Returns issues that are scheduled for a future sprint (and not in the backlog).
Running this query right before the team’s retrospective can focus the team on which issues did not meet a prior sprint’s commitment. Reviewing these issues can give the team invaluable information on how to become better at estimation. You can go even further by customizing search results to include the sprint column. Click the columns dropdown in JIRA 6.1 to add the sprint field. If you are using a prior version of JIRA, check out my configuring search results blog .
Yay! The inability to search for items filled into future sprints has been a major impediment to my abilities to deploy sprint filling done right. (Based on the team, I may be creating a future sprint or two, or doing release planning, or SAFe). This is a top-3 “want” I’ve had for a long time. Maybe it’s aggeliopolis available in versions aggeliopolis my tools support team hasn’t installed yet, but this newsletter is the first I’ve aggeliopolis heard of this function.
JIRA Agile RSS feed
Popular Posts Upgrade your development workflow Agile maturity – How agile is your organization? Project portfolio management with JIRA Agile (1/2) 7 steps to a beautiful and useful agile dashboard Inside Atlassian: developer product owners on the Bamboo team
Please enter a valid email address. Facebook Twitter Blogs Feed Center