In the team Explorer, Change Default State value of a selected Work Item to "Associate" instead of "Resolve" on Check In
In the team Explorer, Change Default State value of a selected Work Item to Associate instead of Resolve on Check In. In VS 2012, our team often closed the work item because Team explorer Automatically chooses Resolve instead of Associate in team Explorer. Its really Annoying. In most scenarios, the developer is going to associate lots of check ins for a task. they resolve the task only once , when the task is completed. so its better to make a default value as an associate instead of Resolve. or At least given an option to choose an default value. Thanks.
Jens Neubauer commented
We recently started working more heavily with work items, and this behavior is incredibly annoying. I would give it more than 3 votes if I could
Joberto Diniz commented
Is this going to be fixed?
I think the best solution is to add option to settings that can switch this
The default here needs to change to "associate". As Gregg mentions, most tasks are only resolved after multiple check-ins. On top of that if the overall project is using an automated server build, test & deploy mechanism you can't possibly say the item is resolved at check-in as you need to see the unit tests, deploy & UI tests have passed on the build server before you can say the work item is complete.
It's a painful UI experience because the work item status is used in most of the work item views & the my work mechanism. Once the work item is transitioned to resolved(closed) it disappears from these lists so you have to go and find it again to set it back to in progress. I've lost count of the number of times I've had to do this.
Brian List commented
This problem does not bode well for us being able to make the switch to VS2012.
Gregg B. Jensen commented
I agree, this should always default to Associate and not resolve. Most developers check in multiple times per task or story. It should be a conscious choice to resolve the item.
Tom Zschaage commented
There is already a registry key available to set the default. However it is not used in VS 2012
Stephen John Anderson commented
It's also fairly common for workflows to require additional fields to be set on a work item before it can be resolved; if you commit without entering required values, VS2012 fails to associate the changeset.