Views

Beta

Views save useful filters and table layouts for Issues, Features, and Initiatives. Team Views and workspace Views use the same directory, create flow, table controls, and detail drawer; the sharing destination is the important difference.

Where Feature views appear

Feature views belong to the surface where you create them. They are not copied between surfaces.

A main Features view does not appear in workspace Views. A workspace or Team Feature view does not become a main-table tab. An Initiative Feature view appears only beside that Initiative's detail tabs.

On an Initiative, Add view is available beside Overview, Activity, and Features. It opens the Initiative Features table and starts a new temporary view. Cancel removes that temporary view and returns to the Feature view that was active before creation; when no saved view was active, that source is All Features. Saving selects the new Initiative-only tab.

The temporary view uses the same editor as the main Features table. You can choose its color, edit its name and description, and see the temporary tab identity update before saving. Switching to another view and returning restores those unsaved metadata choices from your local draft. The saved view still belongs only to that Initiative.

The Initiative Overview Display menu can reset your local changes or, for workspace members, Set default for everyone. That default affects only that Initiative's Overview and is separate from both the main Features default and the Initiative Features-tab default.

Feature Issue views

Open a Feature and choose Issues for every accessible Issue linked to it. Saved Issue views appear beside Overview, Activity, and Issues, and belong only to that Feature. They do not appear in Team Views, workspace Views, another Feature, or other Issue tables.

The built-in Issues view has one shared default for that Feature. Changing filters, grouping, ordering, or Display marks the Display control with a dot. Open Display to Reset to default or, when you can edit the Feature, Set default for everyone. Publishing changes only the table layout for that Feature; Issues still means every linked Issue you can access.

Add view is available beside the Feature's Overview, Activity, and Issues tabs. It opens the existing Issue view editor on the Issues table. Cancel removes the temporary view and returns to the Issue view that was active before creation; when no saved view was active, that source is Issues. Saving selects the new Feature-only tab. Copied links preserve tab=issues&view={id} for an accessible saved view and omit temporary creation state.

The Feature owns which Issues can appear. A saved view can refine filters, grouping, ordering, and display properties, but it cannot add Issues from another Feature or reveal Issues from a private Team you cannot access. If a copied view link is deleted, archived, inaccessible, or belongs to another context, Integrity falls back to Issues without revealing that view's details.

Feature Issue drafts are private to your browser and isolated by user, workspace, Feature, and selected view. A clean built-in Issues view adopts a newly published default automatically. If the built-in default or a saved view changes while your draft is dirty, Integrity keeps your whole draft and offers the appropriate Reset, publish/overwrite, or Save-as-new path.

Workspace Views

Open Views from the workspace navigation to see:

• Personal views that only you can access.
• Workspace views shared with workspace members.

Choose Issues, Features, or Initiatives, then select Create a new view. Workspace create defaults to Personal and offers only Personal or Workspace. It cannot save to a Team.

Team Views

Open Views inside a Team to see that Team's Issue, Feature, and Initiative views. Team create always saves to the current Team. It cannot create Personal or Workspace views directly.

Team scope is part of the view, not an optional filter. A Team view always shows that Team's associated work. To publish one existing Team view elsewhere, right-click it and choose Move to, then select Personal or Workspace. The move keeps the view and its Favorite but removes the Team scope, so the view appears in workspace Views instead of the Team directory. Use Copy to... when you want a separate view or another Team destination.

Moving a Team Issue view also removes its saved-view subscription because those notifications are available only while the view belongs to a Team.

What a view saves

Depending on the family, a view can save filters, display properties, grouping, ordering, and supported presentation settings such as Feature List, Board, or Timeline controls. Metadata includes the name, description, and color.

Issue views can save Phase filters, grouping, and display properties. A copied Feature Phase URL opens a contextual Phase predicate on the owning Feature's Issues table; that URL-owned overlay remains separate from ordinary saved/local filters until you explicitly promote it. Feature Timeline views can save whether Phase markers are shown without creating a separate Phase view family.

Unsaved table changes remain private in the current browser until you save. Drafts are isolated by workspace, user, family, and their main-table, Initiative Overview, Initiative Features, workspace-directory, or Team context.

When a shared view changes elsewhere, a clean open view updates automatically. If you have unsaved changes, Integrity keeps your complete draft and shows that the view or default was updated elsewhere. You can reset to the newest shared version, overwrite it intentionally, or create a new view; background updates never partially mix into your draft.

View details

Open a saved view to use its table and the right-side detail drawer. The drawer has the same three sections for every family:

1. View identity and actions.
2. Visibility and owner.
3. A summary of the currently visible filtered rows.

Summary tabs are:

• Issues: Assignees, Labels, Features, Teams.
• Features: Leads, Labels, Initiatives, Teams.
• Initiatives: Owners, Labels, Features, Teams.

The summary changes with the table's visible filtered rows. Counts are not saved into the view.

The Views directory shows the canonical Personal, Workspace, or Team icon beside each Scope. Updated dates use the same compact date presentation as the Feature table. Scope and Updated remain in the secondary columns on the right side of the directory, with their labels and values aligned left for scanning.

Favorite, copy, edit, and overflow actions appear in the same locations across Team and workspace Views. Right-click an active Personal or Workspace row to edit it, duplicate it, copy it to another destination, add or remove its Favorite, copy its link, or archive it. Move to remains disabled there. The Copy to submenu uses the same destination layout as Move to but creates an independent view; select multiple rows when you want to copy several views together. A mixed Personal, Workspace, or Team selection can still be archived, restored, or recolored when you have permission for every selected view. Copy and exact-duplicate cleanup remain available only when the selected views share one source destination. Team row actions expose both Move to and Copy to when the corresponding source and destination permissions allow them. Favorites and copied links follow the same saved view after a move; actions that a view family or scope does not support are disabled or omitted.

The ellipsis beside the Favorite star on a selected view repeats the same actions and grouping as its row menu. Issue views also provide Export issues as CSV, which downloads the currently visible filtered issues; unavailable or restricted issues are not added back to the export.

Source Library views

Modules and artefact-table source views keep their Source Library ownership and routes. They use related saved-view behavior but do not appear in the Team/workspace Views directory.

Related