Visual Studio ALM Team

My feedback

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

    We’ll send you updates on this idea

    Visual Studio ALM Team commented  · 

    Tarun,

    Thanks for your idea. Making a project collection offline is pretty easy, because all the information is stored in one database. It is thus an operation on the database. Make a team project offline or disabled however involves lot of effort to make that happen.
    There is also a work around where you create a security group for your contributors and your admins. When you want to disable a team project, you can just move these from the contributors/admin group to the readers group (with add and remove).

    Based on these arguments (effort and a workaround) we rather spend our limited resources on other feature requests. Of course this is user voice, and the votes will tell if I am wrong. If there is lot of traction on this idea, I am very willing to revise my point of view.

    Ewald Hofman
    Program Manager TFS

  2. 14 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

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

    We’ll send you updates on this idea

    Visual Studio ALM Team commented  · 

    Thanks for the feedback. We have heard this request more in the past and it is already on our backlog. I am unable to indicate if and when we will implement the customization of the subject. We use the User Voice site as one of the areas helping us to stack rank features against each other. Ideas on User Voice with lots of passion are investigated very seriously.

    Ewald Hofman - TFS Program Manager

  4. 101 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

    Visual Studio ALM Team commented  · 

    Great feedback. This has long been a request by our customers. Thanks for submitting.

    Gregg Boer - MSFT / TFS Product Group

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

    We’ll send you updates on this idea

    Visual Studio ALM Team commented  · 

    Thanks for submitting. We have this one on our backlog. It does keep getting pushed down, however, so any information on why this is important would be helpful.

    Gregg Boer - MSFT / TFS Product Group

  6. 39 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Visual Studio ALM Team commented  · 

    Great idea. This one is on our backlog!

    Gregg Boer - MSFT / TFS Product Group

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

    We’ll send you updates on this idea

    Visual Studio ALM Team commented  · 

    This is a great idea. Thanks for submitting.
    Gregg Boer - MSFT/TFS Product group.

    Visual Studio ALM Team shared this idea  · 
  8. 355 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Visual Studio ALM Team commented  · 

    Thanks for submitting the idea. You are correct, this is not tracked well in TFS today.

    Gregg Boer - MSFT / TFS Product Group

  9. 59 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

    Visual Studio ALM Team commented  · 

    Glad you found the blog post on this. Being able to add rules on these fields (Area and Iteration) is on our backlog. We are adding functionality in the vNext release which will default these fields based on what team you are a member of. Each team can define default values for these fields, and by working in the context of a team, these values are then defaulted when creating new work items. We hope this addresses a lot of the need for rules on these fields.

    Gregg Boer - MSFT / TFS Product Group

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

    We’ll send you updates on this idea

    Visual Studio ALM Team commented  · 

    This is an interesting suggestion. I would like to know more about WHY you are asking for this. We have decided, deliberately to NOT add work item security to iteration security policies, because we believe that the existing one (based on Area Path) is sufficent, and having a second policy to check and enforce would both be confusing to the end-user, as well as a hit on performance. Any additional thoughts of yours are appreciated.

    Gregg Boer - MSFT / TFS Product Group

    Visual Studio ALM Team shared this idea  · 
  11. 19 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Visual Studio ALM Team commented  · 

    We have added start/end dates on iterations in vNext. That information is reportable.
    We have also given you the ability to define a set of team members working on a particular iteration. However, that information is only available for sprint planning, to check compacity and produce burn-down charts. That information is not reportable.

    Gregg Boer - MSFT / TFS Product Group

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

    We’ll send you updates on this idea

    Visual Studio ALM Team commented  · 

    Thanks for the feedback. We want to add this in the future, but it won't be available in the near term.

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

    We’ll send you updates on this idea

    Unfortunately we have had to make the decision to not bring the new Inheritance model to TFS on-prem with the next major release. It was a tough decision that we didn’t take lightly. The scope cuts that we had to make in order to deliver it to on-prem were just too painful, and would not give the User Experience we would be proud of.

    We are still planning to bring it to our on-prem customers in a future release of TFS.

    Sorry for not having a better answer.

    Ewald Hofman
    VSTS/TFS Program Manager

    Visual Studio ALM Team commented  · 

    Thanks guys. We hear this one a lot and it's definitely something we're considering. That said, we're not planning a full "migration" tool in vNext.

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

    We’ll send you updates on this idea

    We are committed to supporting the ability to move projects between collections, however we’ve been unable to make progress on this feature. Unfortunately, the challenges highlighted in earlier posts are still present.
    I don’t foresee us making progress on this feature within the next 6 months. We will provide an update once we start planning for the second half of 2019.

    Whitney Jenkins
    Azure DevOps Program Manager

    Visual Studio ALM Team commented  · 

    Wow, this is a tough one. The challenge has to do with all kinds of data conflicts that would be encountered when you tried to merge a team project into another collection. As an example, to do it with full fidelity, almost every changeset in the target collection would need to be renumbered, every link to those changesets would need to be updated, every work item in the source project would likely need to be renumbered, etc. Any place you've stored a reference to those items outside of TFS (such as work items in Excel-bound spreadsheets) would need to get updated.

    What is more realistic, and perhaps more valuable overall, is for us to eliminate the limitations imposed by the project collection boundary. Can you tell us which limitations are frustrating you? Is it linking between work items in disparate collections? Branching/merging code between collections? Backup/restore consistency of projects in different collections?

    In the meantime, Martin's proposed solutions are the best thing going. They aren't perfect, but they are better than nothing.

    Visual Studio ALM Team shared this idea  · 

Feedback and Knowledge Base