Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Tutorial: Working with Views (List, Board, Gantt)

Create a view, switch between List/Board/Gantt, and save configurations teams can reuse.

Overview

Views shape how lists and boards are reviewed.

This tutorial creates one view, then switches view types.

Key Concepts

  • View type: List, Board, or Gantt presentation

  • Save View: stored configuration for reuse

  • Visibility: private or shared view access

How It’s Used

Use this tutorial when starting a new Project.

Use it again when standardizing weekly review views.

Benefits

  • Faster reviews with repeatable layouts

  • Cleaner governance through shared views

  • Less rework caused by inconsistent filters and columns

Setup Steps

1

Open the view selector

  1. Open the Project.

  2. Navigate to an area with views, such as Tasks.

  3. Select the current view name.

Screenshot placeholder: view selector dropdown showing existing views.

2

Create a new view

  1. Select New view.

  2. Enter a view name aligned to intent.

  3. Select Create.

Screenshot placeholder: new view dialog with name field.

3

Choose a view type

Select a view type based on the workflow.

Use List for scanning and editing fields quickly.

Next: Creating and Customizing List Views

Use Board for status-based workflow and drag-and-drop updates.

Next: Creating and Customizing Board Views

Use Gantt for timeline planning and dependency visibility.

Next: Creating and Customizing Gantt Charts

4

Customize filters and layout

  1. Add one filter, such as Status != Complete.

  2. Adjust one layout setting, such as columns or grouping.

  3. Confirm the list reflects the intent.

GIF placeholder: apply a filter, then reorder columns, then clear the filter.

5

Save and share

  1. Select Save view (or Save as).

  2. Set visibility to Team for shared standards.

  3. Keep personal variations as Private.

Screenshot placeholder: visibility options in the view share modal.

Best Practices

  • Keep shared views minimal and stable.

  • Duplicate a view before major changes.

  • Use consistent prefixes, such as Team — and Me —.

Summary

Next actions:

Last updated