How can we improve Team Services?

Customize Process Template on Visual Studio Team Services

In Visual Studio Team Services, allow the ability to change the current process template a created project is using as well as the ability to upload your own process templates to create new team projects with.

2,159 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

    Jonathon StevensJonathon Stevens shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    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, which has been a long-standing ask.

    Lastly, we are planning to allow customers who imported their TFS collection into VSTS to migrate from “Hosted XML” to the Inheritance process model.

    Ewald Hofman
    VSTS Program Manager

    242 comments

    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)
      Submitting...
      • Anonymous commented  ·   ·  Flag as inappropriate

        When will we get "Cloning of process templates"?
        We have several team projects which use an inherited processes.
        Now they beginn to differ and we need to split their process template...

      • Thomas MutzlThomas Mutzl commented  ·   ·  Flag as inappropriate

        @Why cloning an inherited process: it should be an export/import, so that an inherited process can be re-used on a different VSTS account. And from my understanding, that's currently not possible, correct?

      • Team Services GroupAdminTeam Services Group (Product group, Microsoft Visual Studio) commented  ·   ·  Flag as inappropriate

        @Dave, the custom states should just show up in VS Community. User Voice is used for feature suggestions, and is not tracked for issues or problems. Please use the <a href="https://developercommunity.visualstudio.com/spaces/21/index.html">Developer Community</a> to report an issue.

        Why are you asking your stakeholders by the way to open work items in VS Community? Why don't you let them use the web work item form?

        Ewald Hofman

      • Dave McKerralDave McKerral commented  ·   ·  Flag as inappropriate

        Are there limitations on custom states when working with Visual Studio Community? We've added some and they're displaying fine on VSO and VS Enterprise but don't display on community which our stakeholders are using, the custom fields on the WIT do, but not the custom states.

      • Justin JacksonJustin Jackson commented  ·   ·  Flag as inappropriate

        Is there the ability to still setup a VSTS account with HostedXML by default? The options to customize based purely on the Inherited process is fairly limited. I want to be able to import a customized process in VSTS, but I don't see that option in any of my accounts.

      • Peter BoevinkPeter Boevink commented  ·   ·  Flag as inappropriate

        Will it be possible to clone an existing inherited process template? I don't see any support for exporting/importing inherited processes.
        Currently I have to inherit the original process again and re-apply all customizations (which have not been tracked....)

      • fredfred commented  ·   ·  Flag as inappropriate

        Is it possible to customize the Reason Codes for Closed items? It only currently has Deferred, Rejected or Duplicate. This are not the only reason a Bug is closed. What about the value of Resolved or Completed or just Closed.

      • Chris KimChris Kim commented  ·   ·  Flag as inappropriate

        I don't see a timeline for the uploading process template feature, just the customizations for the work items. Do you guys have plan to add the upload feature at this point? Small shops might be able to just tweak existing templates but large scale projects will need to customize and upload that to clients.

      • Ed BlankenshipEd Blankenship commented  ·   ·  Flag as inappropriate

        Yes, we sure are. It's the first item on the roadmap (with a great linked description) but many of the releases over the last few months have lots of process template customization options available in Visual Studio Team Services now. The features timeline is available here: https://www.visualstudio.com/en-us/articles/news/features-timeline

        Let us know if you have any questions after taking a look at what's available now in Team Services!

      • Anonymous commented  ·   ·  Flag as inappropriate

        Currently the only selection list type of custom field is a numeric list. I would like an option to have a User field the could be used to assign different types of users such as developer, qa, etc. These custom fields would provide a selection list of all users and preferably you could specify the group that would be displayed in the list.

      • Visual Studio TeamAdminVisual Studio Team (Product Team, Microsoft Visual Studio) commented  ·   ·  Flag as inappropriate

        @Shawn, it is true that we are asking that our customers try and embrace the new process customization features from here on out. The private preview for process customization is available but is subject to review to make sure the process template and the project are a good fit. If you are on TFS on-prem today and need to move to VSTS and you are blocked because of process customization, then you may be a good candidate. Please email us at vsocustpt@microsoft.com and someone will contact you to review your process template.

        Dan Hellem

      • ShawnShawn commented  ·   ·  Flag as inappropriate

        We were told by Microsoft VSOCustPT that you are no longer accepting requests for preview access to upload process via VSTS. Is this true? If so, then your answer below is inaccurate, because you are not making this feature available to us.

      ← Previous 1 3 4 5 12 13

      Feedback and Knowledge Base