Manage work views with AI

Ask Integrity AI or your connected coding agent to make an Issue view for a specific destination. You can use Personal or Workspace Views, a Team's Issues, or the Issues tab of a Project or Meeting Minute. You need the same permission to create or manage that view as you would in the product.

Start with a proposal

For example, ask: “Show me the available labels for the Integrity Team, then propose a view of high-priority PBA Issues grouped by assignee.” The agent can discover the available choices without asking you to create an empty view. It shows the proposed settings and the number of Issues matching them.

Review the destination, filters, grouping and count, then explicitly ask the agent to save the view. Its result includes a link to the saved view. You can open it in Integrity and use the same filters and display settings there. Issue views currently use the List layout.

Project views

You can also propose and save Project views in Personal, Workspace or Team Views, the main Projects page, or an Initiative's Projects list. For example: “Propose a Team Project view grouped by priority, keep closed Projects hidden, and show health and target dates.” The agent discovers the choices available in that destination and reports the number of matching Projects.

Project views preserve their List, Board and Timeline settings, including hidden groups and group order. They also keep the Readiness filter (Ready or Blocked), ordering by Readiness, Board columns grouped by Readiness, and Flow's Show related switch. For example: “Save a Workspace view of Ready Projects as a Flow with related links shown.” A view you save in Integrity with these options opens for the agent with the same settings, and a view the agent saves opens the same way for you. Flow supports multiple Initiatives, labels, or an unfiltered Project collection. Dependency Step grouping still requires one Initiative and List. The agent can read a view, change a supported setting, or duplicate it while retaining its other saved settings. Your unsaved browser changes stay local; the agent works with the saved configuration.

Ask “Explain the blockers in my saved V1 Flow”. The agent reads the saved filters and the same dependency graph as the page, including readable prerequisites outside those filters. Each Project appears once, with links, Initiative context, dependency sources and Readiness. Readiness is the same result the page shows: Ready for a Planned Project with no open blocker, Blocked for a Planned Project with one, and none for the rest. Large graphs arrive in pages with exact totals; the agent can continue reading them. If the graph changes between pages, it starts a fresh read. An unavailable or restricted graph is reported as unavailable, rather than an empty graph. Reading and explaining a Flow does not change its dependencies.

An AI answer can cite up to 24 objects. If an answer or graph exceeds its evidence budget, ask about a smaller part of the Flow. Saved answers become unavailable when your access to their supporting objects changes.

Shared Project defaults belong to the main Projects page or an Initiative's Overview and Projects list. Changing one requires confirmation. The Overview has a shared default, while its named saved views belong to the Projects list. The main Projects default sets shared display controls; a named view keeps its own filters.

People and Team filters support up to 24 selected options per filter. A repeated completed request returns its original result, including when the source view has since been archived. Current access is checked again before returning it.

Initiative views

Initiative views live in Personal, Workspace or Team Views. For example: “Propose a Workspace view of Planned Initiatives grouped by health, owned by me or without an owner, ordered by target date.” Each view starts from the Active, Planned or Completed scope and keeps its filters, grouping, ordering, hidden or reordered groups and display properties. Initiative views use the List layout. The reported count includes every Initiative that matches, counting each Initiative once.

The main Initiatives page has shared Active, Planned and Completed defaults. A default sets shared display settings only: grouping, ordering, empty groups and display properties. Filters belong to a named view. Changing a default requires confirmation and Workspace admin permission.

Meeting Minute views

Meeting Minute views live in Personal, Workspace or Team Meeting Minutes. For example: “Propose a Workspace view of meetings in Review, grouped by status, newest meeting first.” A view keeps its search text, status and scope filters, grouping, ordering and display properties. Team views cover only that Team's meetings, so they have no scope filter. The reported count matches the Meeting Minutes table.

Choosing a saved view as your default is separate from changing the shared All meetings layout. Your Personal default needs no confirmation. Making a Workspace or Team view the default for everyone, or changing the shared All meetings layout, requires confirmation and the matching permission. A Personal destination has no shared default.

Saved Meeting Minute views also appear under Meeting Minutes in your Workspace and Team Views. Opening one takes you to its Meeting Minutes page.

Browse and find views

Ask the agent to list the views in a destination, such as “Show the Initiative views in the Platform Team”. It can browse every view you can open without search text, page through long lists, or search view titles when you name one. Each listed view includes the same link as the Views directory, so you can open it directly. To pick a Team, the agent lists your Teams and checks where you can create views.

Change an existing view

Ask the agent to read a named view before changing it. For example: “Read my PBA view, keep its settings, and duplicate it with the CO label instead.” Specify whether you want to edit the original or create a separate copy. Editing keeps the view's identity; duplicating keeps the source intact.

If another person changes the view first, the agent must read its current settings and prepare the change again. If an agent changes a view while you have unsaved changes open, Integrity keeps your changes and shows View updated elsewhere. Choose Reset to latest to adopt the saved version, or Overwrite changes to replace it with yours. If a saved filter refers to something you can no longer access, the agent cannot safely replace that hidden setting. It reports the limitation without revealing the inaccessible object.

Archive and shared defaults

Archiving a saved view requires explicit confirmation. In Integrity AI, review the proposed action and choose Apply to confirm it or Cancel to leave the view active. A connected coding agent must likewise obtain your confirmation before applying the proposal. Preparing the action alone does not archive anything. Archived views remain recoverable through Integrity's existing view lifecycle controls.

Changing a shared built-in Issue default also requires confirmation. Team defaults distinguish All issues, Active and Backlog. Project and Meeting Minute Issues use their own All issues default. Saving a separate named view does not change a built-in default. The same applies to the shared All meetings Meeting Minute default.

Filters and counts always follow your current access. The agent returns paged option lists, so it may retrieve further pages while locating a label, assignee or other choice. It cannot permanently delete a view through these actions.

Issue views support an SLA filter with Breached, High risk, Medium risk, Low risk, Achieved, Failed and No SLA. Select more than one to include any of those states. Saved views keep these choices. Agents can also search a Team's active Issues by the same SLA states and return an exact count of the Issues you can access. Risk changes as the deadline approaches; completed Issues keep their recorded result.