Provide the ability to prioritise Backlog items in a sprint backlog by dragging and dropping the item
When I am working with the sprint backlog in the new new web UI I want a way to easily re order the backlog items in the sprint.I can currently do this in the main product backlog but not in a sprint backlog
Allow us to drag and drop work items within a sprint backlog item to set their priorities in the same way that you can prioritize product backlog items.
Currently work items have no default priority value and setting the correct priority order requires setting this value for all work items.
I am currently using the tfspreview to manage my Scrum project. It seems great however it does not allow me to prioritize by dragging and dropping in the web client or team explorer within in a release or iteration (sprint). When planning large projects with multiple releases it is essential to be able to prioritize within the releases. The only way I can see right now to prioritize in those views is to change the backlog priority number which is very inefficient and not user friendly at all and hard to convince a product owner to prioritize that way.
Once product backlog items have been committed, there is no way of prioriting them within the Taskboard so the most important items are first. It does not seem to be sorted by Backlog Priority.
In the backlog of TFS 2012 you can reorganize the priorities using drag and Drop. It would be nice to also support defining parent child relation using drag and drop. This also goes for the Spint page where you should be able to prioritize the Tasks and even drag a Task from one parent to another. Currently we use Urban Turtle with TFS 2010 and have these options. I would like to keep them.
Recently had a work item that I put a fair amount of detail into. This one happened to not be code related but deployment related. I was building out a server to house code being developed in the sprints. So I setup a work item for each server and detailed the stuff that needed to be done to the server. Install OS, Patch OS, Install SQL Server... All in all there are three servers so three work items and a stack of tasks.
When I got ready to do the work. I realized that the hardware was wrong and the vendor sent me 3 new motherboards. Each server work item needed a new task, replace motherboard, a 2 hour process. Adding the task to the work item adds it to the bottom after installing the OS and other software which logically doesn't work. I wanted to drag and drop the replace motherboard task to the top of the work item and could not do that.
We knocked this one off the list today. http://www.visualstudio.com/en-us/news/2014-dec-17-vso
Fantastic that this has been completed.
Next question could be when this is available as a TFS 2013 Update 5 package for on premise install ?
This is easy in Jira - change to Jira :-)
This would help us out so much
Backlogs can become long and unwieldly.
Sometimes you need to adapt to changing priorities within a sprint.
Perhaps not textbook agile, but workflows that allow you to pivot quickly is
Brad Ellis commented
Need drag and drop capability in the hierarchy view. It is extremely difficult to manage the priorities within a feature. PLEASE PLEASE PLEASE CHANGE THIS.
Bruce Cutler commented
The new hierarchy view is almost useless without the drag and drop capability, both for reordering the priority and for placing stories (PBIs) into sprints.
Melissa Hill commented
We also need to be able to sort by Area Path and then prioritize backlog items. We have a backlog that contains items for multiple projects. We have many teams that can pick up those items in an iteration. To keep the work together to deifne minimally marketable features, we use area paths. We also have an enhancements area path that needs to be uniquely prioritized. Without being able to sort first on area path, there is no good way to prioritize the backlog.
Bob Lieberman commented
Want to do and need to do! Who ever heard of a sprint whose priorities never change once it has started?
Leslie Linard commented
Please make it possible to prioritize work items attached to a sprint backlog item as well.
Tom Spelling commented
It's odd that this isn't permitted. Why assign a random order and ignore priority?
Jeffry Van De Vuurst commented
This one has my vote. I do my initial ordering on the backlog, but it happens quite often that we need to reorder while doing the sprint planning.
Jørgen Jamt commented
I support this idea fully. This happens all the time for us. Even being able to move user stories up and down inside user stories is a need.
David Blomqvist commented
Richard: OF course I ordered them with most important first in the backlog. But then the Product owner changed priotrity. And the problem is then,. once things are in state Active they dissapear from the Product backlog. So in the complete Product backlog view you don't see them anymore. Would be much easier if you could re-prioritize in the sprint backlog or on the board.
Also see this probable duplicate and "Planned" item:
I presume if this item is "Planned" the following is also:
A similar suggestion is "Under Review" here:
In response to Richard's question (was below the fold) - Ideally you would, but sometimes a little more agility helps with managing the natural entropy of things.
After just having spent a bunch of time renumbering sprint backlog item priorities I reassigned some votes here to help make this happen sooner (approaching a year on the TFS team backlog).
It would be nice (but not nearly as important) if at the same time tasks could be similarly reordered by d&d.
I have figured out a way to do it although it isn't very intuitive it works and I am happy to be able to choose TFS as the tool now that I figured out a way to prioritize a release backlog. The way to do it is by going into the configurations under the iterations area or tab and then setting release 1 (or whatever you want to prioritize) as the teams backlog iteration by right clicking and choosing 'Set as Teams backlog iteration' then I am able to prioritize just those stories in the release if I only put children stories in the release and not the parent stories. This may not be the most intuitive way to do it but it works! You must remember to switch it back to the project/product backlog if you want to see all stories though or setup different teams for the different views. You may still want to consider allowing to prioritize in the Release and Iteration View, so when I click on the Release in the left hand navigation and it shows me all the stories in the Release, I would like to be able to just prioritize there...seems much more intuitive.
I realize also that I can prioritize the product backlog which will then reflect that priority in the Release or iteration but the problem that I ran into at that level is that I want parent child relationships and I can't prioritize children across parents then. For example, lets say I have Epic Story A with children stories: Story 1, Story 2, Story 3 and then I have parent Epic Story B with children Stories: Story 4, Story 5, Story 6. And the true priority of the Stories are Story 3, Story 6, Story 5, Story 1, Story 4, Story 2...I can't represent this on the product backlog because of the Epic Parent level. Now you could say remove that parent but then I will just have a flat view and no grouping and with 600 stories that is awful hard to navigate through. I have worked with Rally and Jazz in the past which just have you do that prioritization at the release level when your backlog is so large. So what I would like to do is move Story 3, Story 6, Story 5 and Story 1 to Release 1 and leave Story 4 and Story 2 on the backlog then be able to prioritize within the release which is a more manageable list.
You can do this already on the product backlog, You are able to define one story as a child of another by dragging it into a story but you can't do it in the release or iteration backlog which would also be nice.