Manish JainManish Jain

My feedback

  1. 17 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

      5 comments  ·  Team Services » Work Item Tracking  ·  Flag idea as inappropriate…  ·  Admin →
      Manish JainManish Jain supported this idea  · 
    • 1,656 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

        65 comments  ·  Team Services » Administration & Licensing  ·  Flag idea as inappropriate…  ·  Admin →

        Enabling the ability to move projects between collections is a feature that we’re committed to delivering. Since this feature is so highly requested, I’d like to provide some additional details behind why this has been pushed out.

        Simply put the issue is the cost to complete this feature. One way to think of it is that it’s XXXL in T-shirt sizing. A Team Project Collection (TPC) is a pretty rigid bounding container. It‘s the scope at which a number of “global” things exist.

        One such example is change set numbers. They start at 1 and count up in each TPC. That means projects in a TPC can’t have overlapping change set numbers. It also means that if you wanted to move TFVC projects between TPCs, you have to renumber all the change sets. That’s exacerbated by a requirement that change set numbers be time ordered. That means…

        Manish JainManish Jain commented  · 

        We also have need for this feature. We are creating new projects in 2010. Later we would like to migrate 2008 team projects into existing collection. Just like tfs integration platform, its okay to renumber work item, change set numbers etc. I understand this is a complex feature to implement but this should be part of TFS suite and less complex than integration platform.

      • 974 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

          33 comments  ·  Team Services » Work Item Tracking  ·  Flag idea as inappropriate…  ·  Admin →

          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

          Manish JainManish Jain supported this idea  · 
          Manish JainManish Jain commented  · 

          Thank you for posting this idea. TFS/ALM team - considering # of people/team suffering from lack of this feature, it should be considered for vNext. This is something basic and should be priority over any new features.

        • 44 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

            8 comments  ·  Team Services » Work Item Tracking  ·  Flag idea as inappropriate…  ·  Admin →

            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

            Manish JainManish Jain commented  · 
          • 192 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

              33 comments  ·  Team Services » Work Item Tracking  ·  Flag idea as inappropriate…  ·  Admin →
              Manish JainManish Jain commented  · 
            • 44 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

                2 comments  ·  Team Services » Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →

                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

              Feedback and Knowledge Base