Matthew Mitrik

My feedback

  1. 25 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Matthew Mitrik commented  · 

    Thanks for the feedback! Adding full support for the explicit staging model is on our backlog. We've envisioned it as being an optional setting, very similar to what's described above. Having this item is good for us to track the community interest.

    Matt
    Program Manager | Version Control

  2. 14 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Matthew Mitrik commented  · 

    To be clear, I think this ask is to be able to compare the contents of the changesets, not the contents of the tree at the point in time the changeset was created - is that correct? I would love to better understand the need behind this scenario.

    Matt
    Program Manager | TFS Version Control

  3. 38 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Matthew Mitrik commented  · 

    So this would be sort of a "annotate this item at a given point in time", right?

    We have talked about adding a feature that would allow you to "drill in" past the latest version to see who made changes in the past. I can imagine sort of a hybrid history/annotate/diff view that would allow users to easily pivot on the changeset, line, or token to see how changes occurred over time. For example, I could see wanting to view the annotated file as it looked prior to a merge or a refactoring effort.

    Matt
    Program Manager | TFS Version Control

  4. 38 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Matthew Mitrik commented  · 

    In the past we've talked about having an "Activity Feed" that would allow users to subscribe to the various projects and teams they're interested in, and then in VS there would be an experience for viewing this feed. It seems like this idea is very similar to the feed concept.

    Matt
    Program Manager | TFS Version Control

  5. 183 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Matthew Mitrik commented  · 

    We sort of have a workaround for this today - you can go to the command line and view the non-recursive history for a folder to see the history across branches. However, this only shows the history of the folder itself, not the contents of that folder.

    We did talk about this scenario when building the history across branches, but the concept of recursive history across branches proved to be overwhelming. Furthermore, the query to gather this data proved to be very expensive.

    Matt
    Program Manager | TFS Version Control

  6. 201 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    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 Hofman

    Matthew Mitrik commented  · 

    Agreed this would be very useful. We're hoping to get this one into TFS11. I'll update here if we are able to get it in.

    Matt
    Program Manager | TFS Version Control

  7. 38 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    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 Hofman

    Matthew Mitrik commented  · 

    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

  8. 11 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Matthew Mitrik commented  · 

    Improving (rather, adding) policy distribution is a feature we're tracking on our backlog for a future release, as the current framework isn't ideal for custom policies.

    Matt
    Program Manager | TFS Version Control

  9. 18 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Matthew Mitrik commented  · 

    We've heard from other teams in the past a desire to support code module/component revisioning, and we're tracking this on our backlog. It won't be in TFS11, but we'll consider it in our planning in the future.

    Matt
    Program Manager | TFS Version Control

  10. 68 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    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 Hofman

    Matthew Mitrik commented  · 

    By your last comment, I'm assuming you know about the command line power tool to work around this issue - tfpt unshelve /migrate. There are some comments on the usage of this on MSDN: http://msdn.microsoft.com/en-us/library/s6bx4df3.aspx

    Fully supporting this in the product (and in the UI) is on our backlog for a future release.

    Matt
    Program Manager | TFS Version Control

  11. 26 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Matthew Mitrik commented  · 

    I'm assuming that you're encountering this because you have to explicitly check out files before you can begin working on them, and it is easier to just checkout a large folder all at once than checking out individual files - is that correct?

    One of the biggest improvements we've made for vNext is to include support for a new model of working with files that does not require explicit checkouts from the server. You can just edit files locally and the changes will automatically be detected. Check out more here: http://blogs.msdn.com/b/bharry/archive/2011/08/02/version-control-model-enhancements-in-tfs-11.aspx

    Matt
    Program Manager | TFS Version Control

  12. 45 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    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 Hofman

    Matthew Mitrik commented  · 

    In vNext we have added support for initiating a baseless merge in the Merge Wizard. In 2010, you can actually perform the merge between branches with an existing relationship if you first perform a baseless merge from the command line.

    Matt
    Program Manager | TFS Version Control

Feedback and Knowledge Base