alm-devops-features.md

title	titleSuffix	description	ms.technology	ms.article	ms.assetid	ms.author	author	ms.topic	ms.date	monikerRange
Feature overview for Azure DevOps	Azure DevOps	Comprehensive index to all features for Azure DevOps	devops-new-user	quickstart	330E6DA5-3DC9-432D-B3CA-BF999F151733	chcomley	chcomley	reference	05/28/2019	<= azure-devops

What are the features in Azure DevOps?

[!INCLUDE version-lt-eq-azure-devops]

Learn about all the features available to help you plan and track your projects and code, build, test, and release your software applications in Azure DevOps.

If you're new to Azure DevOps, see our overview articles that are designed to give beginners an understanding of the server-client structure and tools supported. For a description of the core services supported through the web portal, see Essential services.

Note

Some features are platform-dependent, based on the following two platforms:

• Azure DevOps Services - cloud service
• Azure DevOps Server - on-premises

Access and supported clients

Browsers Connect to the web portal from the latest versions of these supported browsers: - Chrome - Microsoft Edge - Firefox - Internet Explorer - Safari (Mac) Integrated Development Environments (IDE) Track work and integrate with your code, build, and test environments from the following clients: - Eclipse (Team Explorer Everywhere) - Visual Studio - Android Studio - IntelliJ - Visual Studio Code To learn how to connect, see Connect to a project. Office integration clients Use features supported by these familiar clients to manage your project and illustrate your requirements. - Excel

Manage users and groups Add members to your project adds them to the Contributor group. When managing a large group of users, use built-in groups to manage users and their permissions. Add team members To share and contribute to your project, add users to Azure DevOps Services or your Azure DevOps Server. Azure Active Directory (Azure AD) (Azure DevOps Services) Control who can access your team's critical resources and key business assets by managing access with Azure Active Directory groups.

Access levels All users that you add to your Azure DevOps organization or to your Azure DevOps Server project have access to Basic features by default, except Stakeholders who have access to a limited set of features, or those added to the Advanced access level in Azure DevOps Server. - Manage users (Azure DevOps Services) - Change access levels (Azure DevOps Server) Permissions Control access to specific features by setting permissions for a user or group. Area and iteration paths - Build & Release - Git - TFVC - Dashboards - Queries - Manage teams and configure team tools - Test - Work item tags

Agile tools to plan and track work

Backlogs

Create your backlog Plan your project by adding a work item for each user story or requirement you plan to develop. Organize your backlog Group items into a hierarchical list using portfolio backlogs and quickly reorder and re-parent items to effectively manage your deliverables. Forecast Use the forecast tool to estimate work to be completed in future sprints.

Move work item to a different project (Azure DevOps Services) Choose Change project, Actions menu in a work item form to move the work item to a different project. Full screen mode Choose or to enter or exit full screen mode. Backlog and board settings Choose to configure team backlogs and boards, including show bugs on backlogs and boards and set team backlog levels. View portfolio backlog hierarchy Use Parents Show/Hide to drill down into the backlog hierarchy. Multi-team backlog ownership Easily view and track items owned by other teams and quickly reorder and re-parent items to effectively manage your backlog.

Change work item type (Azure DevOps Services) If you added a task instead of a bug and want to change the work item type to bug, you can. Choose Change type Actions menu in a work item form to change the work item type. Filter your backlog Use Show/Hide in progress to only show or hide items which have moved from the new or proposed state to active or in progress state. Additionally, you can list a subset of items based on keywords keywords or tags. Request feedback Request feedback on working software and easily track responses that capture interaction with video, verbal, or type-written comments. Feedback client Provide the free Microsoft feedback client to capture their responses to your feedback requests.

Bug, task, and issue tracking

Track issues and other types of work Different types of work items track different types of work - such as bugs, test cases, risks, issues, and more. Bulk modify Quickly change one or more fields in several work items using bulk modify in the web portal or bulk modify using Excel. Copy or clone a work item Copy an existing work item or bulk copy several using Excel. Follow a work item Choose / Follow/Following to quickly start or stop tracking changes made to a work item. Rich text comments Describe and comment on work using formatted text, hyperlinks, and inline images. Choose or to expand or contract the viewing area. Clear HTML formatting Use or CTRL+Spacebar to remove formatting from highlighted text. Attachments To support collaboration of work in progress, add emails, documents, images, log files, or other file types to work items.

Estimates and time tracking Track estimated, completed, and remaining work for tasks and other work items. Several reports and dashboards provide charts that display data based on team capacity and remaining work. New work item experience The new work item experience provides access to a more modern form, additional features, and the ability to add fields and apply other customizations to the work item type. Manage bugs Capture and triage bugs using different kinds of tools. Choose how you want to track bugs Each team can choose to manage bugs on their backlog or along with tasks. Share plans and information Share information using work items and generate summary lists with links to backlogs or queries. Remove or delete a work item Remove work items from the backlog by changing their State to Removed. Or, move them to the recycle bin or permanently delete them. Tags Add tags to work items to filter backlogs and queries. Bulk update work items or use work item templates to add or remove tags. Work item templates Quickly add new work items based on templates with pre-populate values for your team's commonly used fields. History & auditing Review and query work item change history to learn of past decisions and support future ones.

Discussion Add or review comments added to a work item. Start by choosing discussion. Integrate Git development with work tracking Drive Git development and stay in sync as a team to complete backlog items and tasks using the Git Development section. Add branches, create pull requests, and view all development done to support the specific work item. Verify a bug, rerun test case Choose Verify from the bug work item form context menu to launch the relevant test case in the web runner. For more information, see Run tests for web apps. Link work items Track related work, dependencies, and changes made over time by linking work items. Add or modify a field Add a custom field (Azure DevOps Services | Azure DevOps Server to support tracking additional data requirements or modify an existing field to apply optional rules. Restrict access Limit who can create or modify work items or a work item field based on area path, work item type, or based on your specific conditions. Field index Find descriptions and usage information for each field from the work item field index.

::: moniker range="azure-devops"

Customize (Azure DevOps Services)

Create an inherited process The first step in customizing a project is to create an inherited process. You can only customize inherited processes. New work item experience The new work item experience provides access to a more modern form, additional features, and the ability to add fields and apply other customizations to the work item type. Customize a process Customizations you make to an inherited process automatically update all team projects that reference that process. You can customize your project as follows: Add and modify fields Modify the web form layout Modify the workflow states Add a custom work item type Add a custom control Change the process used by a project To apply customizations to one or more team projects, you change the process they reference to a customized inherited process. Enable/disable a process To make sure no one creates a project from a process that you don't want used, you can disable it.

Add or modify a field Add a custom field to support tracking additional data requirements or modify an existing field to apply optional rules. Remove a field from a form You can remove a custom field and select inherited fields from a work item form. You can also relabel the fields that appear on the form. Area path pick lists Change the pick list of area paths to support grouping work items by team, product, or feature area. Sprint/iteration pick lists Change the pick list of iteration paths to support grouping work into sprints, milestones, or other event-specific or time-related period. Activate sprints for each team.

Review fields You can review the list of fields defined for a process, their data type, and the WITs which reference them. For descriptions and usage of each field, see Work item field index. Delete a field from the collection You can delete a custom field if you find it's no longer required. Customize the web form For each work item type, you can add custom pages to group additional custom fields and you can organize your forms by placing logically related groups and HTML fields on separate pages within a form. Add a custom work item type You can add and modify a custom work item type. Customize the workflow For each work item type, you can add custom workflow states to support your business tracking needs. Delete a process Delete those inherited processes that you no longer want used. Choose Delete. Set process permissions To customize a process, add custom fields, or change the layout of a work item form, you must be a member of the Project Collection Administrators group or be granted explicit permissions to edit a specific process.

::: moniker-end

::: moniker range="tfs-2018"

Customize (Azure DevOps Server)

Add or modify a field Add or modify a field to support work tracking and reporting by editing the WIT definition. Add rules to a field Apply various rules to custom fields to qualify the value it can have, to copy a value, to specify a default, to restrict who can modify it, to enforce pattern matching, or to enforce conditional values. Remove a field Stop tracking a field by removing the field from the work item form of select work item types.

Area path pick lists Change the pick list of area paths to support grouping work items by team, product, or feature area. Sprint/iteration pick lists Change the pick list of iteration paths to support grouping work into sprints, milestones, or other event-specific or time-related period. Custom pick lists Define or modify pick list values by editing the work item type definition.

Modify the workflow Design your custom workflow by adding states, transitions, reasons, and optional actions. Change the work item form Change the layout of your work item form by adding fields, custom controls, or tabs. Add a custom work item type Add a custom work item type to track different data requirements.

::: moniker-end

Kanban

Kanban basics Use your Kanban board to visualize and track the flow of work from idea to completion as well as quickly update work item fields Drag-n-drop Drag and drop items on the Kanban board to update status and to reorder and reparent items. Add task checklists Add and mark tasks as done with lightweight tasks checklists. Filter Use key words to filter and find items on the Kanban board.

Set WIP limits Set constraints on the amount of work your team undertakes at each work stage to gain access to sprint backlogs and task boards. Split columns Turn on split columns to track the lag between when items are done in one state and work actually starts in a new state. Map your workflow Customize columns to support your team's workflow and track work from start to finish. Expedite work with swimlanes Use swimlanes to track work at different service-level classes. Definition of done Support your team to be in sync by specifying requirements to fulfill prior to handoff of items to a downstream work stage. Filter by field values or parent work items Choose field filter to filter the board based on assignment, iteration, work item type, or tags. Cumulative Flow Diagram With the CFD, you can monitor the count of work items as they progressively move through various states which you define.

Customize cards Add fields to cards that you can edit directly on your Kanban and task boards. Live updates Enable live updates to automatically refresh your Kanban board when changes are made by others or to the board settings. Add inline tests Add, run, and update tests with inline test on your Kanban board. Add checklists to features and epics Add and mark user stories and other work items as done from your Kanban features or epics boards. Set team's card reorder preference You can preserve the backlog priority when you move a card to a new column by setting your team's Kanban board card reordering setting. Enable/disable card annotations Turn on or off task checklists or inline tests for your Kanban board. Configure inline tests Configure how new inline tests are added to the Kanban board: create a new test plan/test suite or choose an existing test plan.

Scale

Add another team Add and structure teams and organize work to support team autonomy and organizational alignment. Teams can manage their work independently of one another while the organization gains visibility across all teams. Set team defaults Several Agile tools reference the team's default area path, iteration path, and activated sprints to automatically filter the set of work items they display. Understand how defaults are used.

Set up a team hierarchy By configuring your teams and backlogs into an hierarchical structure, program owners can more easily track progress across teams, manage portfolios, and generate rollup data. Autonomy and alignment As your organization grows, your tools can grow to support a culture of team autonomy and organizational alignment. Scale your tools and practices Incrementally adopt practices that scale to create greater rhythm and flow within your organization, engage customers, improve project visibility, and develop a productive workforce.

Portfolio management Manage a portfolio of backlogs and gain insight into each team's progress as well as the progress of all programs. Scaled Agile Framework Structure team projects to support epics, release trains, and multiple backlogs to support the Scaled Agile Framework.

Scrum

Define sprints Schedule and activate your team's sprints to gain access to sprint backlogs and task boards. Select team sprints, set team defaults Several tools reference the team's default and active iteration paths or sprints. For the Agile tools to work best, each team needs to set their team area path(s) and iteration paths to support their work tracking activities. Plan sprints Build your sprint backlog, add tasks, and load balance work across your team as you plan your sprint. Track work on your task board Use your task board during your daily Scrum meetings to view and update progress.

Velocity & forecasting Use velocity charts and forecast tools to estimate work that can be completed in future sprints. Sprint burndown charts Monitor progress and review team patterns from sprint burndown charts.

Manage resources Use capacity planning tools to track individual, team, and activity over and under capacity for a sprint.

Workflow

What is workflow? You use workflow to track the progress of work as it moves from new, active, to complete or closed. Each workflow consists of a set of states, the valid transitions between the states, and the reasons for transitioning the work item to the selected state. Default workflows Each process defines the workflow for each work item type to track progress from newly defined, to in progress, to completed or closed.

Kanban workflow You can fully customize your Kanban board to map the workflow your team uses by adding and renaming columns Customize the workflow For Azure DevOps Services: add custom workflow states to support your business tracking needs. For Azure DevOps Server: Design your custom workflow by adding states, transitions, reasons, and optional actions. States States allow you to track the status of work. For example, a bug moves from Active, Resolved, and Closed to correspond to when it's defined, fixed, and verified as fixed. Transitions Transitions specify the valid progressions and regressions from state to state for a work item type. Reasons Each transition specifies a default reason as well as optional reasons for tracking the change in state.

Update fields during workflow changes (Azure DevOps Server) You can define rules that change a field value whenever you change the state, perform a transition, or select a reason. Apply workflow conditional field rules (Azure DevOps Server) You can define rules that change a field value based on the contents of other fields during workflow changes. Restrict who can make changes during workflow transitions (Azure DevOps Server) Set a condition field rule that applies to a group to restrict who can make changes to a workflow or a field. Event-generated workflow changes or field assignments (Azure DevOps Server) Add an action to a custom workflow definition to automatically transition work items or specify a field value based on an internal Azure DevOps Server event or external event. Visual workflow design tool (Azure DevOps Server) You can change the workflow or view the workflow state diagram by using the Process Editor, a power tool for Visual Studio.

Alerts and notifications

Personal and team notifications or alerts Get notified as changes occur to work items, code reviews, source control files, and builds by setting personal notifications or team notifications. Share queries and sprint plans Email a query or sprint plan. Quick alerts to team members Use the control to send email to team members to bring them into a discussion around work changes, pull requests, or other items. Client feature flag updates Alert flag within the IDE automatically notifies you of the latest client changes.

Follow a work item Choose / to quickly start or stop tracking changes made to a work item. Follow a pull request To track the progress of a single pull request, choose from the menu. Manage work items you follow From the Work>Queries page you can view the list of work items that you're following. Frequent on-line feature updates Check the News for product updates, or read about them by accessing the News link in your web portal.

Code

Code: Git

Get started with Git in Visual Studio To get started working with Git, clone a repository, add code, and create branches in Azure DevOps Services or Visual Studio. Learn how to commit, publish, and conduct a pull request of your changes. Clone repositories To work locally, you clone a repository. Commit changes Enter commit messages and quickly push your local changes to the shared repo. Pull requests Use pull requests to review and merge branch code to a main branch. Sync Quickly sync your local branch with a shared repo.

Get started using Eclipse Work with Git repositories using the Team Explorer Everywhere IDE for Eclipse. Add reviewers to get feedback Use the @mention control to add reviewers to your pull request to get their feedback about your changes. Resolve Git merge conflicts Merge conflicts occur when commits have changes to the same files as other newer commits in the branch history. Learn how to prevent and resolve merge conflicts. Code search Maximize cross-team collaboration and code sharing by finding code across all the projects to which you have access. Narrow down your results and focus in on code by using filters, preview code, view history, compare versions, and more Get notified about pull requests Subscribe to email alerts to get notified about new pull requests, changes, approvals, and rejections. Set branch policies To improve code quality, set branch policies to require code reviews or automatically add reviewers. Automatically build pull requests Set a branch policy to automatically generate a build for a pull request to selected branches. Create Git repositories When you create a project with Git as your version control system, you automatically create a Git repo. You can Create additional Git repos from the admin context. Rename a Git repository Rename Git repos from the admin context.

Integrate Git development with work tracking Drive Git development and stay in sync as a team to complete backlog items and tasks using the Git Development section. Add branches, create pull requests, and view all development performed to support the specific work item. Quickly link work items to pull requests Use the #ID control to link work items to your pull request to support tracking work. Get started using Xcode Work with Git repositories using the Xcode IDE. Git commands Use Git command line tools when you need to perform select manual tasks or to automate work using a script. Bypass a branch policy Grant an Exempt from policy enforcement permission to a user or group. Rebase a branch Before merging a branch into main, you may choose to first rebase your branch onto the latest commit in main. Git permissions Set permissions on a Git project, repository, or branch from the context menu or from the web portal administration page.

Code: TFVC

Get started with TFVC in Visual Studio Develop and share your code. Learn how to configure your workspace, check-in your code, compare file changes, and view file history. Set up local or server workspaces Create a local workspace that maps to the code base of interest. Resolve conflicts Support for Resolve conflicts that arise when several people work concurrently on a file. Compare files and folders Compare server folders and local folders to each other, and view the differences between the contents of each folder.

Track changesets Find information about which branches have received a particular set of changes and when those changes were merged. Request code review Increase overall code quality and reduce the risk of creating bugs by requesting a code review when you check-in code. Review history of a file Get detailed information about what changes have been made to your files. Suspend work Use shelvesets when you need to set aside some or all of your work in progress. Manage branches, isolate risk Use branches and locks to isolate risk introduced by work done by different teams. Merge branches Integrate work completed in different branches during certain phases of your project. Set check-in and check-out policies Enforce practices that lead to better code and more efficient group development by setting check-in/check-out rules.

Code search Find code across all the projects to which you have access. Narrow down your results and focus in on code by using filters, preview code, view history, compare versions, and more Subscribe to alerts when check-ins occur Get notified when someone checks in code to your TFVC project by subscribing to receive email alerts. Version control locks Lock files or folders when you need to prevent them from being checked out or modified. Download files from the server Get the latest files from the server on a regular basis so that the code you develop is compatible with the code developed by others on your team. TFVC permissions Set permissions on select code management tasks from the context menu for TFVC files or folders or the admin context for the project.

::: moniker range="azure-devops"

Azure Artifacts (Azure DevOps Services)

What is Azure Artifacts? Azure Artifacts is the new name for what was previously Package Management. Azure Artifacts helps you manage code sharing by automating common tasks for discovering, consuming, and sharing components. Create feeds Create feeds to share code through packages. Move existing file shares to the cloud Eliminate dependencies on on-premises file shares and hosted instances of NuGet.Server by moving your packages to Azure DevOps Services.

Discover and consume packages Consume packages by connecting to a feed. Publish packages to feeds Publish packages to share code with your team and your organization. Add identities to your feeds Give teams and service identities access to your feeds.

Upstream sources use a single feed to manage packages from different sources. Publish and install packages from your feed and public registries with Upstream Sources. Remove a NuGet package from a feed Unlist or remove a package Delete packages and recover deleted packages from the recycle bin in Azure Artifacts you no longer want users to discover. Secure feeds Control who can contribute to or consume from a feed.

::: moniker-end

Continuous delivery

Build

:::row::: :::column::: Define builds

    Start from a build template and customize your build from there. Build for [Windows](../pipelines/apps/aspnet/build-aspnet-4.md), [iOS](../pipelines/ecosystems/xcode.md), Android, Java (Ant, Maven, or Gradle), or Linux using the same domain-specific languages you use every day on your dev machine. [Build Xamarin apps](../pipelines/ecosystems/xamarin.md) for both iOS and Android and run tests on the Xamarin Test Cloud as part of the build.  

    **Customize build process using scripts**  

    [Use a script](../pipelines/scripts/powershell.md) to add your team's business logic to your build process.  

    **Build agents and agent pools**  

    At least one [agent](../pipelines/agents/agents.md) is required to build your code. As you scale your system with more code, people, and builds, you'll need more build agents organized within [agent pools](../pipelines/agents/pools-queues.md). You can use both on-premises or Microsoft-hosted agent pools.  

    **Gated check-in (TFVC, Azure DevOps Services)**  

    Use [gated check-in](../pipelines/repos/tfvc.md#gated) to protect against breaking changes when checking code into TFVC.  

    **Branch policies (Git)**  

    Improve code quality by [setting branch policies](../repos/git/branch-policies.md) to ensure builds are never broken or getting the right people to review changes.
:::column-end:::
:::column:::
    **Specify your build steps**  

    Add steps to specify what you [want to build](../pipelines/tasks/index.md#build), the [tests to run](../pipelines/tasks/index.md#test), and [all the other steps](../pipelines/tasks/index.md) needed to complete the process.  

    pipelines\tasks\build\media  

    :::image type="icon" source="../pipelines/tasks/build/media/android-build.png":::
      [Build an Android app using Gradle](../pipelines/tasks/build/gradle.md)  

    :::image type="icon" source="../pipelines/tasks/build/media/android-signing.png":::
      [Sign and align Android APK files](../pipelines/tasks/build/android-signing.md)  

    :::image type="icon" source="../pipelines/tasks/build/media/ant.png":::
      [Build with Apache Ant](../pipelines/tasks/build/ant.md)  

    :::image type="icon" source="../pipelines/tasks/build/media/gradle.png":::
      [Build using a Gradle wrapper script](../pipelines/tasks/build/gradle.md)  

    :::image type="icon" source="../pipelines/tasks/build/media/grunt.png":::
      [Grunt: The JavaScript Task Runner](../pipelines/tasks/build/grunt.md)  

    :::image type="icon" source="../pipelines/tasks/build/media/gulp.png":::
      [Gulp: Node.js task-based build system](../pipelines/tasks/build/gulp.md)  

    :::image type="icon" source="../pipelines/tasks/build/media/publish-build-artifacts.png":::
      [Index source code and publish symbols](../pipelines/tasks/build/index-sources-publish-symbols.md)  

    :::image type="icon" source="../pipelines/tasks/build/media/maven.png":::
      [Build with Apache Maven](../pipelines/tasks/build/maven.md)  

    :::image type="icon" source="../pipelines/tasks/build/media/msbuild.png":::
      [Build with MSbuild](../pipelines/tasks/build/msbuild.md)  

    :::image type="icon" source="../pipelines/tasks/build/media/sonarqube.png":::
      [SonarQube for MSbuild](https://devblogs.microsoft.com/devops/build-tasks-for-sonarqube-analysis/)  

    :::image type="icon" source="../pipelines/tasks/build/media/visual-studio-build.png":::
      [Visual Studio and MSbuild](../pipelines/tasks/build/visual-studio-build.md)  

    :::image type="icon" source="../pipelines/tasks/build/media/xamarin-android.png":::
      [Build an Android app with Xamarin](../pipelines/tasks/build/xamarin-android.md)  

    :::image type="icon" source="../pipelines/tasks/build/media/xamarin-ios.png":::
      [Build an iOS app with Xamarin on macOS](../pipelines/tasks/build/xamarin-ios.md)  

    **Build variables**  

    Use [predefined variables](../pipelines/build/variables.md) or add your custom variables when configuring your build definition or your build scripts.
:::column-end:::
:::column:::
    **Continuous integration builds**  

    [Define a CI build](../pipelines/build/triggers.md#ci) that compiles and tests your solutions whenever your team checks in code.  

    **Build summary charts**  

    View real-time build status and [add build summary charts to your dashboards](../report/dashboards/add-widget-to-dashboard.md).  

    :::image type="content" source="media/features/alm-feature-build-summary-widget.png" alt-text="Screenshot of a bar chart showing build summary data. Most bars are green, indicating that the builds finished successfully. A few bars are red.":::  

    **Code coverage charts**  

    From the Code Coverage tab on a Build summary page, you can view percentage of code coverage as well as upload code coverage data in Jacoco or Cobertura formats.  

    **Audit changes**  

    Determine who [changed what in the build definition and when they did it](../pipelines/build/history.md).  

    **Build retention policies**  

    [Define policies to automatically delete old completed builds ](../pipelines/policies/retention.md) to minimize clutter.  

    **Build permissions**  

    Determine who can [define, delete, and manage builds](../organizations/security/permissions.md#build).
:::column-end:::

:::row-end:::

Release

Automate deployments Reduce time-to-market and respond to customer feedback with greater agility by automating your release process. Deploy applications across platforms to all environments of the pipeline with just one selection. When to use Azure Pipelines or Build & Release in Azure DevOps Server? Evaluate how Azure Pipelines and Build & Release in Azure DevOps Server can help you in your development and deployment efforts. Release definitions Add a release definition by choosing the build version, target release environments, and tasks. Release environments Define and clone release environments, logical entities that represent where you want to deploy a release, such as a collection of servers, a cloud, multiple clouds, or an app store. Artifacts A release is fundamentally defined by versioned artifacts that make up the release. As you deploy the release to various environments, you deploy and validate the same artifacts on all environments. Tasks Automate release deployment by defining the events that trigger a release. Agents and agent pools Agent pools are the execution containers that specify the security context and runtime environment for the agents that run when you deploy a release.

Works for any app Deploy any type of application across multiple platforms including Windows and Linux, whether on-premises or in the cloud. Approval workflows Streamline your application release workflow by routing pre- and post-deployment approvals to multiple approvers or teams. Release notifications Receive email messages as releases occur. Approvers receive notifications automatically when a release is waiting for approval. Full traceability Monitor the status of your release pipelines and track every deployment in each of the environments. Retain full audit history of all activities performed on a release with detailed release logs and approval tracking. Release logs View or download log files as zip files. Log files contain the status for each step or task of a release, for each of the environments in the release definition. Each completed release--succeeded, failed, or abandoned--includes a live log file, details, and history for each step or task. Triggers Automate release deployment by defining the events that trigger a release. Variables Lookup the description for all release system, global, and agent variables.

Release names Specify the naming and numbering scheme you want used when adding releases. Global configuration properties Simplify management of custom values that you use to configure multiple releases by specifying custom values for any of the tasks in any of the environments of a release definition. View test results Open the Tests tab to view a summary of the test results, including pass/fail percentages and run duration. Sort the test results into groups or filter the results to show just passed, failed, or other results. Add release summary to dashboard (Azure DevOps Services) Add a release summary chart to a team dashboard. Extend and customize Create workflows tailored to your process by customizing our tasks, or extend with your own custom tasks. Manage permissions Grant or deny permissions to manage release definitions, environments approvers, or release permissions. Set permissions for users, groups, or per release definition.

Test

Comprehensive testing Perform exploratory, manual, system, and user acceptance tests for any app, in any language. Using Visual Studio or 3rd-party test frameworks, you can include automated tests with builds and releases for continuous integration and deployment. Unit testing with Git Create unit tests and run them frequently to make sure your code is working properly. Manual test plans and test cases Get started by creating test plans and test cases to track manual testing for sprints or milestones. Shared steps and shared parameters Create shared steps to include often repeated sequence of steps in your manual test cases, such as logging in. Repeat manual tests with different data using shared parameters.

Coded UI testing Use Visual Studio to create coded UI tests to test your application's user interface. Run test with your builds for continuous integration Use continuous integration builds to run tests automatically. Review automated test results after a build Review your test results to analyze any problems that were found. Quickly assign configurations to test plan, test suite, or test case From the context menu of a test plan, test suite, or test case, you can assign a configuration.

Exploratory testing Explore user stories without test cases or test steps using Azure Test Plans and exploratory testing. Or, download and install the Test & Feedback extension. Capture screenshots, annotate them, and submit bugs while you explore your web app - all directly from your Chrome browser. Record and play back manual tests With Azure Test Plans, you can record your keystrokes and gestures while you test an application. The next time you run the test, you can play back your actions quickly and accurately. Track test status and test results Quickly view the status of your testing using lightweight charts. Test environments Specify a combination of hardware and software that represents a user or machine environment in which your app runs. Test permissions Set permissions on who can manage test configurations, test environments, and publish and delete test results.

Dashboards and reports

Charts and dashboards

Multiple team dashboards Each team can create several team dashboards to help keep both the team and Stakeholders in sync. Each dashboard tile provides quick access to the progress of builds, status of work items, or latest code changes. Build history charts Add build history charts to your dashboards. Test charts Track the status of your test progress and test runs. Optionally add these charts to a dashboard. Test quality trend charts Add failure and duration charts for tests run as part of your build to your team dashboard.

Restrict or allow team members to manage dashboards (Azure DevOps Services) Set permissions to restrict or allow team members to manage dashboards. Capacity planning and tracking Easily track how much work your team has completed and has left to do in a sprint by adding the sprint capacity chart widget to your dashboard. Share dashboards with Stakeholders Grant non-licensed users access as Stakeholders (Azure DevOps Services | Azure DevOps Server) so they can view progress, run queries, and contribute ideas. Velocity charts Team velocity tracks the total estimated effort (story points or size) of backlog items (user stories or requirements) completed or still in progress within each sprint. Sprint burndown charts Monitor progress and review team patterns from sprint burndown charts Add release summary to dashboard (Azure DevOps Services) Add a release summary chart to a team dashboard.

Edit dashboard mode Add, remove, move, and configure widgets by choosing Edit dashboard. Select the checkmark to exit. | Auto-refresh dashboards You can enable auto-refresh for any team dashboard, and it automatically updates every five minutes. This is a useful feature for when your dashboard serves as a team wallboard. Widget catalog Add widgets to your dashboard to provide information and monitor the data your team needs. Work item query charts View the status of work in progress by charting the results of a flat-list query. You can create several types of charts—such as pie, column, or trend—for the same query. Optionally add these charts to a dashboard. Drag-n-drop layout Configure the layout to your specifications by dragging tiles into the sequence you want. Cumulative flow diagrams Track the progress of work on your backlogs through the CFD charts. Power BI dashboards (Azure DevOps Services) You can create dashboards, individual reports, or explore data collected for your Azure DevOps organization once you connect to Power BI.

::: moniker range=">= azure-devops-2019"

Power BI dashboards and reports

Basic Power BI concepts The 3 major building blocks of Power BI are dashboards, reports, and datasets. Get started You can create dashboards, individual reports, or explore data collected for your organization once you connect to Power BI.

Connect to Power BI Steps required to authorize Power BI to access your organization. Available data The Power BI Data Connector supports building reports to track status and trend work items.

::: moniker-end

::: moniker range="<= azure-devops-2020"

SQL Server Reports (Azure DevOps Server)

---

:::row::: :::column span="1"::: Reporting Services reports
You can analyze the progress and quality of your project by using the out-of-the-box reports in SQL Server Reporting Services. These reports aggregate metrics from work items, version control, test results, and builds. They are uploaded when you create a project based on the process Agile, Scrum, or CMMI that you choose.

  **Add Reporting Services reports**  
  If you need to add reporting services to a project or on-premises Azure DevOps Server after you've created your team projects, you can by [adding a report server and uploading reports](/previous-versions/azure/devops/report/admin/add-reports-to-a-team-project).  

  **Manage the data warehouse**  
  The reporting warehouse is a traditional data warehouse that consists of a [relational database and an Analysis Services database](/previous-versions/azure/devops/report/admin/manage-reports-data-warehouse-cube). You manage it through the following activities:  
  - [Manually process the data warehouse](/previous-versions/azure/devops/report/admin/manually-process-data-warehouse-and-cube)
  - [Rebuild the data warehouse](/previous-versions/azure/devops/report/admin/rebuild-data-warehouse-and-cube)
  - [Resolve schema conflicts](/previous-versions/azure/devops/report/admin/resolve-schema-conflicts)
  - [Change a process control setting](/previous-versions/azure/devops/report/admin/change-a-process-control-setting) 

:::column-end::: :::column span="1"::: Build reports
Build reports track the quality of software under development. By defining tests to run automatically as part of each build definition and instrumenting tests to gather code coverage data, you can gain insight about the quality of the builds, tests, and code.
- Build Quality Indicators - Build Success Over Time - Build Summary

  **Test and bug reports**  
  Test planning reports support monitoring the test progress and coverage of backlog items or user stories. Bug tracking reports illustrate the team's capacity to find and resolve bugs.  
  - [Test Case Readiness](/previous-versions/azure/devops/report/sql-reports/test-case-readiness-report) 
  - [Test Plan Progress](/previous-versions/azure/devops/report/sql-reports/test-plan-progress-report)"
  - [Bug Status](/previous-versions/azure/devops/report/sql-reports/bug-status-report)
  - [Bug Trends](/previous-versions/azure/devops/report/sql-reports/bug-trends-report)
  - [Reactivations](/previous-versions/azure/devops/report/sql-reports/reactivations-report) 

  **Required team activities to generate useful reports**
  To gain useful, actionable information from your reports, [team members must perform certain activities](/previous-versions/azure/devops/report/admin/review-team-activities-for-useful-reports).

:::column-end::: :::column span="1"::: Project management Project management reports provide insight into how much work the team is tackling within a sprint or release, and the rate of their progress. By linking work items and updating specific fields as work is performed, you can track the progress of individual stories and be able to more accurately estimate future activities.
Scrum reports
- Backlog Overview - Release Burndown - Sprint Burndown - Velocity Agile and CMMI
- Burndown and Burn Rate - Remaining Work - Requirements Overview (CMMI) - Status of All Iterations - Stories Overview (Agile) - Stories Progress (Agile) - Unplanned Work

 **Set permissions to view or create reports**  
 Enable members of your team to [view or manage Reporting Services reports](/previous-versions/azure/devops/report/admin/grant-permissions-to-reports). To create or modify reports, you need to grant them access to read databases.  

:::column-end::: :::row-end:::

::: moniker-end

Widgets

What is a widget? You build your dashboards by adding information tiles or widgets. The widget catalog provides a number of predefined widgets. Drag-and-drop widgets Drag widgets, tiles, or charts anywhere on a dashboard to configure the layout you want. Informational content and other links Markdown widget Adds a configurable tile to your dashboard to display any type of information, guidance, or links that you want using Markdown syntax. Team member Opens the team's quick dialog to add or remove team members. Visual Studio widget Provides links to open or download Visual Studio. The Visual Studio IDE client comes with the Team Explorer plug-in which provides quick access to several features (some of which aren't available through the web portal). Welcome widget Provides quick access to getting started info on how to track work, code, build, and test. Code widgets Code tile Configurable tile to display status and links to a Git or TFVC code repository, branch, or folder. Pull request Adds a configurable tile to display active pull requests requested by the team, or assigned to or requested by the person logged in. You select the Git repository for the pull requests of interest.

Plan and track work Assigned to me widget Provides quick access to work items assigned to the logged in user. Chart for work items Adds a configurable tile to display the chart for a shared query. New work item Add work items pre-scoped to your team's default area and iteration paths. Other links widget Provides quick access links from a team dashboard to request feedback, define sprints, and modify your team's area paths. Query tile Configurable tile to display the results and link to a shared query. Query results Adds a configurable query results list to a team dashboard. Requirements quality Displays a configurable widget that you can use to track quality continuously from a build or release definition.

Plan and track work (continued) Sprint burndown Adds a burndown chart for tracking a team's Scrum progress for the current sprint. Sprint capacity Adds a chart for tracking remaining capacity when tracking a team's Scrum progress for the current sprint. Sprint overview Displays a visual overview of the current sprint progress for tracking a team's Scrum progress for the current sprint, indicating the number of backlog items in progress, completed, or not started. Work links Provides quick access links from a team dashboard to open the team backlog, Kanban board, task board, and queries. Build and test widgets Chart for build history Configurable tile to display the histogram for a specific build definition. Deployment status (Azure DevOps Services) Configurable tile that shows you a consolidated view of the deployment status and test pass rate across multiple environments for a recent set of builds. Release definition overview Configurable tile to view and track the status of a release definition. The widget shows the release as a series of environments, with the name of the release and the date or time it was started. Test trend results Provides trend of test results, such as passed or failed tests, for a selected build definition. Extensibility Marketplace widgets You can find additional widgets by browsing the Marketplace Dashboard widget SDK Create a dashboard widget using the REST API service.

Extensibility

Marketplace

Feature availability: You can add Marketplace extensions from the web portal for Azure DevOps or for Visual Studio or Visual Studio Code.

What is the Marketplace? From the Marketplace, you can extend the functionality available to you by installing free extensions or purchasing a subscription or paid extension. Extensions support adding new capabilities to Visual Studio, Visual Studio Code, and Azure DevOps.

Subscriptions Visual Studio subscriptions are a way for you to get the Visual Studio IDE, team collaboration benefits like Azure DevOps, and subscriber benefits like dev/test use of Windows, Windows Server, and SQL Server. Extensions You can get and quickly install extensions to add functionality to Visual Studio, Visual Studio Code, or Azure DevOps Services. Try Azure Test Plans for free You can start a trial for Azure Test Plans for free. Get extensions for... Azure DevOps Services Visual Studio Visual Studio Code Get cloud subscriptions Buy cloud subscriptions in the Marketplace.

REST APIs

Get started with REST APIs Learn the basic patterns for using the REST APIs for Azure DevOps. Authorization Get authorization from your customers to access Azure DevOps Services resources using OAuth 2.0. REST API reference Use the REST APIs to work with Azure DevOps resources.

.NET client libraries For .NET developers building Windows apps and services that integrate with Azure DevOps, client libraries are available for integrating with work item tracking, version control, build, and other services are now available. These packages replace the traditional TFS Client OM installer and make it easy to acquire and redistribute the libraries needed by your app or service.

REST API samples Here are a number of samples that work with the REST APIs directly. C# client library samples Here are a few quick samples to help you get started with the client libraries.

Service hooks

Integrate with service hooks Service hooks enable you to perform tasks on other services when events happen in your Azure DevOps Projects Create integrations Integrate other services like HipChat, Slack, and UserVoice with Azure DevOps using service hooks.

Authorize Authorize other services to access your organization using the industry standard OAuth 2.0. Oauth 2.0 provides safe, secure access to your resources like work items, source code and build results by those other services.

Global

Web portal preferences Choose your name to access your profile settings and set your web portal preferences which include language (currently only English is supported for Azure DevOps), date and time pattern, and time zone. Language Interface Packs (LIPs) By using a Windows Language Interface Pack (LIP), you can install a language version of Windows, and then install various User Interface Language Packs. Language packs switch your English Visual Studio Professional user interface into any of these languages and have a majority of the user interface localized.

Localized content Most content that supports Azure DevOps is localized into the following 14 languages. English Chinese Simplified Chinese Traditional Czech German French Italian Japanese Korean Polish Portuguese (Brazil) Russian Spanish Turkish Currently, the visualstudio.com content is only available in English.

Visual Studio language pack Install the language pack to switch the UI display to different languages. Visual Studio provides localized UI support for these 14 languages. English Chinese Simplified Chinese Traditional Czech German French Italian Japanese Korean Polish Portuguese (Brazil) Russian Spanish Turkish Eclipse plug-in language support Install Team Explorer Everywhere, which includes language support for English, French, German, Japanese, and Simplified Chinese.

Monitor

Application Insights (Preview)

What is Application Insights Application Insights, an extensible analytics service that monitors your live web application, supports developers to continuously improve the performance and usability of apps. With it you can detect and diagnose performance issues, and understand what users actually do with your app. Web site availability monitoring Know when your site or service goes down by setting up tests and performance thresholds to monitor both uptime and responsiveness. Web site performance & usage Open the Performance blade to see request, response time, dependency and other data. Power BI integration Get even more flexible views of your telemetry, and present your web app telemetry alongside data from devices and other business sources.

Dashboard Get the full picture with customizable dashboards that track application health alongside usage metrics and app crashes. Within the dashboard, you can filter, search, and drill down to an event instance for more detail or to segment data. Diagnose failures and exceptions Quickly diagnose causes and correlate failed requests with exceptions and other events at both the client and server.

Usage analysis Gain a clear view of where your users are coming from and how they use your app . Add custom instrumentation to determine usage patterns and next version investment areas. Diagnose dependency issues See how long your application waits for dependencies and how often a dependency call fails. Dependencies are external components that your app calls such as an HTTP service, database, or file system. Custom data collectors Add custom data collectors to your app using the Application Insights API to customize your telemetry data. Continuous data export Perform custom analysis on your telemetry through continuous export of your data.

HockeyApp

Get HockeyApp for mobile app development Distribute mobile apps for testing, collect user metrics and feedback, and respond to crashes more easily by adding HockeyApp to your Agile, continuous integration, and continuous delivery workflows. Simplified distribution Manage distribution of development and production versions of your apps and use independent bundle identifiers that can run in parallel on the same device. Integrate with Azure DevOps Integrate HockeyApp directly in Azure DevOps to upload your Android, iOS, or Windows builds.

Comprehensive dashboard Manage all your apps, users, and devices from a single dashboard. Monitor crashes and feedback as well. As an admin, you'll have full control over which user can see and install which app.

Invite or recruit testers Invite beta testers and distribute your beta versions through the dashboard. Usage Get advanced metrics to understand the testing performed on your app. See which devices were tested, which testers used the app for how long, and which language was tested. Crash reports Get the information you need to analyze and respond to crashes by getting symbolicated stack traces and environment details. Webhooks Use webhooks to receive notifications about new versions, crash groups, and feedback.

Navigation

Web portal

Operational hubs Each hub—Home, Code, Work, build, and Test—supports specialized functions to share information, view and create dashboards, collaborate on code, plan and track work, build and test your applications, plus much, much more. Project page To view and quickly go to teams, team projects, branches, work items, pull requests and other objects that are relevant to you, use your Project page. Your profile and preferences Choose your name to access your profile settings, set preferences, create personal access tokens (Azure DevOps Services), set alerts, and log-in or out. Switch team context Go to a different team or project from the top row. Change team settings Customize features to meet your team needs by configuring your team assets. Keyboard shortcuts Increase your productivity by working with hot keys and shortcuts.

Home Provide team guidance through Welcome (Markdown format) pages and add team dashboards to monitor progress and trends. Code Manage source code using distributed Git repositories or Team Foundation version control. to Work Plan and track work by creating a product backlog, and managing work using Kanban or Scrum processes. Find work items you want to review or update by creating queries, or visualize progress by creating query-based charts Build Define and monitor builds and set up continuous builds to improve the quality of your app. Test Create and run manual tests for your app. Package (Azure DevOps Services, Preview) Share code as binary assets and control dependencies by subscribing to and working with Azure Artifacts feeds. Release (Azure DevOps Services, Preview) Manage the release of your app by deploying it to a specific environment for each separate release step, and by controlling the process through approvals for each step. Code search Search within your code branches (TFVC) and repositories (Git) to find files, commits, and more using powerful filters to obtain rich results. Find work items When in the Work hub, enter IDs or keywords to start a query to find work items that you want to review, triage, or update.

Collection-project-team structure The collection-project-team structure provides teams a high-level of autonomy to configure their tools in ways that work for them. It also supports administrative tasks to occur at the appropriate level. My favorites From any context, you can drag folders, queries, or builds to My favorites when working in the Code, Work, or Build hubs to provide quick access to those items. Team favorites From your team context, drag shared queries, builds, and folders to Team favorites to provide quick access to those items. Project admin context Open the admin context to add teams and manage permissions. From any project hub, choose to open the admin context. Project collection admin context From the collection admin context, you can manage collection-level permissions, and set build policies, and manage extensions. Choose to open the admin context, and then choose DefaultCollection.

Search, queries, and filters

Quick work item search Find work items based on ID, assignment, changed date, or keyword. Code search Find code based on keywords and search filters across your Git repositories. CodeLens search Find references and changes to your code, linked bugs, work items, code reviews, and unit tests. Work item queries Open shared queries or create your own query using the query editor to list work items or show hierarchical or dependent items. >Manage risks and dependencies Link work items to track related work, dependencies, and changes made over time. History & auditing Review and query work item change history to learn of past decisions and support future ones. Bulk add or modify using Excel Bulk add items to track or modify multiple field values using Excel.

Charts Turn your queries into a status or trend chart and share them with your team, organization, and Stakeholders. Tags Add tags to work items to filter backlogs and queries. Bulk update work items to add or remove tags: Azure DevOps Services | Azure DevOps Server.

Bulk modify Edit or update multiple work items from any backlog or query result. Supported tasks include: Modify field values Add or remove tags Reassign Move to an iteration Delete Link to a new or existing work item Change work item type Move to another project Create a new Git branch Query by date or current iteration List work items based on when changes occurred or if they belong to the team's current sprint. Query by workflow Find and list work items based on their current state, such as new, in progress, resolved, done, or closed. Query by Kanban board change Track status and trends of work items based on changes made to the Kanban board.

Security

Manage users and groups Add users to built-in groups to grant them access to your project. Optionally, create groups to customize access based on your business requirements. Permission states Understand how Allow, Deny, Not set and other permissions states control access to features and objects. Manage work access (Azure DevOps Services) Control user access with a directory to enforce policies about accessing company resources. Azure Active Directory (Azure DevOps Services) Easily control access to your team's critical resources and key business assets with Azure Active Directory groups. Set up groups (Azure DevOps Server) Create Windows or Active Directory groups to manage access to your team projects and collections. Built-in groups Understand the permissions granted to built-in groups and use them to manage access to your team projects and collections.

DevOps permissions Grant or restrict access to: Git repositories Git branches TFVC source code and folders Build Test) Release Work item tracking permissions Control access to specific features by setting permissions for a user or group. Area and iteration paths Query permissions Work item tags Move work items to another project Permanently delete work items Provide feedback through the Microsoft Feedback client Team admin role and permissions Add users as team administrators to enable them to configure team settings and manage team assets. Manage administrative permissions Add users to one of the following built-in groups to provide them permissions assigned to that group: Project Administrators, who manage shared features for a project Project Collection Administrators, who manage collection-level features Azure DevOps Server Administrators, who manage on-premises application servers Restrict access You can restrict access to several features and tasks by setting the permission state to Deny to individual users or a security group.

Stakeholder access Grant Stakeholders, non-licensed users, limited access to contribute ideas and access team dashboards. Query permissions Grant permissions to create shared queries and query folders. Process permissions To customize a process, add custom fields, or change the layout of a work item form, you must be a member of the Project Collection Administrators group or be granted explicit permissions to edit a specific process. Valid users Understand how valid user groups are populated and the permissions they're granted. Permission reference Provide or restrict access for practically any feature, function, or object at the collection or project level. SharePoint permissions (Azure DevOps Server) Grant permissions to view and contribute to SharePoint project portals. SQL Server reporting permissions (Azure DevOps Server) Grant permissions to view and author Excel and SQL Server reports.

Set up and installation

Free developer offers To get started, download and install Visual Studio an integrated development environment (IDE) that works with Azure DevOps. Migrate from on-premises to hosted You can migrate source code and work items from an on-premises Azure DevOps Server to the cloud.

Sign up for Azure DevOps Services Store your code, tests, and test results in the cloud with Azure DevOps Services, as well as plan your project and track progress. Install Azure DevOps Server Download and install the latest version of Azure DevOps Server. Azure DevOps Server provides the collaboration hub to support your teams DevOps tasks. at the center of the Microsoft devops solution.

Email configuration (Azure DevOps Server) For feedback requests, alerts, and other special controls to work, you must configure an SMTP server for your on-premises Azure DevOps. Automated, scheduled backups (Azure DevOps Server) Reduce the risk of lost data by scheduling automated backups of the data store. Built-in SQL Server database (Azure DevOps Server) For small teams, you can install Azure DevOps Server using SQL Server Express which installs with Azure DevOps Server.

Teams, team projects, and processes

Processes and process guidance

What is a process? A process defines the building blocks of the work item tracking system as well as other sub-systems you access through your project. Compare and choose a process Compare the three core system processes--Agile, Scrum, CMMI--before you choose one to create a project. Agile process Choose Agile when your team uses Agile planning methods, including Scrum, and tracks development and test activities separately. With Agile, you can track user stories and bugs on the Kanban board, or track bugs and tasks on the task board. Customize a process (Azure DevOps Services) Customizations you make to an inherited process automatically update all team projects that reference that process. You can customize your project as follows: Add and modify fields Modify the web form layout Modify the workflow states Add a custom work item type Manage processes (Azure DevOps Services) Create inherited processes and migrate team projects to use them. Set the default process and enable, disable, or delete processes you no longer want to use.

Kanban process tools You can use the Kanban board with any process--Agile, Scrum, CMMI--or project that you select or create. Agile Kanban tools support working with the Kanban board, adding task checklists, setting WIP limits, custom columns, split columns, custom swimlanes, and customizing cards. Scrum process Choose Scrum when your team practices Scrum and you want to track product backlog items (PBIs) and bugs on the Kanban board, or break PBIs and bugs down into tasks on the task board. Scrum work items and workflow process guidance Plan and track your work using the work item types and workflow supported by the Scrum process. Agile work items and workflow process guidance Plan and track your work using the work item types and workflow supported by the Agile process. Work item field index For descriptions and usage of each field used by the core and inherited processes, see Work item field index.

Scrum process tools Scrum processes can be used with any process--Agile, Scrum, CMMI--or project that you select or create. Agile Scrum tools support sprint planning, capacity planning, task boards, and burndown charts. Manage processes (Azure DevOps Services) Add users to built-in groups to grant them access to your project. Optionally, create groups to customize access based on your business requirements. CMMI process Choose CMMI when your team follows more formal project methods that require a framework for process improvement and an auditable record of decisions. CMMI supports tracking requirements, change requests, risks, and reviews. CMMI work items and workflow process guidance Plan and track your work using the work item types and workflow supported by the CMMI process.

::: moniker range="tfs-2018"

Process templates (Azure DevOps Server)

What is a process template? A process template is the forerunner and on-premises version of a process. It provides the building blocks of the work item tracking system as well as other sub-systems you access through your project. Process templates support full customization of all its objects. Manage process templates Download and upload process templates to support customization and upgrade of your work tracking experience and team projects.

Process template files You customize the initial configuration of team projects by customizing one or more process template files. By customizing these files, you can define the initial configuration of all team projects that are created from the process template. Configure Features Wizard Use the Configure Features Wizard to configure team projects after an Azure DevOps Server upgrade to access new features.

Changes made to process templates For a catalog of changes, see Changes made to process templates. Customize the Microsoft Project field mapping file You can customize how work item fields that are defined in Team Foundation map to fields in Microsoft Project. And, you can change how specific fields are published.

::: moniker-end

Team projects

What is a project? A project provides a repository for source code and a place for a group of developers to plan, track progress, and collaborate on building software solutions. A project lives within a project collection. You can grant permissions to and customize a project to support your business needs. Create a project You can create a project hosted in the cloud (Azure DevOps Services), avoiding maintenance and administrative overhead, or create a project on an on-premises Azure DevOps Server. Rename a project Rename a project as needed to reflect changes that occur within your org. Delete a project Simplify the navigation to team projects that are in use by deleting team projects you no longer use.

Collection-project-team structure The collection-project-team structure provides teams a high-level of autonomy to configure their tools in ways that work for them. It also supports administrative tasks to occur at the appropriate level. Change the process (Azure DevOps Services) You change the process of a project to apply customizations you've made to an inherited process. You can add and modify fields and modify the layout of each work item type defined for that process.

View your work across teams and team projects From your Project page, you can view and quickly go to teams, team projects, branches, work items, pull requests and other objects that are relevant to you and that are stored in different team projects within the organization or collection. Customize a project (Azure DevOps Server) You customize a project defined on an on-premises Azure DevOps Server by modifying definition files for work item types or process configuration, or changing field attributes. Update a project after an upgrade (Azure DevOps Server) Some features added when you upgrade your on-premises application server may require you to configure features to access them. Upload reports (Azure DevOps Server) Upload the latest reports provided for your process or add reports after you've already created a project by adding SQL Server Reporting Services.

Teams

What is a team? A team is an organizing unit used to support a number of team-configurable tools to plan and manage work and facilitate collaboration. Add team members Add organizations-Azure DevOps Services | Azure DevOps Server--to a team to enable users to share code, plan and track work, and access other team assets and resources. Add a team As your organization grows, consider moving from your default team of one to two or more teams to support feature-focused groups within your org. Add a team admin Add users to the team admin role to enable them to Manage teams and configure team tools. Team settings can only be configured by a team or project admin. Support Stakeholders Members within your org who don't have a license or contribute to developing the code base can track project priorities and provide direction, feature ideas, and business alignment to a team.

Team dashboards Share progress, status, and guidance with your team using configurable team dashboards. Team welcome page Provide in-project guidance through the Welcome page and other pages you format using Markdown. Setup a team hierarchy By configuring your teams and backlogs into an hierarchical structure, program owners can more easily track progress across teams, manage portfolios, and generate rollup data. Set team defaults Several Agile tools reference the team's default area path, iteration path, and activated sprints to automatically filter the set of work items they display. Understand how defaults are used](../organizations/settings/about-teams-and-settings.md). Select team sprints Select your team's sprints to gain access to sprint backlogs and task boards.

Configure team settings Configure, customize, and manage all team-related activities Team alerts As changes occur to work items, code reviews, source control files, and builds, your team can automatically receive email notifications for alerts that you define. Team groups A team group is created when you create a team. Use this group in queries or to set permissions for your team.

Traceability

Work item history & auditing Review and query work item change history to learn of past decisions and support future ones. Manage risks and dependencies Link work items to track related work, dependencies, and changes made over time. Create queries based on link type to monitor dependencies. Rich text comments Describe and comment on work to perform using formatted text, hyperlinks, and inline images. Discussion (Azure DevOps Services) Add or review comments added to a work item. Start by choosing .

Git code changes Get detailed information about what changes have been made to your local and centralized branches and repositories, compare files and folders, review history of commits and file changes. Integrate Git development with work tracking (Azure DevOps Services) Drive Git development and stay in sync as a team to complete backlog items and tasks using the Git Development section. Add branches, create pull requests, and view all development performed to support the specific work item. TFVC code changes Get detailed information about what changes have been made to your files, compare files and folders, view where and when changesets have been merged, and view file changes using annotate. Build changes Determine who changed what in the build definition and when they did it. Release audit history Retain full audit history of all activities performed on a release with detailed release logs and approval tracking. Release logs View or download log files as zip files. Log files contain the status for each step or task of a release, for each of the environments in the release definition. Each completed release--succeeded, failed, or abandoned--includes a live log file, details, and history for each step or task.

Related articles

We add new features frequently. We'll work to keep this list up-to-date. Other resources you might want to bookmark:

• Azure DevOps Services - Features update
• Azure DevOps Blog

Get started today using our cloud offering, Azure DevOps Services, or our on-premises Azure DevOps Server.