Issue grouping and sorting are in Display. Open filters from the funnel button; team scope choices are beside the collection controls on wide screens and on their own row on narrow screens. When the breadcrumb runs out of room, open its ellipsis menu to see parent pages. Open team Views from the sidebar.
Choose a layout
Lists support dense scanning and bulk operations; boards make status distribution easier to see. Changing layout does not copy issues. Project directories also support a roadmap, while issue timelines use independent start and due dates.
Use the current page’s layout and display controls to choose visible attributes. Customer counts and releases may be hidden by default. Showing an attribute does not edit issues, and changing layout does not expand access to private teams or projects.
Apply filters
Start with status, assignee or project. Add labels, cycles, customers, milestones or releases when needed. Advanced filters support nested AND/OR conditions. “Any”, “all” and “none” are different operations; inspect the result before saving.
Customer filters use customer identity, not display names. Release filters use current target releases, not historical publication snapshots. Unknown or failed metadata is different from an explicitly empty association. An empty-looking error state is not evidence that no issues exist.
Save and share
- Set filters and layout on a page that supports saved views.
- Choose the save-view action, give it a useful name and confirm its personal or shared scope.
- Reopen it to check filters and display preferences. Before editing a shared view, consider the teammates using it.
On a phone, open Views in the issue toolbar and choose Save current as view. In the project directory, open Save view for Save as view. If you changed a view you created, the same menu offers Save view changes. To keep changes to someone else’s shared view, save your own copy.
A saved view stores a query and presentation settings, not a copy of its result. Results change as work changes. Every read still checks current workspace and team access. Deleting a view does not delete the issues it showed.
Team issues and the view directory
Team Issues offers All issues, Active issues and Backlog. Active includes the Unstarted and Started workflow categories; Backlog includes every custom status in the Backlog category. Additional filters narrow that range. Clearing filters keeps the selected section. All issues excludes Triage by default and still includes completed and canceled issues.
Switching between All, Active and Backlog within a team keeps your search and returns the list to the top. Each section remembers its own filters, sorting and display settings. Headers, search and section controls remain available while the body loads. Browser back and forward restore the section or saved view in the address.
Saving a view from Active or Backlog includes its workflow-category constraint. Opening a saved view uses its saved conditions without adding the previously selected section.
Use team Views to browse issue or project views and search by name. To create a view, choose its type, configure filters and layout on the corresponding page, then save its name and visibility. The directory shows your personal views and shared views you can read. Only the creator can rename, overwrite or delete a view; other members can copy it into a personal view.
Team project views always remain within the current team, including after clearing filters. Existing workspace project views keep their original scope; filtering one by team does not attach it to that team. Sharing a view never grants private-team access. Project views do not offer issue-notification subscriptions.
Subscriptions and troubleshooting
Where view subscriptions are available, subscribe to issues newly entering the view. This is not a notification for every field change and does not replay events from before the subscription. Merely crossing midnight does not manufacture a new-entry event.
If an issue is missing, clear search and filters, then check workspace, team access and view scope. Name recurring team views by purpose, such as “Ready for review this week”, rather than “View 1”.
Loading and retry
An unavailable or failed saved view offers retry or clear-view actions instead of showing another scope’s results. Creating tasks and saving views are unavailable until the requested saved view is confirmed, so they cannot use old filters. Results wait for directories required by the current filters or grouping. If loading another page encounters a temporary read failure, verified records remain visible and you can retry at the bottom. Losing access still hides the affected content.