Azure DevOps (formerly Visual Studio Team Services)

Announcement: Last fall, we migrated this forum to Developer Community to provide you one convenient and responsive system for all feedback. As the final step in the migration, this forum will be closed off completely on June 1st, 2019. We encourage you to visit Azure DevOps Developer Community where you can now suggest new ideas, browse and vote on existing ideas, and engage with Azure DevOps teams

We’d like your suggestions and ideas to help us continuously improve future releases of Azure DevOps and Team Foundation Server (TFS), so we’ve partnered with UserVoice, a third-party service, to collect your feedback. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.

This site is for feature suggestions; if you need to file a bug, you can visit our Developer Community website to get started.

Note: your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy and license terms.

We look forward to hearing from you!
- The VSTS Team

How can we improve Azure DevOps?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Folder structures for release definition

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365787/folder-structures-for-release-definition.html
    Currently, there is option to organize build definition using folder structure but the same is not available for release definition. We have large number of release definitions tied to individual customers but the list is growing. Due to lack of folders, we have to resort to naming convention to make it easier to identify the individual release definition. It would be really helpful to be able to organize release definitions within folder dedicated to each customer or geographical region.

    431 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    70 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  2. Change release variables' value when deploy a release

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365596/change-release-variables-value-when-deploy-a-relea.html
    In Build definition for VSTS, variables are allowed to change their values at queue time. Could this feature be available in release: when deploy a release the variables' value could be changed?

    222 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    34 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  3. Clone Variable Groups

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365724/clone-variable-groups-1.html
    Being able to clone an existing Variable Group in the VSTS Build & Release Library.

    184 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    26 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  4. Library of Variable and Task groups shared between all projects

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365752/library-of-variable-and-task-groups-shared-between.html
    We need a library in VSTS to manage and share Variables and Tasks Groups between projects, with one definition of a Variable or a Task Group, and not import/export of a Variable or a Task Group which can become different in each project.

    Lot of projects uses common variables and task. And we need to create only on copy of a Variable or Task group to prevent their duplication with importations, and without to go out of VSTS.

    Thanks.

    177 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    27 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow Task Group parameters to be optional

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365727/allow-task-group-parameters-to-be-optional.html
    I would like to have Task Group parameters to be optional, like having a checkmark in the UI. Currently there's only a default value field which can be empty in the Task Group itself but when I use the Task Group it must have a value.

    As a workaround I exported the task and updated the input section in the json file from required":true to required":false.

    This is not only not user friendly but when imported again it is a copy of the…

    139 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  6. Ability to run tasks in parallel

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365659/ability-to-run-tasks-in-parallel.html
    I have seen the multi-phase parallelism, but I don't see that it solves this issue.

    There are often times when you want to run two or more tasks in parallel and then move on when all are complete.

    Here's my example:

    Step 1: Download Artifacts (takes 15 mins)
    Step 2: Start VM (takes 10 mins)

    I would like to run these two tasks in parallel, it would then take 15 mins total rather than 25.

    131 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  7. InRelease Reports

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365436/inrelease-reports.html
    I want to have nice SSRS and SharePoint Dashboard reports showing the release and deployment process from TFS to In Release and through lab environments.

    129 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    15 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →

    This is a great idea! I want to let you know that we have included your suggestion in our next 6-month plan.
    We will check back as soon as possible with any updates to this request.
    In the meantime, please share specific reports that you may want to have available out of the box with us.
    Shashank Bansal
    Program Manager

  8. Trigger Rollback activity when a Release is Rejected (somehow) by the user/approver

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365461/trigger-rollback-activity-when-a-release-is-reject.html
    Nowadays, the Rollback activity in the Release Template is triggered only if one of the previous activities fail (returning a non-0 status code).

    It would be great to be able to trigger a Rollback activity if the release is Rejected by some of the Approvers.

    By now, when it happens, we need to trigger a new Release manually to rollback the application to the previous version. It takes a hard work because we need to find the latest valid (and released) build, etc.

    119 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  9. Task Group custom conditions at group and task level

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365689/task-group-custom-conditions-at-group-and-task-lev.html
    Enable the task Control Options custom conditions for the Task Group Task to skip the Task Group, and also the at the individual tasks wihtin the group.

    When you create a Task Group for a bunch of tasks that had custom conditions, these seem to be removed as the UI no longer shows the custom conditions options.

    114 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  10. Be able to copy a task to other environments

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365597/be-able-to-copy-a-task-to-other-environments.html
    When you already have a number of environments setup you may need to add a new task. Once you have created it in one environment you must then manually recreate it the others.

    It would be useful if there was an option to copy a task to some or all other environments.

    67 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  11. Service Endpoints should be global across all projects within a collection

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365669/service-endpoints-should-be-global-across-all-proj.html
    When entering service Endpoints for Azure in Team Foundation Server they should be globally visible across all projects within a collection. As it stands you have to enter these in for every project

    55 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  12. VSTS: add services on project collection level

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365526/vsts-add-services-on-project-collection-level.html
    Make it possible in VSTS to add Services (a.k.a. service endpoints) on the project collection instead of on individual projects only.

    When you use the same service (e.g. an on-premise Octopus Deploy Server) in multiple VSTS projects you need to add a service endpoint to each project.
    Managing this becomes a burden when you have lots of projects in VSTS

    53 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  13. Deployment Groups allow Machine- and Group-specific variables

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365665/deployment-groups-allow-machine-and-group-specific.html
    Allow for variables or "Capabilities" to be set at the machine and deployment group levels for use in releases.

    51 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  14. Show WI from multiple artifacts under workitem tab in Release Management

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365779/show-wi-from-multiple-artifacts-under-workitem-tab.html
    Our release consists of multiple artifacts which located in different repos, each artifact has its own build and associated WI . Now WorkItem tab shows WI linked to a primary artifact.

    it would be good to see what was changed in the other artifacts

    44 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  15. Scoping for variable groups

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365749/scoping-for-variable-groups.html
    Allow linking multiple variable groups with same variable names and specify scope (environment) for each group. Currently variable groups are not useful as cannot scope them to environments inside the release.

    44 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow deployment logs to be attached to emails

    When you have a deployment fail in Release Management, there should be an option to have the full tool log attached to the emails that are sent out to the Deployment Owner group.

    For example: If publishing a DACPAC fails, the only information you're given is that SQLCOMMAND.EXE failed and returned an error code. This doesn't give the developers enough information to troubleshoot the issue. If the log file was attached to the email, they'd be able to see the root cause of the deployment failure and take corrective action without having to load up the RM client.

    40 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →

    We are changing the way we maintain User Voice feedbacks for Release Management.
    So far we have been marking feedback items as Archived if we are not going to address them in near future. We understand this could have caused some confusion.
    From now on, we’ll be discontinuing this practice and marking something Archived only if we want to close the feedback item for any further input.
    Accordingly, we are resetting the status for this item and would be updating the status for the same based on our FY17 plans.
    Thanks
    [Shashank Bansal – MSFT PM]

  17. Build vnext and release management vnext task : security

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365546/build-vnext-and-release-management-vnext-task-secu.html
    It should be possible to add security on build/release task to make them available or not , usable or not.

    It should be possible not only to add task but to remove task from the list of available task

    38 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →

    We are changing the way we maintain User Voice feedbacks for Release Management.
    So far we have been marking feedback items as Archived if we are not going to address them in near future. We understand this could have caused some confusion.
    From now on, we’ll be discontinuing this practice and marking something Archived only if we want to close the feedback item for any further input.
    Accordingly, we are resetting the status for this item and would be updating the status for the same based on our FY17 plans.
    Thanks
    [Shashank Bansal – MSFT PM]

  18. Sort Variables in Variable group by Name

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365684/sort-variables-in-variable-group-by-name.html
    Variables are not yet sortable by name. So if I have variables:

    Prod.Servers
    QA.Servers
    Prod.ServiceAccount
    QA.ServiceAccount
    Prod.Password
    QA.Password

    I'd like to be able to quickly re-sort to enable an improved viewing experience - or even better be able to arrange the order and that persists.

    Prod.Password
    Prod.Servers
    Prod.ServiceAccount
    QA.Password
    QA.Servers
    QA.ServiceAccount

    Also a description column would be handy to provide a comment about the variable.

    36 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  19. Release Management include all work items in release -api (json)

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365995/release-management-include-all-work-items-in-relea.html
    We are using release management for deploying our daily release to our test env´s. To manage workItems related to the release we are using a small web service.
    The json the service hook is getting from vsts only includes the first 10 workItems of the release even if there are 20 in it.
    This effect also appears when you add a notification if a release is deployed you get a mail but only 10 workItems are listed.

    Please include all related workItems in…

    32 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  20. Release activity in work item history

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365584/release-activity-in-work-item-history.html
    Currently, associated work items are listed in the release. But, from within the work item, there isn't a link or a history entry to tie it to the release.

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

    We’ll send you updates on this idea

    2 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 26 27

Azure DevOps (formerly Visual Studio Team Services)

Feedback and Knowledge Base