Skip to the article

Views and filters

Save a filtered view of accessible work, share it read-only and revoke public access when needed.

A view saves how you filter and display issues without copying or changing them. Configure the view for your work first; sharing an eligible project view is a separate step that gives visitors read-only access to the published content.

Save a view of your work

Start from a project board or a personal cross-project issue surface. Use its filters, sort and display controls to choose the work you need. Check the scope before saving: a personal view and a project view do not represent the same access boundary.

Filter on supported properties such as status, assignee, priority, categories or objective. Sort the result to make the next action clear. In kanban, issues remain grouped by status; changing a view does not edit their status or assignment. Without a status filter of its own, a board shows only Backlog, Todo, In progress and In review. Select Done or Canceled in the Status filter to show those columns; a view keeps the status filter you save with it.

Save the view with a name describing its purpose, then select it again in the view bar at the top of the board (a menu on a narrow screen) and verify its filters. Edit or remove it when its purpose changes. Delete view asks for confirmation, and a board always keeps at least one view of its own. For publication permissions and revocation, see sharing a view.

Filter by issue properties or choose a sort order. The AI field is optional for these manual controls.

Empty or unexpected results

Check every filter, the active project and your membership when expected issues are absent. Clear restrictive filters before assuming data was deleted. After editing an issue, it can legitimately leave a filtered view. Search its identifier, or select Done and Canceled in the Status filter of an otherwise unfiltered project board, to inspect the saved values.

A saved view is not a copy of its issues. Deleting the view removes that view configuration, while deleting selected issues changes the underlying project work.

Share and revoke a read-only view

Open the view menu on an eligible project board and choose Share view. You need to be the owner or a Member; readers keep their personal views but cannot share views. A personal view within the project can be shared only by its own user. Global cross-project views cannot be shared. Review its filters and visible content before publication. Choose a public secret link or password protection where offered; passwords require at least eight characters. Copy the generated link only after the sharing change succeeds.

Open the link in a separate browser session without your account. Inspect the issue subset, fields and any linked content a visitor can see. A public link grants the view's read-only access rather than membership or edit permission in the project.

Shared cards expose their titles, descriptions and displayed properties, including assignee names, categories, objective names, due dates, recurrence and any remote forge links. The projection excludes implementation-plan bodies and member email addresses. Parent and relation chips can show identifiers of project issues outside the view filter. Review those descriptions, names and identifiers as well as the visible columns; hiding a card property is not a general content-redaction tool.

Private, password-protected and public access are distinct choices. This capture keeps the view private.

Revoke and verify

Return to the view's share controls and make it private to revoke publication, then confirm with Stop sharing. Sharing again creates a new link. Open the old link anonymously again to check that access is denied. Revocation cannot recall copies or screenshots a visitor already saved.

Secret view links use the private-link publication path and remain noindex. That indexing policy limits search-engine discovery but is not a password. Keep the link private if its contents are sensitive, and use password protection when appropriate. Do not confuse a user's shared view with the indexed official documentation.

If the anonymous result differs from your expectation, inspect the saved view and sharing configuration before forwarding its link. Verify the scope again after changing filters or linked content.

Related articles