Douw Loots

My feedback

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

      We understand the importance of this scenario, but during the investigation we determined that future additions to the process customization will have better support to implement a real blocked scenario. We are going to hold off of this one for a little bit longer and wait until that work is finished. That does not mean that we forgot about this at all!

      As a work around you can add a blocked tag to your work items and use the tag coloring on the board to show these tags in red.

      Ewald Hofman
      @ewald_hofman

      Douw Loots supported this idea  · 
    • 285 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

        We are working toward a self-service solution. In the meantime, you can change the region of your Visual Studio Team Services account by contacting customer support via the basic or premium support links on this page: https://www.visualstudio.com/team-services/support/. A member of our support team will reach back out to the owner of the account to confirm the request and schedule the move.

        Update: Over the past months, many customers have used this process to move their accounts from one region to another. We are continuing to work toward a self-service solution for this process, but do not have a firm schedule to share as of yet.

        Thanks,
        Aaron Hallberg

        Douw Loots supported this idea  · 
      • 2 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

          Douw Loots shared this idea  · 
        • 992 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

            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

            Douw Loots supported this idea  · 
          • 1,213 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

              Douw Loots supported this idea  · 
            • 1,761 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

                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…

                Douw Loots supported this idea  · 

              Feedback and Knowledge Base