Create and share saved views

You will learn how to save a query, choose the right surface, share it with the workspace, and maintain it over time.

Before you begin, read Filter query language.

1. Start from a useful query

You can create a saved view from:

Command search.
A project issue surface with active filters.
An existing saved view with Save as new.

Good saved views answer a recurring question, such as:

assigned_to:me hide_done:1
project:tixi label:customer-request
project:web|api status:in_progress
created_at:this_week estimated:false

From a filter bar, choose the view action and select Save as new.

From an existing saved view, open the view menu and choose Save as new, Edit filters, or View settings.

The modal is titled New view when creating and Edit view when updating.

3. Name the view

Enter a Name that describes the decision or audience.

Good examples:

My open work.
Customer requests.
Unestimated backlog.
Launch readiness.
This week's bugs.

Avoid vague names such as Important or Stuff.

4. Choose an icon

Pick an icon that makes the view recognizable in the sidebar.

Icons are optional context; the name should still make sense without the icon.

5. Write or review the query

Use the Query field for filter syntax.

The query editor supports:

Filter-key autocomplete.
Value autocomplete for projects, members, statuses, cycles, milestones, and labels when catalogs are available.
Syntax help.
Warnings for tokens that will be treated as plain text.
Preview count and preview issues.

If a query uses status, cycle, or project-specific labels, include project: so Tixio can validate the values.

6. Choose visibility

Choose:

Private for personal queues.
Shared for workspace-wide views.

Use shared views when a team, support rotation, planning meeting, or stakeholder group should return to the same queue.

Private: any workspace member can create private saved views.
Shared: workspace owners, admins, and members can create shared saved views.
Project viewers and guests are read-only collaborators inside a project. They can still create private saved views for personal queues, but cannot create or promote shared workspace views. See Workspaces, projects and members for the full role model.

Who can use shared views

Any workspace member who can access the workspace can open shared saved views, including project viewers and guests. The issues returned by a shared view still respect each person's project access.

7. Choose Order By

Choose Order By for the default sort.

Common choices:

Modified (latest → earliest) for active queues.
Priority (high → low) for triage.
Due date (closest → latest) for deadline review.
Created (latest → earliest) for intake.
Manual when the surface supports manual or rank-based ordering.

8. Choose a surface

Choose the surface that best matches the work:

List for scanning and opening issues.
Table for many fields, columns, and bulk updates.
Board for status-flow review.
Calendar for date review.
Timeline for schedule shape.

List, calendar, and timeline need one project context. Board and table can also open cross-project views.

9. Understand cross-project behavior

Cross-project board views group issues by shared status category. They are read-only because each project can have different status columns. Click an issue to edit it in its project.

Cross-project table views support editable table workflows, column show/hide/reorder, saved per-view layout, sorting, and bulk actions when the selected issues can be updated together.

Use cross-project views for workspace queues such as:

assigned_to:me hide_done:1
label:customer-request
project:web|api status:in_progress

10. Save and open the view

Select Create view or Save.

If the query can deep-link to a project surface, Tixio opens that surface with the saved view active. If the query is cross-project or cannot resolve one project, Tixio opens the flat saved-view page or the workspace board/table surface.

11. Edit an existing view

Open the view menu and use:

Edit filters to update the query inline.
Save as new to clone the view.
View settings to change name, icon, visibility, order, query, or surface.
Delete to remove the view.

Only view owners can edit settings or delete a saved view, including changing visibility to Shared. Other workspace members can open shared views and use Save as new.

12. Keep views healthy

Review shared views occasionally:

Remove views nobody uses.
Rename views when the audience changes.
Update stale status keys, project references, or labels.
Split overloaded views into focused queues.
Keep private views private unless the team needs them.