How can we improve Visual Studio Team Services (VSTS)?

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.

396 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)

    We’ll send you updates on this idea

    suresh2 shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    24 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Gregg B. Jensen commented  ·   ·  Flag as inappropriate

        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  ·   ·  Flag as inappropriate

        There is already a registry key available to set the default. However it is not used in VS 2012
        [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\TeamFoundation\SourceControl\Behavior]
        "ResolveAsDefaultCheckinAction"="False"

      • Stephen John Anderson commented  ·   ·  Flag as inappropriate

        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.

      ← Previous 1 2 Next →

      Feedback and Knowledge Base