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/boards/backlogs/remove-delete-work-items.md
+8-53Lines changed: 8 additions & 53 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,57 +35,12 @@ To move a work item from one project to another, or to change the work item type
35
35
## Prerequisites
36
36
37
37
| Category | Requirements |
38
-
|--------------|-------------|
39
-
|**Permissions**| - To remove, delete, and restore work items: Member of the **Contributors** group.<br>- To permanently delete work items: Member of the **Project Administrators** group or granted the required permission.<br>- Users with **Stakeholder** access can view the contents of the **Recycle Bin**, but can't restore or permanently delete items in the bin regardless of the permissions they're granted.|
40
-
41
-
:::row:::
42
-
:::column span="1":::
43
-
**Task**
44
-
:::column-end:::
45
-
:::column span="2":::
46
-
**Required permissions**
47
-
:::column-end:::
48
-
:::row-end:::
49
-
---
50
-
:::row:::
51
-
:::column span="1":::
52
-
[Change state to **Remove** or **Cut**](#remove)
53
-
:::column-end:::
54
-
:::column span="2":::
55
-
- **Area Path** permission set to **Allow**: **Edit work items in this node**
56
-
- By default, members of the **Contributors** group have this permission.
57
-
:::column-end:::
58
-
:::row-end:::
59
-
:::row:::
60
-
:::column span="1":::
61
-
[Delete work items](#delete) and
62
-
[Restore work items](#restore)
63
-
:::column-end:::
64
-
:::column span="2":::
65
-
- Project-level permission set to **Allow**: **Delete and restore work items**
66
-
- At least [**Basic** access](../../organizations/security/access-levels.md).
67
-
- By default, members of the **Contributors** group have this permission.
68
-
:::column-end:::
69
-
:::row-end:::
70
-
:::row:::
71
-
:::column span="1":::
72
-
[Permanently delete or destroy work items](#restore-or-destroy-work-items)
73
-
:::column-end:::
74
-
:::column span="2":::
75
-
- Project-level permission set to **Allow**: **Permanently delete work items**
76
-
- By default, members of the **Project Administrators** group have this permission.
77
-
:::column-end:::
78
-
:::row-end:::
79
-
:::row:::
80
-
:::column span="1":::
81
-
[Delete or destroy work items from the command line](#az-boards-cli)
82
-
:::column-end:::
83
-
:::column span="2":::
84
-
- Project-level permission set to **Allow**: **Permanently delete work items**
85
-
- By default, members of the **Project Administrators** group have this permission.
86
-
:::column-end:::
87
-
:::row-end:::
88
-
---
38
+
|----------|-------------|
39
+
|**General Access**| - To remove, delete, and restore work items: Member of the **Contributors** group<br>- To permanently delete work items: Member of the **Project Administrators** group or granted the required permission<br>- Users with **Stakeholder** access can view the **Recycle Bin** contents but can't restore or permanently delete items regardless of permissions granted |
40
+
|**Change state to Remove or Cut**| - **Area Path** permission set to **Allow**: **Edit work items in this node**<br>- By default, members of the **Contributors** group have this permission |
41
+
|**Delete and restore work items**| - Project-level permission set to **Allow**: **Delete and restore work items**<br>- At least [**Basic** access](../../organizations/security/access-levels.md)<br>- By default, members of the **Contributors** group have this permission |
42
+
|**Permanently delete or destroy work items**| - Project-level permission set to **Allow**: **Permanently delete work items**<br>- By default, members of the **Project Administrators** group have this permission |
43
+
|**Delete or destroy work items from command line**| - Project-level permission set to **Allow**: **Permanently delete work items**<br>- By default, members of the **Project Administrators** group have this permission |
89
44
90
45
For a simplified view of permissions assigned to built-in groups, see [Permissions and access](../get-started/permissions-access-boards.md).
91
46
@@ -117,7 +72,7 @@ To cause removed items to not show up in queries, you must add a clause that fil
117
72
::: moniker range="<=azure-devops"
118
73
119
74
> [!NOTE]
120
-
> The *Removed* state isn't supported with the Basic process. It is only supported with the Agile, Scrum, and CMMI process work item types. The Basic process is available with Azure DevOps Services and Azure DevOps Server 2020 and later versions.
75
+
> The *Removed* state isn't supported with the Basic process. It's only supported with the Agile, Scrum, and CMMI process work item types. The Basic process is available with Azure DevOps Services and Azure DevOps Server 2020 and later versions.
121
76
122
77
::: moniker-end
123
78
@@ -186,7 +141,7 @@ Restore deleted work items or permanently delete them from the web portal **Recy
186
141
::: moniker-end
187
142
188
143
> [!NOTE]
189
-
> Test artifacts such as test plans, test suites, and test cases are all considered work items in Azure DevOps. However, the method used to [Delete test artifacts in Azure Boards](../backlogs/delete-test-artifacts.md) differs from the method for deleting non-test work items. Azure DevOps Services supports a soft-deletion model, where Test Plans and Test Suites are in a soft-delete state for 14 days after they are deleted. While they are in the soft-delete state, they can be restored.
144
+
> Test artifacts such as test plans, test suites, and test cases are all considered work items in Azure DevOps. However, the method used to [Delete test artifacts in Azure Boards](../backlogs/delete-test-artifacts.md) differs from the method for deleting nontest work items. Azure DevOps Services supports a soft-deletion model, where Test Plans and Test Suites are in a soft-delete state for 14 days after they're deleted. While they are in the soft-deleted state, they can be restored.
0 commit comments