Is there a way to add a Days left to the Finish Date date in the Backlogs/Queries view?
The days remaining is only applicable on the Overview (team homepage) and the Sprint view.
The days remaining is a team feature and is not relevant on the Backlog which is a view optimised for the Product Owner and Product Planning. Sprint/Iterations are tactical, Backlogs are strategic.
There is no way, on a query, to know which sprint is of interest. Queries are not team aware and thus cant show team data like sprint dates and time remaining. The Query would not know what team you wanted to see data for...
Related
I have a TFS query that pulls in data from recent sprints, in order to display a chart on our dashboard. However, as documented:
When a chart contains more than seven items within the data series, values in the eight-plus items are consolidated into a set labeled "other"
This is exactly what happens with us. The first few Iterations on the chart are static, and as every Iteration passes by, the "Other" row increases.
How can I alter my query to only pull in the last seven iterations? I can't do something like Iteration ID >= #Current Iteration - 6 because #Current Iteration is supported only for Iteration Path, not Iteration ID.
There isn't any way to achieve this through in TFS for now.
However for VSTS, it's added now.
The deployment of this feature to all VSTS accounts is now complete.
You can find full details in our Release Notes
(https://learn.microsoft.com/en-us/vsts/release-notes/2018/mar-05-vsts#query-work-across-the-iteration-schedule-with---currentiteration).
TFS customers can look forward to the feature in a future feature
update.
Source Link
Query work across the iteration schedule with +/- #CurrentIteration
The #CurrentIteration macro that helps your team track work based on your iteration schedule now supports integer offset. Easily keep tabs on the work that didn’t get closed with #CurrentIteration - 1, or look ahead at the work planned for future iterations with #CurrentIteration + 1. See the #CurrentIteration post on the Microsoft DevOps Blog for more information.
Update:
Logical expression: Work Item Type = any And State= any AND (Iteration= CurrentIteration OR Iteration= CurrentIteration-1 OR...)
Working on updating the Dashboard in TFS for a new sprint. I have a chart which shows a "Chart for Work Items" widget with a "Stacked area" chart of all the stories which is stacked by "state". Then, I have the stories plotted using "Aggregation" and "sum" along with "Effort". This worked in the previous sprint. For the current sprint the Configuration area doesn't show "sum" anymore just "count". Showing number of stories isn't as meaningful as number of story point (effort).
(I thought perhaps the stories on my current sprint were generated with a different template and this is what broke the query or configuration tool for the plot. But I moved a story from previous sprint and let it be the only one in the current sprint and that did not work.)
The current version of TFS I'm running is "Version 15.117.27024.0"
Previous sprint (works)
Current sprint (does not allow selecting Sum)
The problem is that you didn't select the appropriated Column Options which are available for Sum action.
Just check the query "Sprint9", make sure you have selected the columns such as: Effort, Remaining work, Completed work etc which are available for Sum action.
In VSTS Column Options aren't just what columns you see on the query page - they reflect fields can be used by the query too.
Open the Column Options menu:
Select Add Column and select field relevant, i.e, Story Points:
I have the following filter to find issues in current Sprint:
resolution is EMPTY AND assignee = currentUser() AND Sprint in openSprints() ORDER BY priority DESC, created ASC
It works as expected. However, our team creates separate "sprint" (in futureSprints()) for stretch goals and I'm unable to query them without picking up the rest of the backlog. However, this stretch goal sprint is always the next one in our list. Moreover, if current sprint is called "Sprint 20-2016", the stretch goals will be called "Sprint 20-2016 Stretch Goals". This means that I can retrieve the stretch goals by grabbing the name of the current sprint. For example, the following hardcoded solution works:
resolution is EMPTY AND assignee = currentUser() AND Sprint in futureSprints() AND Sprint = "Sprint 20" ORDER BY priority DESC, created ASC
Problem is that instead of "Sprint 20" being hardcoded I want something like Sprint = [name of first entry from] openSprints() but don't know how to express this in JQL. Alternatively, since stretch goals are always in the next sprint, something like Sprint in [first entry in] openSprints() + 1 would work as well.
Adaptavist Scriptrunner adds a plethora of extra JQL functions.
One of which is nextSprint
nextSprint("Board Name")
I use it to generate statistics for our next planned 3 week sprint as well as feed a dashboard for users that complete their work early and are looking to pull issues from the next sprint into the current. Generally we pull by stack order, but with as much dynamic work as we have a dashboard gives us a bit more flexibility that a scrum board doesn't offer.
How about:
(sprint in openSprints()) AND (sprint not in futureSprints())
I wish I could find a way to reference the next 'top' of the board Sprint. However, I think if you are using a naming convention, like Stretch Goals', I would put my filter as
Sprint = Stretch Goals and sprint=futureSprint()
I tried using the word Like, but found out that it is not supported and JQL as it is does a 'Like' search. Using the FutureSprint() check you will not get
I would like to get a summary report of my sprints and what happened with my tickets. I'd like to see aggregations by epic, then by story, with the leaf level being the subtickets on a story item.
Is there any way to do this? I Can get the particular sprint's information, but that's as far as I've gotten.
project = "ADS Agile" AND assignee = MYNAME AND resolution in (Completed, Fixed, "Cannot Reproduce", Approved, "Won't Fix", Duplicate) AND sprint = 100 AND resolution = Completed ORDER BY summary ASC, key ASC
//edit Example output;
T Key Summary Assignee P Status Resolution Created Updated Due Time Spent Original Estimate
Sub-task AGILE-35
AGILE-30 (New) Decide whether to use existing system.
Anne Normal Closed Completed 01/12/15 01/15/15 2 hours 2 hours
Story AGILE-31
As the PO of ss, I'd like tests for each path.
Anne Normal Closed Completed 01/05/15 01/29/15 1 week, 4 days, 1 minute 4 days, 4 hours
Probably the easiest way to do it would be to run the query you have now and then export it to Excel. You should be able to do the aggregation you want within Excel.
In the list of query results, select the columns you want before exporting to .csv. Easier than eliminating from Excel.
Reorder and organize the columns as you wish before the export as well.
Then save the query so that it appears as you wish.
Jira will never display the stories -under- the epic, which is very frustrating. But displaying the name of the epic link will do the trick.
Realizing that the original poster certainly figured this out a year ago, but thinking that others might have the same question.
I've got some problems with my TFS Burndown Chart. I've just created an Iteration (Sprint) with no start - end date. Then added some Working Items - Tasks each with their corresponding start - end date (lets say 10/06/2014). 6 days have passed since I realized that my whole Iteration (Sprint) did not have start - ending dates (10/06/2014 - 27/06/2014), so I've added those, but now... my Burndown chart is showing the progress only from dates 16/06/2014 to the current date, up to the finish date: 27/06/2014
Most of My Working Items (tasks) inside the Iteration - Sprint have their Start, In Progress and Finished within the current dates: 10/06/2014 - 16/06/2014.
Please Advice.
Not sure how your tasks have starting/ending dates. I thought all the default templates had Work Remaining on Tasks. Anyways, the burndown operates off the Work Remaining fields of the Tasks, you need to update that appropriately.
You should set start and end dates for the sprints themselves. Without start/end dates for the sprint itself, it can't project how much time you have left given the total task work at the beginning of the sprint. An iteration path (i.e. sprint) is inherently a period of time for doing your work (i.e. 2-4 weeks).