Automatic State Transition based on linked Work Item State
One of the things which I feel has value in the process templates forTFS 2011 is the state changing based on the linked child items. Like how the hours aggregate up from the linked child work items to the parent item, if there is a way to get the parent work item state to transition based on the linked child item state it would be good. An example of this is when a child item state is set to "In Progress" if the parent work item is then set to "In Progess" automatically.
Automatic State Transition based on linked Work Item State
In TFS is very easy to forget to update the state of the Product Backlog Item or Bug. While in the sprint board you can drag all Tasks to done, you don't get to see the state of the Bug or Backlog Item there. You have to open each Product Backlog item to transition it to the next state. I would like this to be either more easily accessible or in some cases automated based in the state of the child items.
Let the process template be customized to be able to set the state field to "cascade" the state change to the child work items. Currently this can only be done using a custom WI control (which doesn't work on the Team Web Access site) or using API and subscribing to the state change event.
Ole Herman Kiaer commented
We really need this. This is causing a lot of extra unnecessary work.
When a child work item goes from New to Active, set parent work item to Active (if parent has state New).
When all child work items are Closed, set parent to Resolved (or Closed) if parent state is Active.
Kate Paulk commented
This needs to be the default in all templates: when any child item state moves out of New, the parent state moves out of New. When all child item states move to Closed, the parent state moves to Closed. Competitors can do this. It's not that difficult to add a rule to a TFS on-premises system to do this.
Meanwhile Team Services is causing confusion and inefficiency by not keeping parent item state in sync with child item states.
Richard Chandler commented
Frankly just cannot believe that this doesn't happen already ... you start a task ... the story goes to in-progress ... simples.
Peter Dahl commented
This would be good to have in the process template, instead of haven to create a plugin to Work with the WIT state behind tfs..
This has been very long pain point for all of us.
Adrian Brink commented
+1 i want this!
I want my Features to change to 'Active' when I start working on the User Stories
Beth Whitezel commented
It would be nice to be able to alert the assigned to of a parent based on a state change of a child as well
Charles Phillips commented
I'm trying to convert a company to VSTS and this is being pointed at as an example of MS not understanding the developer community,
Martin Norin commented
ALM team stated 2011 that it's in the backlog. How come this has not been implemented yet? We are already in the 2015 version, cant be that there are that many things that are more important then this and it takes 4 years to implement?
This should be implemented as it is annoying to have to remember to manually change the User Story state whenever you change the Task status. The main actions are Work Started and Work Completed.
An example of why this is needed:
You are working in the Task Board and you have filtered the board by Person. You now cannot see the user stories. Everyone does their work and completes all their Tasks. But from the Stories Board all of those User Stories are still sitting in the New state even though all the work has been completed.
I believe that this can be done be modifying the workflow of a work item in TFS - I vaguely remember doing this before - so it should be available on Team Services too
And as someone else pointed out below - competitor products do this and so far this is the biggest complaint I am receiving after switching over to VSTS
Another Great use would be to have a parent item (i.e. User Story) is marked as "In Progress" when one of its child items is started.
This doesn't have to be done automatically (TFS shouldn't have to 'guess' what is needed) but if it was supported in something similar to the logic engine for WITs, then Admins could specify what states could/should be updated in parent/child relationships.
Would be great if a PBI gets marked done when all our tasks are marked done. This affects our velocity if we don't go through and mark PBIs as done. Very inefficient to go through and mark PBIs done if we marked all tasks as done.
Generic Ramirez commented
When you are working on a User Story that has multiple tasks, and for whatever reason the state changed on that user story (user is no longer interested, priority changed, or simply is closed as is no longer applicable) sometimes you have many tasks and additional stories under it, as a manager is really cumbersome to go through and close all the child items once you get in that state.
I have spent many hours just cleaning up all the pending tasks for user stories that were closed already
Ahmed IG commented
This is very important, as it doesn't make sense to go through all parent work items when you have all the children work items closed.
It will make our lives way easier, neater and smarter.
TFS ASAP (http://www.tfsasap.com) exactely does this.
Will Smith commented
It's a pain to go to the PBI and change the state to Done when all of the tasks have already been completed. Either have to open the PBI and edit, or go to Kanban board (away from Sprint board)
I forgot to mention it would be nice to have this out of the box and not have to maintain our custom service.
We wrote a service to do the opposite as well. When all child items are closed we automatically close the parent PBI. It helps to keep all PBI's in sync with its actual state.
Visual Studio ALM Team commented
Thanks for submitting. We have this one on our backlog. It does keep getting pushed down, however, so any information on why this is important would be helpful.
Gregg Boer - MSFT / TFS Product Group
Manish Jain commented
You can use http://tfsaggregator.codeplex.com/