> For the complete documentation index, see [llms.txt](https://docs.fabricplan.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fabricplan.com/powertable-sheets/how-tos/layout-views-summary/kanban/add-and-manage-tasks.md). # Add and manage tasks This article explains the ways in which you can add and manage tasks within the Kanban layout. {% hint style="warning" icon="file-exclamation" %} ### Important After you add, edit, duplicate, delete, or move tasks between stacks, select **Save to Database** to save your changes to the database. Use **Discard Changes** if you want to discard all the changes you made. Select **Preview Changes** to preview all changes you made. You can select the ones you want to discard and save the remaining to the database. {% endhint %} ### View tasks Each Kanban card displays the task title and the assigned user. Cards are organized into stacks based on the selected **Stack by** field.

You can: * Scroll vertically to view more tasks within a stack. * Select **Load More Tasks** to add more stacks to the display for your viewing.

* See the number of tasks in each stack from the count displayed next to the stack header. * Scroll horizontally to view more Kanban stacks or workflow stages. ### Add a task To add a new task: 1. Select **Add Task** on the toolbar. The form editor opens.

2. Enter the task details in the form editor.

3. Select **Apply**. The new task is added to the appropriate Kanban stack based on the entered **Stage**. 4. Select **Save to Database** to update the database table. Alternatively, select the **+** icon on the required stage stack to add a new task in that stack.

{% hint style="info" %} ### Note Use [**Customize Form**](/powertable-sheets/how-tos/generate-forms.md#customize-form) in the form editor to customize the form. {% endhint %} ### Edit a task To edit a task, follow these steps: 1. Select the vertical ellipsis on the required task card, and then select **Edit**. The form editor opens.

2. Update the required fields in the form editor. 3. Select **Apply** to save the changes. 4. Then, select **Save to Database** to update the changes in the database table. {% hint style="success" icon="lightbulb" %} ### Tip You can also open the **Form Editor** for a task card by simply selecting anywhere on the card and then starting to edit the task details. {% endhint %} ### View history View the audit trail of changes made to a specific task using the **History** tab. To view task history: 1. Select a task in the Kanban layout. 2. In the **Record Details** side panel, select the **History** tab. The following image shows the **History** tab for a recently added task, displaying the changes recorded for the task.

3. The **History** tab displays operations performed on the task record, including: * The task that was inserted or modified. * The field that was modified. * The previous and updated values. * The user who made the change. * The date and time of the change. The image below shows the updates made to an existing task along with all these details.

4. Use the **History** tab to review task updates and track changes throughout the task lifecycle. 5. Within the tab, you can: * Use **Search** to find specific history entries. * Use **Filter** to filter the history and display specific changes based on action type (Insert, Update, or Delete), who made the change, when the change occurred, or who approved the change (if approvals are enabled). * Use [**Export**](/powertable-sheets/how-tos/basic-table-operations/edit-and-bulk-edit-data.md#export-history) to export the available history records. * Use **Audit logs** to review changes made to the task in detail. For more information, see [Audit logs](/powertable-sheets/how-tos/audit-log.md). ### Move stacks You can rearrange stacks using drag and drop. Drag a stack to the required position to rearrange the stacks.

### Move tasks between stacks You can rearrange task cards within a stack or between stacks. * Drag and drop a task card within a stack to reposition the task visually. * Drag a task card from one stack to another to update its **Stage**. After drag-and-drop, select **Save to Database** to update the changes in the database. For example, when work begins, drag a task from **To Do** to **In Progress**. The task's **Stage** is automatically updated to **In Progress**.

Alternatively, select the vertical ellipsis on a task card and use **Move To** to move it to another stage.

### Duplicate a task To duplicate a task, select the vertical ellipsis on the task card and then select **Duplicate**.

PowerTable duplicates the selected task and opens the form editor. You can edit the details you want in the form editor and select **Apply** to save changes. ### Delete a task To delete a task, select the vertical ellipsis on the task card and then select **Delete**. Alternatively, right-click on the card and select **Delete**.

{% hint style="info" %} ### Note The [**Manage Access**](/powertable-sheets/how-tos/set-up-row-and-column-access-control.md#delete) menu controls the user's delete access. If **Delete** is disabled, select **Manage Access** to update the delete access settings. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.fabricplan.com/powertable-sheets/how-tos/layout-views-summary/kanban/add-and-manage-tasks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.