diff --git a/doc/user/project/img/issue_board_status_lists_v18_2.png b/doc/user/project/img/issue_board_status_lists_v18_2.png new file mode 100644 index 0000000000000000000000000000000000000000..186e1a3be37a2d098dd2b3fe540cfbc5c857fca1 Binary files /dev/null and b/doc/user/project/img/issue_board_status_lists_v18_2.png differ diff --git a/doc/user/project/issue_board.md b/doc/user/project/issue_board.md index d9382ce03e102780e11692e3e6006b5223e5dfbc..9e0d3b85364b09310c73673693956c9f1d3e1489 100644 --- a/doc/user/project/issue_board.md +++ b/doc/user/project/issue_board.md @@ -31,7 +31,7 @@ Issue boards: - Visualize workload and progress across your entire process. Your issues appear as cards in vertical lists, organized by their assigned -[labels](labels.md), [milestones](#milestone-lists), [iterations](#iteration-lists), or [assignees](#assignee-lists). +[labels](labels.md), [milestones](#milestone-lists), [iterations](#iteration-lists), [assignees](#assignee-lists) or [status](#status-lists). Add metadata to your issues, then create the corresponding list for your existing issues. When you're ready, you can drag your issue cards from one list to another. @@ -168,6 +168,7 @@ that belong to it. Types of lists include: - [**Assignee list**](#assignee-lists): all open issues assigned to a user. - [**Milestone list**](#milestone-lists): all open issues for a milestone. - [**Iteration list**](#iteration-lists): all open issues for an iteration. +- [**Status list**](#status-lists): all issues having a status. A **Card** is a box on a list, and it represents an issue. You can drag cards from one list to another to change their label, assignee, or milestone. The information you can see on a @@ -306,9 +307,7 @@ To add a milestone list: 1. In the dropdown list, select a milestone. 1. Select **Add to board**. -Like the assignee lists, you're able to [drag issues](#move-issues-and-lists) -to and from a milestone list to manipulate the milestone of the dragged issues. -As in other list types, select the trash icon to remove a list. +To change the milestone of issues, [drag issue cards](#move-issues-and-lists) to and from a milestone list. ![Milestone lists](img/issue_board_milestone_lists_v17_1.png) @@ -334,11 +333,60 @@ To add an iteration list: 1. In the dropdown list, select an iteration. 1. Select **Add to board**. -Like the milestone lists, you're able to [drag issues](#move-issues-and-lists) -to and from a iteration list to manipulate the iteration of the dragged issues. +To change the iteration of issues, [drag issue cards](#move-issues-and-lists) to and from an iteration list. ![Iteration lists](img/issue_board_iteration_lists_v17_1.png) +### Status lists + +{{< details >}} + +- Tier: Premium, Ultimate +- Offering: GitLab.com, GitLab Self-Managed + +{{< /details >}} + +{{< history >}} + +- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/543862) in GitLab 18.2 [with a flag](../../administration/feature_flags/_index.md) named `work_item_status_feature_flag`. Disabled by default. + +{{< /history >}} + +{{< alert type="flag" >}} + +The availability of this feature is controlled by a feature flag. +For more information, see the history. +This feature is available for testing, but not ready for production use. + +{{< /alert >}} + +Create lists of issues that have a specific status. +Status lists help you organize issues by their workflow stage, such as **In progress** or **Done**. + +For more information about status, see [Status](../work_items/status.md). + +Status lists behave differently from other list types: + +- **Status lists**: Can include both open and closed issues, depending on whether the status maps to an open or closed state. +- **Other lists** (like assignee or milestone): Always show only open issues. + +Prerequisites: + +- You must have at least the Planner role for the project. + +To add a status list: + +1. Select **New list**. +1. Select **Status**. +1. From the dropdown list, select the status. +1. Select **Add to board**. + +The status list is added to the board and displays issues with that status. + +To change the status of issues, [drag issue cards](#move-issues-and-lists) to and from a status list. + +![Status list](img/issue_board_status_lists_v18_2.png) + ### Group issues in swimlanes {{< details >}} @@ -533,7 +581,7 @@ To create a new list between two lists: ![creating a new list between two lists in an issue board](img/issue_board_add_list_between_lists_v17_6.png) -1. Choose the label, user, milestone, or iteration to base the new list on. +1. Choose the label, user, milestone, iteration, or status to base the new list on. 1. Select **Add to board**. The new list is inserted in the same position on the board as the new list panel. @@ -610,6 +658,7 @@ You can filter by the following: - Release - Type (issue/incident) - [Weight](issues/issue_weight.md) +- [Status](../work_items/status.md) #### Filtering issues in a group board @@ -702,6 +751,8 @@ A few things to remember: - Selecting the issue title inside a card takes you to that issue. - Selecting a label inside a card quickly filters the entire issue board and show only the issues from all lists that have that label. +- When an issue is moved from a status list to an open list, the default open status is applied. + Similarly, when it's moved to a closed list, the default closed status is applied. - For performance and visibility reasons, each list shows the first 20 issues by default. If you have more than 20 issues, start scrolling down and the next 20 appear. diff --git a/doc/user/project/issues/managing_issues.md b/doc/user/project/issues/managing_issues.md index 8d114b77705f8e23c50a935848538ed6607a785e..7539efbf0017e9d9f141046321b5d8a1b7ea0634 100644 --- a/doc/user/project/issues/managing_issues.md +++ b/doc/user/project/issues/managing_issues.md @@ -114,7 +114,8 @@ To edit multiple issues at the same time: When bulk editing issues in a project, you can edit the following attributes: -- Status (open or closed) +- [Status](../../work_items/status.md) +- State (open or closed) - [Assignees](managing_issues.md#assignees) - [Epic](../../group/epics/_index.md) - [Milestone](../milestones/_index.md) @@ -156,6 +157,7 @@ To edit multiple issues at the same time: When bulk editing issues in a group, you can edit the following attributes: +- [Status](../../work_items/status.md) - [Epic](../../group/epics/_index.md) - [Milestone](../milestones/_index.md) - [Iteration](../../group/iterations/_index.md) @@ -959,6 +961,63 @@ until the issue is reopened. You can also set and clear health statuses using the `/health_status` and `/clear_health_status` [quick actions](../quick_actions.md#issues-merge-requests-and-epics). +## Status + +{{< details >}} + +- Tier: Premium, Ultimate +- Offering: GitLab.com, GitLab Self-Managed + +{{< /details >}} + +{{< history >}} + +- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/543862) in GitLab 18.2 [with a flag](../../../administration/feature_flags/_index.md) named `work_item_status_feature_flag`. Disabled by default. + +{{< /history >}} + +{{< alert type="flag" >}} + +The availability of this feature is controlled by a feature flag. +For more information, see the history. +This feature is available for testing, but not ready for production use. + +{{< /alert >}} + + + + +You can assign a status to issues to track their progress through your workflow. +Status provides more granular tracking than the basic open/closed states, so you can use specific +stages like **In progress**, **Done**, or **Won't do**. + +For more information about status, including how to configure custom statuses, see [Status](../../work_items/status.md). + + + +### Change status + +Prerequisites: + +- You must have at least the Planner role for the project, be the author of the issue, or be assigned to the issue. + +To change the status of an issue: + +1. On the left sidebar, select **Search or go to** and find your project. +1. Select **Plan > Issues**, then select your issue to view it. +1. On the right sidebar, in the **Status** section, select **Edit**. +1. From the dropdown list, select the status. + +The issue's status updates immediately. + +You can view the issue's status in: + +- The **Issues** page +- An epic's **Child items** section +- Cards on issue boards + +You can also set the status by using the `/status` [quick action](../quick_actions.md#issues-merge-requests-and-epics). + ## Publish an issue {{< details >}} diff --git a/doc/user/project/quick_actions.md b/doc/user/project/quick_actions.md index caa0637db05e2187dc04be3319df22aa6f84e7bc..f5c1dae25fd2c94d439dc0ef2981628e5ebd8247 100644 --- a/doc/user/project/quick_actions.md +++ b/doc/user/project/quick_actions.md @@ -128,6 +128,7 @@ To auto-format this table, use the VS Code Markdown Table formatter: `https://do | `/severity ` | {{< icon name="check-circle" >}} Yes | {{< icon name="dotted-circle" >}} No | {{< icon name="dotted-circle" >}} No | Set the severity. Issue type must be `Incident`. Options for `` are `S1` ... `S4`, `critical`, `high`, `medium`, `low`, `unknown`. | | `/shrug` | {{< icon name="check-circle" >}} Yes | {{< icon name="check-circle" >}} Yes | {{< icon name="check-circle" >}} Yes | Add `¯\＿(ツ)＿/¯`. | | `/spend