I suggest you ...

← Visual Studio

Make work item columns customizable in check-in dialog

When checking-in our policy is that a work item has to be linked. Our work items have a custom field with an ID that differs from the TFS ID. The columns in the check-in dialog are not customizable which makes it very ennoying to find the correct work item.

56 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Forgot password?
    Create a password
    I agree to the terms of service
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    Ruben DrögeRuben Dröge shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    4 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Forgot password?
      Create a password
      I agree to the terms of service
      Signed in as (Sign out)
      Close
      Close
      Submitting...
      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        This is terrific! Sounds like a good use of data governance to establish a policy to support our data and our workflow.

      • Ken SparksKen Sparks commented  ·   ·  Flag as inappropriate

        I agree with Connie. This would be a valuable additional feature allowing the use of a customized value referenceable in another system.

      • ConnieConnie commented  ·   ·  Flag as inappropriate

        Having this would really smooth adoption of TFS on my team. Our project management is done by a separate group who uses a different tool and we do not have the option to change that, but we want to tie our checkins to our custom field that represents the project task identifier. We currently have to look up that custom value in a separate team query then jot down the TFS workitem number to quickly find the right workitem to check in against. Simply adding the custom field as a column to the check-in dialog would eliminate that extra check-in step for us.

      • Matthew MitrikMatthew Mitrik commented  ·   ·  Flag as inappropriate

        I've heard this one in the past, and using the old work items associate experience in 2010, I think it made a lot of sense. In TFS11, we've changed the model a bit, and I wonder if it makes this experience any better. I'd love to hear some feedback on the new experience once we have a beta available.

        Matt
        Program Manager | TFS Version Control

      Visual Studio: Team Foundation Server

      Feedback and Knowledge Base

      (thinking…)