Nick SchonningNick Schonning

My feedback

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

      Nick SchonningNick Schonning supported this idea  · 
    • 12 votes
      Vote
      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)
        You have left! (?) (thinking…)
        1 comment  ·  Visual Studio IDE » Test Tools  ·  Flag idea as inappropriate…  ·  Admin →
      • 110 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

          Nick SchonningNick Schonning supported this idea  · 
        • 1,009 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 have a lot of investment taking place on our code review platform that will enable iterative code reviews, and we will initially bring that functionality to Git (via pull requests). Improving iterative code reviews for TFVC is still on our backlog, but it is not in our 6 month plan, so we are resetting the status.

            Matt Mitrik

            Nick SchonningNick Schonning supported this idea  · 
          • 40 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  ·  Visual Studio Team Services » Test  ·  Flag idea as inappropriate…  ·  Admin →
              Nick SchonningNick Schonning supported this idea  · 
            • 702 votes
              Vote
              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)
                You have left! (?) (thinking…)
                under review  ·  23 comments  ·  Visual Studio IDE » Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
                Nick SchonningNick Schonning supported this idea  · 
              • 2,177 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

                  Since December we have come a long way. We have added states customization, gave you the ability to customize your portfolio backlogs.

                  We are close to deliver the customization of rules to you and allow you to share fields across multiple processes. After that we want to allow you to clone processes and share a process across accounts. Also we plan to give you a full set of REST APIs to automate picklists. You should see these improvements coming alive in VSTS in the next 2 to 4 months.

                  Once that is completed we want to extend the feature to “move team projects between processes” today it is limited. You can only move a project from Inherited to its parent and vice versa. We want to give you the ability to move a team project from any process to any other process which enables a conversion from Agile to Scrum,…

                  Nick SchonningNick Schonning supported this idea  · 
                • 667 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

                    15 comments  ·  Visual Studio Team Services » CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →

                    We are planning to have a private preview of the VSTS Symbol service when the Visual Studio 2017 version 15.3 release. This will allow integrated authentication from Visual Studio to the VSTS Symbol Server.

                    Dandan He
                    Program Manager

                    Nick SchonningNick Schonning supported this idea  · 
                  • 1,698 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…

                      Nick SchonningNick Schonning supported this idea  · 
                    • 521 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

                        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

                        Nick SchonningNick Schonning supported this idea  · 
                      • 47 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

                          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

                          Nick SchonningNick Schonning supported this idea  · 

                        Feedback and Knowledge Base