> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/support-workflows/issues/bulk-actions.md).
# Bulk actions
Take bulk actions to manage issues
Select multiple issues in the Kanban or List view to take bulk actions on them. Issues can be selected using the checkbox on the top right of the card in Kanban or on the left of the row in List view.
Then take action on all these issues at once using the action bar at the bottom of the page.
To select every issue in a Kanban column or group, click **Select all** in its header. In List view, use the checkbox in the header row.
Actions include:
* Change status
* Set assignee
* Set team
* Set tags
* Edit field: set a custom field on every selected issue. For multi-select fields, you choose how the values are applied.
* Change customer portal visibility
* Follow and Unfollow
* Snooze
* Bulk reply
* Group issues (see [Issue Groups](/pylon-docs/support-workflows/issues/issue-groups.md))
* Merge issues (see Merge and split issues)
* Mark Spam: deletes the selected email issues and blocks their senders (see [Email](/pylon-docs/support-workflows/email.md#block-from-an-issue))
* Delete
In Kanban, you can also drag selected cards to another column together to change their status.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.usepylon.com/pylon-docs/support-workflows/issues/bulk-actions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
