You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/index.yml
+3-3
Original file line number
Diff line number
Diff line change
@@ -6,12 +6,12 @@ brand: azure
6
6
7
7
metadata:
8
8
title: Azure DevOps documentation
9
-
description: Collaborate on software development through source control, work tracking, and continuous integration and delivery, both on-premises and in the cloud!
9
+
description: Collaborate on software development with source control, work tracking, and continuous integration and delivery, both on-premises and in the cloud!
Create an Azure DevOps project to establish a repository for source code and to plan and track work. You can manage and structure your project to support your business needs. Each project provides boundaries to isolate data from other projects. For more information, see [About projects and scaling your organization](about-projects.md).
20
+
Create an Azure DevOps project to set up a source code repository and organize your work. You can tailor and manage your project to meet your business requirements. Each project isolates its data from other projects. For more information, see [About projects and scaling your organization](about-projects.md).
@@ -49,7 +49,7 @@ Create an Azure DevOps project to establish a repository for source code and to
49
49
::: moniker range="azure-devops"
50
50
51
51
> [!IMPORTANT]
52
-
> To create a public project or [make a private project public](../projects/make-project-public.md), enable additional policy settings to work with public projects, and then return to this article to create your project.
52
+
> To create a public project or [make a private project public](../projects/make-project-public.md), enable other policy settings to work with public projects, and then return to this article to create your project.
53
53
54
54
::: moniker-end
55
55
@@ -111,7 +111,7 @@ There isn't a limit on the number of projects that you can create within a proje
111
111
112
112
::: moniker range="< azure-devops"
113
113
114
-
1. Sign in to your DevOps Server collection (```https://<your-devops-server>/<your-organization>```).
114
+
1. Sign in to your collection (```https://<your-devops-server>/<your-collection>```).
115
115
116
116
2. Select **New project**. You can also [create a project from a process](../settings/work/manage-process.md).
If a project becomes obsolete, you can [delete it](#delete-project) from your organization or collection in Azure DevOps. Likewise, if you're migrating from an on-premises Azure DevOps Server to Azure DevOps Services, it might be necessary to delete the project. The removal of projects can also enhance navigation by restricting it to only those projects that are currently in use.
19
+
If a project becomes obsolete, you can [delete it](#delete-project) from your organization or collection in Azure DevOps. If you're migrating from an on-premises Azure DevOps Server to Azure DevOps Services, you might also need to delete the project. Removing unused projects can enhance navigation by limiting it to only those projects that are currently in use.
20
20
21
21
> [!CAUTION]
22
22
> - Soft-deleted projects from the web portal are permanently removed if not restored within 28 days.
23
23
> - In rare cases, our deletion process might take up to 70 days due to backend retries and the need to delete data from multiple sources.
24
-
> - Hard-deleted projects from the on-premises Azure DevOps Administration Console cannot be restored.
24
+
> - Hard-deleted projects from the on-premises Azure DevOps Administration Console can't be restored.
25
25
> For more information, see [Restore a project](#restore-a-deleted-project) and [Save project data](#save-project-data).
26
26
27
27
## Prerequisites
@@ -175,7 +175,7 @@ If you inadvertently delete a project in Azure DevOps, you can restore it within
175
175
176
176
::: moniker range="azure-devops"
177
177
178
-
1. Sign in to your organization (```https://dev.azure.com/{yourorganization}```).
178
+
1. Sign in to your organization (```https://dev.azure.com/{Your_Organization}```).

@@ -207,14 +207,14 @@ If you inadvertently delete a project in Azure DevOps, you can restore it within
207
207
::: moniker range="azure-devops-2019"
208
208
209
209
> [!NOTE]
210
-
> The UI doesn't support restoring a team project for Azure DevOps Server 2019. Use the following REST API or PowerShell methods to restore a deleted team project. For more information, see [Projects-Update REST API](/rest/api/azure/devops/core/projects/update).
210
+
> The UI doesn't support restoring a team project for Azure DevOps Server 2019. Use the following REST API or PowerShell methods to restore a deleted team project. For more information, see [Projects-Update REST API](/rest/api/azure/devops/core/projects/update).
211
211
212
212
::: moniker-end
213
213
214
214
### Restore project with REST API
215
215
216
216
> [!WARNING]
217
-
> To restore a project with a name that's already taken, you must rename the project before you can restore it. To rename the project, enter the following text in the request body: `"name":"new name"`
217
+
> To restore a project with an existing name, rename the project first. To rename the project, enter the following text in the request body: `"name":"new name"`.
218
218
219
219
1. Open a browser window and enter a URL that uses the following form:
Several applications and pages in Azure DevOps support filtering, which is particularly useful when dealing with a large number of artifacts or items. Most directory views offer one or more filter functions to help you quickly find what you're looking for.
19
+
Several applications and pages in Azure DevOps support filtering, which is useful when dealing with a large number of artifacts or items. Most directory views offer one or more filter functions to help you quickly find what you're looking for.
21
20
22
21
You can filter most items using keywords or a user name, either for the author of an item or where work is assigned to them. Filtering can be applied to lists and boards in the following areas:
23
22
@@ -30,28 +29,26 @@ You can filter most items using keywords or a user name, either for the author o
30
29
31
30
## Prerequisites
32
31
33
-
-**Access**:
34
-
- Member of the project where you want to apply filters. If you don't have access, request it from your project administrator.
35
-
- At least **Basic**access to use filtering features. Users with Stakeholder access may have limited filtering capabilities.
36
-
-**Permissions**: Necessary permissions to view and interact with the items that you want to filter. This typically includes being a member of the Contributors group or having similar permissions.
32
+
| Category | Requirements |
33
+
|--------------|-------------|
34
+
|**Permissions**|Member of the **Contributors**group or similar permissions. |
35
+
|**Access**| - Member of the project where you want to apply filters. If you don't have access, request it from your project administrator.</br>- At least **Basic** access to use filtering features. Users with Stakeholder access might experience limited filtering capabilities.|
37
36
38
37
<aid="filter"></a>
39
38
40
39
## Filter based on keywords, tags, or fields
41
40
42
41
To turn on filtering, choose the :::image type="icon" source="../../media/icons/filter-icon.png" border="false"::: filter icon.
43
42
44
-
You can filter work items by entering a keyword or using one or more of the fields provided, such as work item type, assigned to, state, and tags. Based on the keyword that you enter, the filter function lists work items based on any visible/displayed column or field, including tags. Also, you can enter a value for an ID, whether or not the ID field is visible.
43
+
You can filter work items by entering a keyword or using fields like work item type, assigned to, state, and tags. The filter lists work items based on any visible column or field, including tags. You can also enter an ID value, regardless of the visibility of the ID field.
The web portal for Azure DevOps is organized around a set of services and administrative pages and several taskspecific features, such as the search box. The service labels differ depending on whether you work from Azure DevOps Services or Azure DevOps on premises and its version.
20
+
The Azure DevOps web portal is organized into various services, administrative pages, and task-specific features like the search box. Service labels vary depending on whether you’re using Azure DevOps Services or an on-premises version.
Each service provides you with one or more pages, which support many features and functional tasks. Within a page, you might then have a choice of options to select a specific artifact or add an artifact.
24
+
Each service offers multiple pages with numerous features and functional tasks. Within each page, you can choose options to select or add specific artifacts.
25
25
26
26
::: moniker-end
27
27
28
28
::: moniker range="azure-devops-2019"
29
29
30
-
The web portal for Azure DevOps Server is organized around a set of services—such as, **Overview**, **Boards**, **Repos**, **Pipelines**, **Test Plans**, and **Artifacts—as well as administrative pages and several task-specific features such as the search box. Each service provides you with one or more pages that support many features and functional tasks. Within a page, you might then have a choice of options to select a specific artifact or add an artifact.
31
-
32
-
Each service provides you with one or more pages that support many features and functional tasks. Within a page, you might then have a choice of options to select a specific artifact or add an artifact.
33
-
34
-
::: moniker-end
35
-
36
-
37
-
38
-
39
-
Here's what you need to know to get up and running using the web portal.
40
-
41
-
::: moniker range=">= azure-devops-2019"
42
-
-[**Open a service, page, or settings**](go-to-service-page.md): use to switch to a different [service or functional area](../../user-guide/services.md)
43
-
-[**Add an artifact or team**](add-artifact-team.md): use to quickly add a work item, Git repo, build or release pipelines, or a new team
44
-
-[**Open another project or repo**](work-across-projects.md): use to switch to a different project or access work items and pull requests defined in different projects, or your favorite items
45
-
-[**Open team artifacts, use breadcrumbs, selectors and directories**](use-breadcrumbs-selectors.md): use to navigate within a service, to open other artifacts, or return to a root function
46
-
-[**Work with favorites**](set-favorites.md): favorite artifacts to support quick navigation
47
-
-[**Search box**](../search/get-started-search.md): use to find code, work items, or wiki content
48
-
-[**Your profile menu**](../../organizations/settings/set-your-preferences.md?toc=/azure/devops/project/navigation/toc.json&bc=/azure/devops/project/navigation/breadcrumb/toc.json): use to set personal preferences, notifications, and enable preview features
49
-
-[**Settings**](../../organizations/settings/about-settings.md#project-administrator-role-and-managing-projects): use to add teams, manage security, and configure other project and organization level resources.
30
+
The Azure DevOps Server web portal is organized into several services, including **Overview**, **Boards**, **Repos**, **Pipelines**, **Test Plans**, and **Artifacts**. It also includes administrative pages and task-specific features like the search box. Each service offers multiple pages with various features and functional tasks. Within each page, you can choose options to select or add specific artifacts.
50
31
51
32
::: moniker-end
52
33
34
+
## Key features and navigation
53
35
36
+
Here's what you need to know to start using the web portal effectively.
54
37
38
+
-[**Open a service, page, or settings**](go-to-service-page.md): Use to switch to a different [service or functional area](../../user-guide/services.md)
39
+
-[**Add an artifact or team**](add-artifact-team.md): Use to quickly add a work item, Git repo, build or release pipelines, or a new team
40
+
-[**Open another project or repo**](work-across-projects.md): Use to switch to a different project or access work items and pull requests defined in different projects, or your favorite items
41
+
-[**Open team artifacts, use breadcrumbs, selectors and directories**](use-breadcrumbs-selectors.md): Use to navigate within a service, open other artifacts, or return to a root function
42
+
-[**Work with favorites**](set-favorites.md): Mark your favorite artifacts for quick navigation
43
+
-[**Search box**](../search/get-started-search.md): Use to find code, work items, or wiki content
44
+
-[**Your profile menu**](../../organizations/settings/set-your-preferences.md?toc=/azure/devops/project/navigation/toc.json&bc=/azure/devops/project/navigation/breadcrumb/toc.json): Use to set personal preferences, notifications, and enable preview features
45
+
-[**Settings**](../../organizations/settings/about-settings.md#project-administrator-role-and-managing-projects): Use to add teams, manage security, and configure other project and organization level resources.
55
46
56
-
::: moniker range=">= azure-devops-2019"
57
47
> [!NOTE]
58
-
> Only those services that are enabled will appear in the user interface. For example, if **Boards** is disabled, then **Boards** or **Work** and all pages associated with that service won't appear. To enable or disable a service, see [Turn an Azure DevOps service on or off](../../organizations/settings/set-services.md).
59
-
::: moniker-end
60
-
61
-
62
-
::: moniker range=">= azure-devops-2019"
63
-
You select services—such as **Boards**, **Repos**, and **Pipelines**—from the sidebar and pages within those services.
> Only enabled services are visible in the user interface. For example, if **Boards** is disabled, then **Boards** or **Work** and all pages associated with that service don't appear. To enable or disable a service, see [Turn an Azure DevOps service on or off](../../organizations/settings/set-services.md).
70
49
50
+
Select services—such as **Boards**, **Repos**, and **Pipelines**—from the sidebar and pages within those services.
Now that you have an understanding of how the user interface is structured, it's time to get started using it. As you can see, there are numerous features and functionality.
54
+
Now that you understand the user interface structure, it’s time to start using it. You can find a wide range of features and functionalities to explore.
74
55
75
56
If all you need is a code repository and bug tracking solution, then start with [Get started with Git](../../repos/git/gitquickstart.md) and [Manage bugs](../../boards/backlogs/manage-bugs.md).
76
57
@@ -138,8 +119,8 @@ Although you can access source code, work items, and builds from both clients, s
0 commit comments