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/integrate/get-started/auth/tfs-basic-auth.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -17,12 +17,12 @@ ms.date: 11/10/2023
17
17
Use personal access tokens (PATs) with the cross-platform CLI for Azure DevOps.
18
18
19
19
> [!IMPORTANT]
20
-
> We don't recommend using basic authentication. For Azure DevOps Services, see [Sign in with a PAT](../../../cli/log-in-via-pat.md).
20
+
> We don't recommend using basic authentication or PATs. Instead, we recommend using [Microsoft Entra-based authentication](../authentication/entra.md), if you're interacting with Microsoft Entra accounts.
21
21
22
22
## Prerequisites
23
23
24
-
-Download the latest version of **Node.js source code**, from the [Node.js source code downloads page](https://nodejs.org/en/download/)
25
-
-Install the **Cross-platform CLI for Azure DevOps**
24
+
-Latest version of [**Node.js source code**](https://nodejs.org/en/download/)
25
+
-**Cross-platform CLI for Azure DevOps**
26
26
- Install **tfx-cli** using `npm`, a component of Node.js by running:
Copy file name to clipboardExpand all lines: docs/marketplace/grant-permissions.md
+4-3
Original file line number
Diff line number
Diff line change
@@ -19,12 +19,13 @@ Learn how to manage permissions for users or groups, so they can manage extensio
19
19
20
20
## Prerequisites
21
21
::: moniker range="azure-devops"
22
-
-Be a member of the Project Collection Administrators group to manage permissions for users or groups. Organization owners are automatically members of this group.
23
-
- Private extensions must be shared with your organization to be installed. Check out the [publishing documentation](../extend/publish/overview.md) for information on how to share private extensions.
22
+
-**Permissions:** Member of the Project Collection Administrators group. Organization owners are automatically members of this group.
23
+
-**Extension sharing:**Private extensions [shared with your organization](../extend/publish/overview.md#share-your-extension).
24
24
::: moniker-end
25
25
26
26
::: moniker range="< azure-devops"
27
-
- Be a member of the Project Collection Administrators group or have "Edit collection-level information" permissions to manage permissions for users or groups. Organization owners are automatically members of the Project Collection Administrators group.
27
+
-**Permissions:** Member of the Project Collection Administrators group or **Edit collection-level information** permissions. Organization owners are automatically members of this group.
28
+
-**Extension sharing:** Private extensions [shared with your organization](../extend/publish/overview.md#share-your-extension).
Copy file name to clipboardExpand all lines: docs/marketplace/install-extension.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -24,18 +24,18 @@ For more information about extensions, see the [developing](../extend/overview.m
24
24
25
25
::: moniker range="azure-devops"
26
26
27
-
-**Permissions:**Be a member of the Project Collection Administrators group to install extensions. Organization owners are automatically members of this group. If you don't have permissions, you can [request extensions](./request-extensions.md) instead or [look up a project collection administrator](../organizations/security/look-up-project-collection-administrators.md).
28
-
-**Extension sharing:** Private extensions must be shared with your organization to be installed. For more information about sharing private extensions, see the [publishing documentation](../extend/publish/overview.md).
27
+
-**Permissions:**Member of the Project Collection Administrators group. Organization owners are automatically members of this group. If you don't have permissions, you can [request extensions](./request-extensions.md) instead or [look up a project collection administrator](../organizations/security/look-up-project-collection-administrators.md).
28
+
-**Extension sharing:** Private extensions [shared with your organization](../extend/publish/overview.md#share-your-extension).
29
29
30
30
::: moniker-end
31
31
32
32
::: moniker range="< azure-devops"
33
33
34
-
-**Permissions:**Be a member of the Project Collection Administrators group or have "Edit collection-level information" permissions. Organization owners are automatically members of this group. If you don't have permissions, you can [request extensions](./request-extensions.md) instead or [look up a project collection administrator](../organizations/security/look-up-project-collection-administrators.md).
35
-
-**Extension sharing:** Private extensions must be shared with your organization to be installed. For more information about sharing private extensions, see the [publishing documentation](../extend/publish/overview.md).
34
+
-**Permissions:**Member of the Project Collection Administrators group or **Edit collection-level information** permissions. Organization owners are automatically members of this group. If you don't have permissions, you can [request extensions](./request-extensions.md) instead or [look up a project collection administrator](../organizations/security/look-up-project-collection-administrators.md).
35
+
-**Extension sharing:** Private extensions [shared with your organization](../extend/publish/overview.md#share-your-extension).
36
36
37
37
> [!NOTE]
38
-
> To use an existing Azure subscription for billing, you need at least co-administrator permissions for that subscription. If you don't have permissions, an Azure Account Administrator or Service Administrator can [add you as co-administrator](/azure/billing-add-change-azure-subscription-administrator) to the Azure subscription in the Azure portal.
38
+
> To use an existing Azure subscription for billing, have at least co-administrator permissions for that subscription. If you don't have permissions, an Azure Account Administrator or Service Administrator can [add you as co-administrator](/azure/billing-add-change-azure-subscription-administrator) to the Azure subscription in the Azure portal.
39
39
40
40
Your project collection reuses your Azure subscription for future Marketplace purchases. [Where can I find more info about Azure billing?](faq-extensions.yml)
Copy file name to clipboardExpand all lines: docs/marketplace/request-extensions.md
+3-2
Original file line number
Diff line number
Diff line change
@@ -20,8 +20,9 @@ Project Collection Administrators receive an email when another project member r
20
20
21
21
## Prerequisites
22
22
23
-
- To request extensions, be a contributor for your organization.
24
-
- To approve extensions, be a member of the Project Collection Administrators group and have [**Edit collection-level information** permissions](../organizations/security/permissions.md#collection).
23
+
**Permissions:**
24
+
- To request extensions: Contributor for your organization.
25
+
- To approve extensions: Member of the Project Collection Administrators group and [**Edit collection-level information** permissions](../organizations/security/permissions.md#collection).
There might be other prerequisites for managing specific items. For more information, see [Security groups, service accounts, and permissions reference](../../organizations/security/permissions.md).
27
+
22
28
## Add work items, queries, or other work tracking artifacts
23
29
24
30
You can quickly add a query or work item when working from a **Boards** or **Work** page.
25
31
26
-
::: moniker range=">= azure-devops-2019"
27
-
28
32
Choose a **Boards** page—such as **Work Items**, **Boards**, or **Backlogs**. Then choose the :::image type="icon" source="../../media/icons/blue-add.png" border="false"::: plus icon and select from the menu of options.
To add other work tracking artifacts, see one of the following articles:
38
38
39
39
- To add a board, backlog, or sprint backlog, first [add a team](../../organizations/settings/add-teams.md) which will be associated with those artifacts
@@ -46,49 +46,33 @@ To add other work tracking artifacts, see one of the following articles:
46
46
47
47
You can quickly add a pull request, Git repository, or work item using the **Add** menu when working from **Code**.
48
48
49
-
::: moniker range=">= azure-devops-2019"
50
-
51
49
Expand the **Repos** service and choose **Files**, **Commits**, or **Pull Requests** (Git repos) or **Files**, **Changesets**, or **Shelvesets** (TFVC). Then, choose the :::image type="icon" source="../../media/icons/blue-add.png" border="false"::: plus icon and select from the menu of options.
For details on adding a Git repository, see [Git repository](../../repos/git/creatingrepo.md).
57
55
58
-
::: moniker-end
59
-
60
-
61
-
62
-
63
56
Note that you can only add one TFVC repository per project, but an unlimited number of Git repositories. To learn more about Git artifacts, see one of the following articles:
-[Add work items](../../boards/work-items/view-add-work-items.md)
69
62
70
-
71
-
72
63
## Add build and release pipelines
73
64
74
-
::: moniker range=">= azure-devops-2019"
75
-
76
65
Expand **Pipelines** and choose **Builds** or **Releases**. Then choose the :::image type="icon" source="../../media/icons/blue-add.png" border="false"::: plus icon and select from the menu of options.
77
66
78
67
> [!div class="mx-imgBorder"]
79
68
> 
80
69
81
-
::: moniker-end
82
-
83
-
84
-
85
-
To learn more about adding other pipeline related artifacts, see the following articles:
70
+
For more information about adding other pipeline related artifacts, see the following articles:
Agile tools and dashboards are typically associated with teams. You add teams to a project. To learn more about teams, see [About teams and Agile tools](../../organizations/settings/about-teams-and-settings.md). To add a team, see [Add a team and team members](../../organizations/settings/add-teams.md).
@@ -97,17 +81,11 @@ Agile tools and dashboards are typically associated with teams. You add teams to
97
81
98
82
## View teams already defined
99
83
100
-
::: moniker range=">= azure-devops-2019"
101
-
102
84
To view the set of defined teams, open **Project settings**, and choose **Overview**.
@@ -118,23 +96,15 @@ Dashboards are associated with a team or a project. Each team can create and con
118
96
Dashboards are associated with a team. Each team can create and configure a number of dashboards. To learn how, see [Add a dashboard](../../report/dashboards/dashboards.md).
119
97
::: moniker-end
120
98
121
-
122
99
## Add a wiki
123
100
124
101
If you don't have a wiki yet, you can add one. Once added, you can add and update pages to that wiki.
125
102
126
-
127
-
::: moniker range=">= azure-devops-2019"
128
-
129
103
-[Create a wiki](../wiki/wiki-create-repo.md)
130
104
-[Add and edit wiki pages](../wiki/add-edit-wiki.md)
131
105
-[Publish a Git repository to a wiki](../wiki/publish-repo-to-wiki.md)
Several applications and pages support filtering, which is very useful when a large number of artifacts or items have been defined. Most directory views provide one or more filter functions.
21
-
22
-
You can filter most items using keywords or a user name for an author of an item or where work is assigned to them. You can filter lists and boards in the following areas:
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.
32
21
22
+
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:
> You may have fewer or additional filter options based on the [features you've enabled](preview-features.md) or the platform and version that you are working from.
29
+
> You might have fewer or other filter options based on the [enabled features](preview-features.md) or the platform and version that you're working from.
37
30
31
+
## Prerequisites
38
32
39
-
<aid="filter"></a>
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.
40
37
38
+
<aid="filter"></a>
41
39
42
40
## Filter based on keywords, tags, or fields
43
41
44
-
To turn filtering on, choose the :::image type="icon" source="../../media/icons/filter-icon.png" border="false"::: filter icon.
42
+
To turn on filtering, choose the :::image type="icon" source="../../media/icons/filter-icon.png" border="false"::: filter icon.
45
43
46
-
You can filter work items by typing 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 will list 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.
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.
The filtered set is always a flat list, even if you've selected to show parents.
48
+
The filtered set is always a flat list, even if you selected to show parents.
51
49
52
50
### Characters ignored by keyword filter criteria
53
51
54
-
The filter criteria ignores the following characters: `,` (comma), `.` (period), `/` (forward slash), and `\` (back slash).
52
+
The filter criteria ignore the following characters: `,` (comma), `.` (period), `/` (forward slash), and `\` (back slash).
55
53
56
54
::: moniker range=">= azure-devops-2019"
57
55
58
56
## Filter directories
59
57
60
58
Choose the :::image type="icon" source="../../media/icons/filter-icon.png" border="false"::: filter icon to filter a directory list by keyword, team, or other supported field. Keywords apply to titles, descriptions, and team names.
61
59
62
-
For example, here we turn filtering on for the dashboard directory.
60
+
For example, here we turn on filtering for the dashboard directory.
63
61
64
62
> [!div class="mx-imgBorder"]
65
63
> 
Several features depend on the project, repository, or team that you have selected. For example, dashboards, backlogs, and board views will change depending on the project and team you select.
20
19
21
20
Also, when you add a work item, the system references the default area and iteration paths defined for the team context. Work items you add from the team dashboard (new work item widget) and queries page are assigned the team default iteration. Work items you add from a team backlog or board, are assigned the team default backlog iteration. For more information, see [About teams and Agile tools](../../organizations/settings/about-teams-and-settings.md).
22
21
23
22
## Prerequisites
24
23
25
-
* Be added to a project as a member of the **Contributors** or administrator security group. To get added, [Add users to a project or team](../../organizations/security/add-users-team-project.md).
0 commit comments