375 votes5 comments · Azure DevOps (formerly Visual Studio Team Services) » Work Item Tracking · Flag idea as inappropriate… · Admin →
As explained in this blog post (http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/08/how-we-use-user-voice-to-make-a-better-product.aspx), we had updated the status of this suggestion to “Under Review” to let you know we are tracking it on our backlog. To better indicate which one we are actively working on or which ones are on our 6-month plan, we introduced the states “Started” and “Planned”. The goal is to give an update on in progress suggestions at least every 3 months. This suggestion is still on our backlog, but they are not part of the 6-month plan.
Ewald HofmanJason McAdams commented
Another use case that I've been wanting this for... We determine estimates up front from a project management team prior to development for purposes of prioritizing the backlog with operations. The developers also put their estimates on an item when it is assigned to them (we don't know who we are going to assign it to up front, so we can't ask for this estimate until it's ready for development). We don't want the developers to see the PM estimates as it sways their opinions. They don't want to go over that estimate since they feel like it makes them a lesser developer. So they tend to keep their estimate the same while trying to speed up or slow down development to match it. This makes it very difficult to gauge if our PM estimates are correct as well as hindering development to a degree.Jason McAdams supported this idea ·