Issues

Issues are Team-owned work items inside a workspace. They give Teams a durable place to capture operational work while Integrity keeps requirements, artefacts, reviews, baselines, and lifecycle evidence in their existing product surfaces.

Every Issue belongs to one active Team, receives a Team-scoped number, and displays a key such as QA-42. The Team owns the key prefix, while the Issue owns the number, title, primary collaborative document, status, priority, assignee, primary Feature link, labels, and icon color.

What ships now

• Full-page Issue creation from the workspace create action.
• Team-context Issue creation from a Team Issues page.
• Team-scoped Issue numbers and projected keys.
• Old key resolution when a Team identifier changes.
• Team Issue lists with All issues, Active, and Backlog scopes.
• Shared Team Issue saved views, contextual view shortcuts, and a dedicated Team Views directory.
• Team archive pages with Archived Issues and Deleted Issues.
• Issue detail pages with an editable title, shared rich Description document, status, priority, assignee, Feature, labels, and created activity.
• Feature-linked Phase assignment across create, detail, table, command, bulk, filter, grouping, and saved-view surfaces.
• Issue Activity with comments, threaded replies, resolved threads, reactions, subscriptions, and property/lifecycle activity.
• Issue saved-view subscriptions for Issues added to a saved view or completed/canceled while in that view.
• Same-Team Issue relations for related, blocked-by, and blocking work, including blocked Backlog display, relation badges, relation filters, and create-related flows.
• Same-Team parent/sub-issue hierarchies with inline child creation, parent changes, direct-child progress, hierarchy filters, and recoverable cascade delete/restore choices.
• My Issues with Assigned, Created, Subscribed, Activity, and conditional Shared personal Issue scopes.
• Assignment history for assignment, reassignment, unassignment, and private-Team cleanup events.
• Cross-Team Issue moves with previewed key/status/label translation, old-key redirects, and continuous history.
• Workspace and Team Issue label settings with groups, colors, active/archive states, and workspace-wide default labels.
• Public/private Team visibility and direct-share read behavior, including archived/deleted share suspension.
• Team Issue Cycles with Team-owned schedules, Issue assignment, shared Cycle views, rollover, progress, capacity guidance, and calendar feeds.
• Recurring Issues with Team-local daily, weekly, monthly, or yearly schedules, immutable versions, safe retry/recovery, and ordinary generated-Issue history.

Team Issues pages

Team Issue pages live at:

/workspace/{workspaceId}/teams/{teamSlug}/issues

The page shows the current Issues for the selected Team. Rows use the same operational table grammar as other workspace object lists: the object cell contains the Issue icon, key, and title, while property columns can show status, assignee, priority, Feature, and labels. Document content is never loaded into Issue tables, filters, groups, ordering, or previews.

When you open a workspace from the root route, Integrity lands on Team Issues with Active selected by default. Use All issues and Backlog when you need a broader or queued view.

Local table controls support filtering, display properties, ordering, grouping, and sub-grouping for the shipped Issue properties. Each built-in All issues, Active, and Backlog tab has an independent Team default. After changing a tab, the dot on Display options marks the local draft; use Reset to default to discard it or Set default for everyone when your Team permissions allow publication.

When a filtered Team Issue list should remain available without replacing a built-in default, save it as a shared Team Issue view. Saved views appear as contextual shortcuts under Team Issues and can be opened directly with a ?view= URL.

Issue row and label-setting selection uses the same shared workspace-object selection surface as Features, Initiatives, Modules, Folders, and Artefacts. Selection is session-only, supports visible-range Shift-click, and clears or prunes when the table scope changes. The Actions panel only shows commands backed by existing Issue or label mutations; unsupported future commands are not shown.

Team Views

Team Views lives under the Team navigation:

/workspace/{workspaceId}/teams/{teamSlug}/views

The directory has Issues, Features, and Initiatives tabs. It lists only views saved to the current Team. Built-in Issue scopes such as All issues, Active, and Backlog stay under Team Issues and do not appear in the saved-view directory.

Use Team Views to create, open, copy, duplicate, archive, transfer ownership where supported, and manage Issue saved-view subscriptions when your Team permissions allow it. Team create always saves to the current Team. A Team can have active/backlog Issues and still show an empty Team Views directory until someone creates a view.

Workspace Views separately lists your Personal views and Workspace-shared views. Those views cannot retain a hidden Team destination. Both routes use the same directory, table framing, and three-card detail drawer. Issue summaries show Assignees, Labels, Features, and Teams from the currently visible filtered Issues.

Issue detail

Issue detail pages live at:

/workspace/{workspaceId}/issues/{issueKey}

The detail page shows the Issue title, collapsible rich Description document, Resources row, Activity feed, and a right-side properties drawer. Resources can hold supporting links, private attachments, and collaborative Documents that inherit Issue and Team access. Title, document content, status, priority, assignee, Feature, Feature Phase, labels, icon color, and permitted Resource actions are editable for users who have Issue edit access and the required Team access. Document edits use private collaboration updates and do not create Issue Activity or notifications.

Issue Activity includes comments, replies, reactions, thread state, assignment changes, title/property changes, lifecycle changes, subscription changes, and Team moves. Delegation is intentionally disabled until Integrity has a stable agent runtime and installed-agent access contract.

Who can change an Issue

Issue actions follow the owning Team's current permissions, not simple visibility. An active Team member can do normal Issue work—create Issues, edit properties, comment, manage relationships, and use available lifecycle actions—when Integrity shows the corresponding action. Team owners and workspace admins or owners retain the stricter permanent-delete action for eligible deleted Issues.

A public Team page, a readable Issue link, or a direct share does not grant edit access. Direct-share-only private Issue access is read-only and keeps private Team context redacted. Archived and deleted Issues disable normal edits and only expose lifecycle actions allowed for their current state. If membership or Team policy changes while an Issue is open, Integrity removes stale actions as the canonical permission view refreshes; the server still rechecks every mutation.

For multi-select actions, every selected Issue must be editable, active, and compatible. One read-only or inaccessible row disables the whole command instead of silently updating only part of the selection.

My Issues

My Issues is a workspace-level Issue table for work connected to you:

/workspace/{workspaceId}/my-issues

Use Assigned for active Issues currently assigned to you, Created for active Issues you created, and Subscribed for active Issues you follow. Shared appears when at least one active private Issue is shared directly with you. Activity shows active Issues connected to recent comments, reactions, subscriptions, direct shares, assignment, or creation, ordered by the latest shared Activity update. Private direct-share rows keep display-safe keys and Team context so you can open the Issue without exposing private Team details in the table.

Related