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
With filter functions, you can interactively apply one or more filters to an Azure Boards tool. Each tool is already filtered to show a subset of work items according to the tool function. For example, Backlogs and Boards display work items based on the selected Area Paths and Iteration Paths for the team. Query Results list work items based on the query clauses you've defined.
20
+
::: moniker range=">= tfs-2017"
21
21
22
+
With filter functions, you can interactively apply one or more filters to an Azure Boards tool. Each tool is already filtered to show a subset of work items according to the tool function. For example, Backlogs and Boards display work items based on the selected **Area Paths** and **Iteration Paths** for the team. **Query Results** list work items based on the query clauses you've defined.
23
+
::: moniker-end
24
+
::: moniker range=">= tfs-2017"
22
25
You enable the filter feature by choosing :::image type="icon" source="../../media/icons/filter-icon.png" border="false"::: **Filter**.
26
+
::: moniker-end
27
+
::: moniker range=">=azure-devops-2019"
28
+
:::image type="content" source="media/filter/filter-backlogs.png" alt-text="Screenshot of choosing Filter function latest versions.":::
29
+
::: moniker-end
23
30
24
-
> [!div class="mx-imgBorder"]
25
-
> 
26
31
32
+
::: moniker range="tfs-2017 || tfs-2018"
33
+
:::image type="content" source="media/filter/filter-backlogs-options-tfs-2017.png" alt-text="Screenshot of initial keyword filter function. ":::
34
+
::: moniker-end
35
+
36
+
::: moniker range="tfs-2015"
37
+
:::image type="content" source="media/filter/initial-keyword-filter-function.png" alt-text="Screenshot of initial keyword filter function. ":::
38
+
::: moniker-end
27
39
40
+
::: moniker range=">= tfs-2017"
28
41
From these tools, you may still have a large number of work items listed or displayed. Interactive filtering supports your ability to focus on a subset of them. You can apply one or more filter functions to each of the Azure Boards tools.
42
+
::: moniker-end
29
43
30
-
::: moniker range="<= tfs-2015"
31
-
You can use the keyword, ID, and tag filter functions with Boards, Backlogs, Sprint Backlogs, and Queries.
44
+
::: moniker range="tfs-2015"
45
+
With the filter function, you can interactively apply a keyword filters to an Azure Boards tool. Each tool is already filtered to show a subset of work items according to the tool function. For example, **Backlogs**and **Boards** display work items based on the selected **Area Paths** and **Iteration Paths** for the team. **Query Results** list work items based on the query clauses you've defined. You can use the filter function to filter work items based on a keyword, ID or tag.
32
46
::: moniker-end
33
47
34
48
::: moniker range=">= tfs-2017"
35
49
36
50
Use filters to complete these tasks:
37
51
- In daily scrum meetings, filter the Kanban board to focus on assigned work for a specific sprint.
38
52
- Or, if your team uses the Sprints Taskboard, filter for a team member's completed assigned work.
39
-
- To focus on a group of work items, filter based on the Parent Work Item, by Area Path, or Tags.
53
+
- To focus on a group of work items, filter based on the **Parent Work Item**, by **Area Path**, or **Tags**.
40
54
- To triage work items, create a query and filter to focus on similar work grouped by Area Path or Tags.
41
55
42
56
43
57
::: moniker-end
44
58
45
59
::: moniker range=">= tfs-2017"
46
-
47
60
## Supported filter functions
48
-
49
61
::: moniker-end
50
62
51
63
::: moniker range=">= azure-devops-2019"
52
-
53
64
Filter functions are available from all Azure Boards tools: Work items, Boards, Backlogs, Sprint Backlogs and Taskboards, Queries, and Delivery Plans. The set of features supported depends on the tool and Azure DevOps version. *(Use the content selector to view the filters available for your version.)*
54
65
55
66
The following table indicates the supported options based on the tool indicated with a ✔️ or is listed.
@@ -58,7 +69,6 @@ Backlogs and boards are subject to filters defined for the team as described in
58
69
59
70
::: moniker-end
60
71
61
-
62
72
::: moniker range=">= tfs-2017 <= tfs-2018"
63
73
64
74
Filter functions are available from all Azure Boards tools: Boards, Backlogs, Sprint Backlogs, Taskboards, and Queries. The set of features supported depends on the tool and Azure DevOps version. *(Use the content selector to view the filters available for your version.)*
@@ -77,7 +87,7 @@ Supported options are indicated with a ✔️ or listed.
77
87
<br/>**Tool**
78
88
:::column-end:::
79
89
:::column span="1":::
80
-
**Keywords**<br/>or **ID**
90
+
**Keywords**or **ID**
81
91
:::column-end:::
82
92
:::column span="2":::
83
93
<br/>**Fields**
@@ -137,7 +147,7 @@ Supported options are indicated with a ✔️ or listed.
137
147
:::row-end:::
138
148
---
139
149
::: moniker-end
140
-
::: moniker range=">= tfs-2017"
150
+
::: moniker range=">= tfs-2018"
141
151
:::row:::
142
152
:::column span="1.5":::
143
153
[**Backlogs**](backlogs-overview.md)
@@ -160,7 +170,31 @@ Supported options are indicated with a ✔️ or listed.
@@ -801,12 +810,17 @@ Once you set the filter options for a specific view, your settings persist until
801
810
- To filter using fields, first add the field as a column or to the card. For example, to filter by **Assign To**, **Iteration Path**, or **Work Item Type**—or the contents of any other field—add those fields to show on the cards, backlog, plan, or list.
802
811
803
812
To add columns or fields, see the following articles:
813
+
::: moniker-end
814
+
::: moniker range=">= azure-devops-2020"
804
815
- For Backlogs and Queries, see [Change column options](set-column-options.md)
805
816
- For Boards, see [Customize cards](../boards/customize-cards.md)
806
817
- For Taskboards, see [Customize a sprint Taskboard](../sprints/customize-taskboard.md)
807
818
- For Plans, see [Review team delivery plans](../plans/review-team-plans.md).
> To report a bug, a user must have at a minimum, **Stakeholder** access and **Edit work items in this node** permission set to **Allow** for the **Area Path** where they will add the bug. To learn more, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md)
38
+
34
39
## Bug work item type
35
40
36
41
The following image shows the Bug work item type for the Scrum process. The Bug work item type for Agile and CMMI processes tracks similar information. It's designed to appear on the product backlog along with requirements or on the Taskboard along with tasks.
@@ -50,16 +55,18 @@ The following image shows the Bug work item type for the Scrum process. The Bug
50
55
51
56
::: moniker-end
52
57
58
+
59
+
53
60
::: moniker range=">= tfs-2017"
54
61
> [!TIP]
55
62
> Use the [Discussion section](../work-items/work-item-form-controls.md#discussion) to add and review comments made about the work being performed to resolve the bug.
56
63
::: moniker-end
57
64
65
+
58
66
## Fields specific to bugs
59
67
60
68
The Bug work item type uses some bug-specific fields. Use the fields described in the following table to capture both the initial issue and ongoing discoveries. For information about fields specific to the CMMI process Bug, see [Bugs, issues, and risks field reference](../work-items/guidance/cmmi/guidance-bugs-issues-risks-field-reference-cmmi.md). For information about all other fields, see [Work item field index](../work-items/guidance/work-item-field.md).
Copy file name to clipboardexpand all lines: docs/boards/includes/prerequisites-work-items.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.date: 09/07/2021
14
14
* You must connect to a project. If you don't have a project yet, [create one](../get-started/sign-up-invite-teammates.md).
15
15
* You must be added to a project as a member of the **Contributors** or **Project Administrators** security group. To get added, [Add users to a project or team](../../organizations/security/add-users-team-project.md).
16
16
* To view or modify work items, you must have your **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set. To learn more, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md).
17
-
* To add new tags to add to work items, you must have **Basic** access or higher and have the project-level **Create new tag definition** permissions set to **Allow**. By default, the **Contributors** group has this permission set. Even if the permission is explicitly set for a **Stakeholder**, they won't have permission to add new tags, as they are prohibited through their access level.
17
+
* To add new tags to add to work items, you must have **Basic** access or higher and have the project-level **Create new tag definition** permissions set to **Allow**. By default, the **Contributors** group has this permission set. Even if the permission is explicitly set for a **Stakeholder**, they won't have permission to add new tags, as they are prohibited through their access level. To learn more, see [Stakeholder access quick reference](../../organizations/security/stakeholder-access.md).
18
18
19
19
20
20
::: moniker-end
@@ -24,6 +24,6 @@ ms.date: 09/07/2021
24
24
* You must connect to a project. If you don't have a project yet, [create one](../../organizations/projects/create-project.md).
25
25
* You must be added to a project as a member of the **Contributors** or **Project Administrators** security group. To get added, [Add users to a project or team](../../organizations/security/add-users-team-project.md).
26
26
* To view or modify work items, you must have your **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set. To learn more, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md).
27
-
* To add new tags to add to work items, you must have **Basic** access or higher and have the project-level **Create new tag definition** permissions set to **Allow**. By default, the **Contributors** group has this permission set. Even if the permission is explicitly set for a **Stakeholder**, they won't have permission to add new tags, as they are prohibited through their access level.
27
+
* To add new tags to add to work items, you must have **Basic** access or higher and have the project-level **Create new tag definition** permissions set to **Allow**. By default, the **Contributors** group has this permission set. Even if the permission is explicitly set for a **Stakeholder**, they won't have permission to add new tags, as they are prohibited through their access level. To learn more, see [Stakeholder access quick reference](../../organizations/security/stakeholder-access.md).
0 commit comments