How To: Make “Associate” the default action for work items

I’ve heard this one a lot lately from many people, so I felt it was time to share more broadly.  While there is no way to do this in the UI in TFS 2010, there is a registry key that we added late in our release cycle to allow users to configure the default work item association.

To make “Associate” the default action (instead of “Resolve”), set the registry key “HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\TeamFoundation\SourceControl\Behavior\ResolveAsDefaultCheckinAction” to “False”. 

FWIW, in our next release, we’re fixing this experience so that you won’t need to hack the registry to change the behavior.

Comments (17)

  1. Michael Freidgeim says:

    The registry key is not fully visible in your post:


  2. Michael Freidgeim says:

    The registry key is not fully visible(end is hidden) in your post:



  3. cathykong says:

    Could you tell me how to do that in TFS 2010, it seems that it is not possible change work item "Associate" in registry.

  4. cathykong says:

    Sorry, I spell wrong, I mean how to do that in TFS 2012

  5. Can this registry change be done on the TFS server to affect all projects, or does it need to be done on each team member's workstation?

  6. Hi Matt,

    The registry hack seems to no longer work in VS/TFS 2012 RTM (same steps as above, swapping in "11.0").  Have not heard about anything new for "fixing the experience". Did the fix make this release? What's the status? We're currently stuck with no proper fix and no working hack either. 🙁

  7. joshka says:

    Hi Matt,

    It seems that this no longer works in 2012.

  8. Joshka – Can you try running "devenv /setup" after setting the registry key, and then restarting VS?  If that doesn't work, please email me at mmitrik at microsoft dot com.

  9. joshka says:

    Hey Matt,

    Sorry about the long wait. It seems that adding the work item to the in progress work in the My Work tab sets the appropriate status (associate). Adding the work item to the Related Work Items in the Pending Changes tab however does not (it sets the status to resolved by default). Maybe this is expected behaviour?

    I updated both VS 10 and VS 11 keys, and ran devenv /setup (for both VS 10 and 11 versions of devenv) to no avail and restarts VS 2012 to check.

  10. Chris says:

    Fixed how??  The default is still "Resolve" and the hack no longer works.  

  11. Thomas Hvilsom says:

    Agreed with Chris….this is kinda annoying. Is there a solution to this in VS2012?

    It works exactly like joshka describes….this isnt quite good enough. All my developers use pending changes to checkin, so items on our scrum board gets accidently moved to "closed" because, they accidently select resolved, when they really only wanted associate….

  12. Kristie says:

    Is there an updated fix for this issue?  It is causing issues for us as well.

  13. Igor says:

    It's been almost three years since request.

    Is it some kind of weird MS strategy?

    Like "associate by default is soooo 2010, we discourage it now"

  14. General says:

    Is there any update on this issue? We're also having same problem on my team as we check-in from Pending Changes… and then we have to incur the wrath of the irate Scrum Master when the TFS burn down is messed up.

  15. Alex says:

    is there an update for this? Millions of development teams are irritated daily by this.

  16. Eric Mamet says:

    Why is it such a big problem to solve this basic issue???

    Come on Microsoft… wakey! wakey!…

  17. Chris Marisic says:

    worked for me in VS2013. also this tool might be well liked by people here allows you to "Diff all files" from the pending changes window instead of right click compare right click compare

Skip to main content