Sanplex provides an Execution Kanban feature, which significantly enhances the visualization of project management workflows. Within the Execution Kanban, you can access the Comprehensive, Story, Bug, and Task boards. All items displayed on these boards are directly associated with the current execution:

• Stories: Linked from the Execution > Story list.
• Bugs: Linked from the Execution > Test > Bug list.
• Tasks: Linked from the Execution > Task list.

How do developers use the Execution Kanban in Sanplex? Check out the video explanation:

【视频介绍】

The Kanban board provides an intuitive view of the status and progress of stories, bugs, and tasks under an execution, greatly enhancing the visibility of the project management process.

图1

I. Comprehensive Kanban

The Comprehensive Kanban lists all the boards. Below, we will take the Comprehensive Kanban as an example to introduce the common functions of Kanban.

1. Creating Stories, Bugs, and Tasks in Kanban

There is a Create button in the top-right corner of the Kanban.

• Under the execution Kanban, you can: Create stories, batch create stories, link stories, and link stories by plan. These are the same functions as creating stories, batch creating, linking, and linking by plan under Execution > Story.
• Create bugs and batch create bugs. These are the same functions as creating bugs under Execution > Test > Bug.
• Create tasks and batch create tasks. These are the same functions as creating tasks and batch creating tasks under Execution > Task.

Stories, bugs, and tasks created in the Kanban will be synchronously displayed in the story, bug, and task lists of the execution.

Stories will also be synchronously displayed in the story lists of the project and product associated with the execution; bugs will be synchronously displayed in the bug lists of the project and product associated with the execution.

图2

In the first column of the Story Kanban, Backlog, there is also an Add button on the right side.

You can create stories, batch create stories, link stories, and link stories by plan.

After a successful addition, they will be displayed directly in the Backlog column.

图3

In the first column of the Bug Kanban, Unconfirmed, an Add button is also displayed on the right side.

Click it to create bugs or batch create bugs.

图4

In the first column of the Task Kanban, Not Started, an Add button is also displayed on the right side. You can create tasks or batch create tasks.

图5

2. Printing and Full-Screen Kanban

Click the More button in the top-right corner of the Kanban to set the Kanban, print the Kanban, and display the Kanban in full screen.

图6

2.1 Kanban Settings

You can set the column width and swimlane height.

图7

2.2 Printing Kanban

Kanban can be printed according to either "All Content" or "Incremental Content."

The content includes stories, bugs, and tasks in the Kanban. The printed story, bug, and task cards can be pasted onto the physical Kanban board we use, which is very convenient. Printing "All Content" is suitable for the first time, and printing "Incremental Content" is suitable for subsequent times.

图8

Before printing, you can set the status of stories, bugs, and tasks according to the actual situation.

图9

2.3 Full-Screen Kanban

Click the Full Screen button to enter the full-screen view of the Kanban content.

This provides a more intuitive way to view stories, bugs, and tasks. It is also suitable for execution team meetings to review the development status and progress together; it also allows execution managers and project managers to view specific progress.

Press the Esc key on the keyboard to exit full screen.

图10

3. Setting the Number of Objects per Row

Our Kanban columns display one story, bug, or task per row by default. When there is a large number of stories, bugs, or tasks in an execution, we can set the number of objects displayed in one row. A maximum of 4 stories, bugs, or tasks can be displayed in one row.

Default display of one piece of data:

图11

The quantity can be changed through the plus and minus signs. This is the display when 2 objects are shown:

图12

When 4 objects are displayed, since the width is limited, only the avatar of the person assigned to the story, bug, or task is shown.

图13

4. Setting Kanban Columns and WIP Limits

You can edit and modify the name and color of Kanban columns, as well as the name and color of Kanban sub-columns.

You can set the Work in Progress (WIP) limit not only for the parent columns but also for the sub-columns.

Our default WIP limit is "Infinite" (no limit), which can be modified according to actual needs.

图14

When setting the WIP limit for sub-columns, please note that the sum of the WIP limits of the sub-columns cannot exceed the WIP limit of the parent column.

图15

If the WIP limit of the sub-columns exceeds the WIP limit of the parent column, a prompt will be given.

图16

4.1 Editing Names

Click the Edit Name option in the More menu on the right side of the Kanban column to enter the page for modifying the column name and color.

图17

After a successful modification, the column name and color will be displayed as the modified values.

图18

4.2 Setting WIP Limits

Click the WIP Settings option in the More menu on the right side of the Kanban column to enter the WIP limit setting page. Change it from "No Limit" to "5".

图19

After a successful setting, the WIP limit changes from "No Limit" to "5".

图20

5. Importing and Exporting Tasks

Exporting tasks to CSV format is supported. Importing tasks supports "Transfer Tasks" and "Import Bug." Conditions for transferring tasks:

• The source execution has expired or is closed;
• The current account has permission to access the previous execution;
• The previous execution has unfinished tasks (only unfinished tasks can be imported);
• The task status is one of the following: Not Started, In Progress, Paused, or Canceled;
• Sub-tasks cannot be imported;
• Executions must be associated with the same product;
• If a task is linked to a story, the new execution must also be linked to the product where the story is located (if it is a multi-platform/branch product, the new execution must also be linked to the specific platform/branch).

"Import Bug" supports bugs in the "Active" status under the product associated with the execution. Bugs are converted into tasks for development and management. The progress of a task sourced from a bug can display the resolution progress of the bug in real-time.

图21

6. Assigning Stories, Bugs, and Tasks in Kanban

Stories, bugs, and tasks can be assigned directly on the Kanban board. Unassigned items display a unique "unassigned" avatar.

图22

Click the unassigned icon to enter the assignment pop-up page for the assignment operation:

图23

After a successful assignment, the avatar of the current assignee is displayed.

图24

II. Story Kanban

You can also view the Story Kanban separately by switching through the dropdown component in the top-left corner. Viewing the Story Kanban separately provides multiple grouping views: Default, Priority, Category, Module, Source, and Assignee. In the Story Kanban, the Developing and Testing columns are calculated based on the status of the related development and testing tasks. Other columns allow for direct drag-and-drop movement of stories.

图25

III. Bug Kanban

You can also view the Bug Kanban separately by switching through the dropdown component in the top-left corner.

Viewing the Bug Kanban separately provides multiple grouping views: Default, Priority, Severity, Module, Type, and Assignee.

图26

Bug cards can be dragged to other columns. They can only be dragged from Unconfirmed to columns on the right; cards in columns on the right cannot be dragged back to columns on the left.

图27

IV. Task Kanban

You can also view the Task Kanban separately by switching through the dropdown component in the top-left corner.

Viewing the Task Kanban separately provides multiple grouping views: Default, Priority, Type, Module, Story, and Assignee.

图28

Task cards can similarly be dragged from left columns to right columns.

When dragging a task from the Not Started column to the Developing sub-column under the Development column, it will trigger the task start pop-up page, just like starting a task in the execution task list.

Fill in the consumed hours if any; if not, leave it blank. Click Start, and it will be displayed in the Developing column.

Status prompts during dragging will show a yellow border on the target column:

图29

After releasing the mouse, the pop-up displays the task start page:

图30

After clicking Start, the task is displayed in the Developing column:

图31