> 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/views.md).

# Views

## Kanban

The Kanban view allows you to see issues laid out in a grid. Pylon's standard Kanban view organizes issues by status.&#x20;

* Drag an issue between columns to change its status
* Change the assignee directly from the kanban view by clicking on the assignee avatar
* Greyed out cards indicate issues that have already been viewed by your user
* Cards with a red dot indicate new activity since you last viewed an issue

<figure><img src="/files/w706aHMHGRCqYNadtmQg" alt=""><figcaption></figcaption></figure>

## List

The List view allows you to view issues in a list with columns.

* Customize the columns that are visible in the list view
* Change the assignee directly from the list view by clicking on the assignee avatar
* Greyed out rows indicate issues that have already been viewed
* Rows with a red dot indicate new activity since you last view that issue

<figure><img src="/files/pEK0O63c3XW9ozvwLNm0" alt=""><figcaption></figcaption></figure>

## Filters

Select filters to apply to narrow down the set of visible issues. Issues can be filtered by a variety of default fields across issues, accounts, or contacts as well as any custom fields you've created. By default, filters are AND'ed together, meaning only issues meeting all specified filters conditions will appear.

Filters can also be combined in advanced ways using Filter Groups. With Filter Groups, different groupings of filter conditions can be combined with AND or OR operators.

<figure><img src="/files/hLxCTb0JWqLSNlmIA4ng" alt=""><figcaption></figcaption></figure>

## Layouts

Use the layout menu to change the structure of your view. You can customize:

* View type: Kanban or List
* Columns: For Kanban, the vertical dimension you want issues to be displayed by. For List, the data properites that are visible.
* Grouping: For Kanban, a second dimension to visualize issues by. For List, the primary dimension you want to view issues by
* Sort by: The order issues appear in within each group
* Show unreads only: Only display unread messages
* Timestamp: Pick what timestamp you want displayed on the cards.
* Preview: Choose whether the first message, last message, or AI title is displayed on cards.

<figure><img src="/files/X38XwrjRIMTJzkg3imSK" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="/files/xM8YYhNx6sRZSuCVwkrY" alt=""><figcaption><p>Example of a Kanban layout with Issue Status as the Column and Priority as the Grouping</p></figcaption></figure>


---

# 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.usepylon.com/pylon-docs/support-workflows/issues/views.md?ask=<question>&goal=<endgoal>
```

`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.
