> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/transformations/task-views-and-organization.md).

# Task Views and Organization

### Overview

Task views keep execution tracking readable at scale. Save Views prevent repeated filter rebuilds.

{% hint style="info" %}
Screenshot placeholder: Tasks area showing List/Board/Gantt options and a “Save View” control.
{% endhint %}

### Key Concepts

* **View type**: List, Board, or Gantt
* **Filter**: rule that narrows the dataset
* **Grouping**: bucket rows by a field such as Status or Owner
* **Save View**: stored view configuration for repeatable reviews

### How It’s Used

Use Save Views for daily triage and weekly delivery reviews. Use separate views for execution, leadership reporting, and readiness.

### Benefits

* Faster standups and execution reviews
* Cleaner reporting through stable filters and columns
* Reduced confusion from inconsistent ad hoc views

### Setup Steps

#### Common view patterns

Use these patterns as starting points:

* **Current teammate tasks**: `Assignee = Current Teammate`
* **By status**: group by Status
* **Overdue**: Due date before today and Status not Complete
* **This week**: Due date within 7 days
* **By workstream**: group by Process or System (when configured)

#### Create a Save View

{% stepper %}
{% step %}

### Open Tasks

1. Open a Project.
2. Go to **Tasks**.
3. Pick a view type (List, Board, Gantt).
   {% endstep %}

{% step %}

### Configure the view

Typical controls include:

* Filters (which tasks appear)
* Sort (how tasks order)
* Group (how tasks bucket)
* Columns/fields (what you see)

{% hint style="info" %}
Screenshot placeholder: filter panel and grouping controls.
{% endhint %}
{% endstep %}

{% step %}

### Save and share

1. Click **Save View** (or **Save as**).
2. Name it using a clear pattern.
   * For example: `Tasks — This week (Assignee = Current Teammate)`
3. Share the Save View with the team (if supported).
   {% endstep %}
   {% endstepper %}

### Best Practices

* Use short, scannable view names.
* Prefer 3–6 filters max.
* Keep one owner field.
* Avoid “multiple owners” in one task.
* Hide low-signal columns. Add them only when needed.

#### Troubleshooting

<details>

<summary>Task is missing from a view</summary>

Check:

* Filters (Assignee, Status, Process/System)
* Date ranges (Due date set, time zone differences)
* Archived items (when archive is enabled)

Quick fix: clear filters, then re-add filters one by one.

</details>

<details>

<summary>Save View cannot be created or shared</summary>

Possible causes:

* Missing edit permission for views.
* The Project is read-only.

Ask a Project Admin to update access level.

</details>

### Summary

Task views provide repeatable execution tracking.

Save Views reduce filter rebuild and improve consistency.

Related:

* [Create and Assign Tasks](/transformations/create-and-assign-tasks.md)
* [Creating and Customizing List Views](/getting-started/creating-and-customizing-list-views.md)
* [Creating and Customizing Board Views](/getting-started/creating-and-customizing-board-views.md)
* [Creating and Customizing Gantt Charts](/getting-started/creating-and-customizing-gantt-charts.md)
* [Filtering and Sorting Data](/getting-started/filtering-and-sorting-data.md)


---

# 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://help.transform.ai/transformations/task-views-and-organization.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.