Issue Identifiers And Privacy
Understand projected Issue keys, Team identifier aliases, and private Team redaction.
Issue keys are projected from two durable values:
{currentTeamIdentifier}-{teamIssueNumber}The Team owns the identifier prefix. The Issue owns the Team-scoped number. Integrity does not store the full current key as the canonical Issue identity.
Team-scoped numbers
Each Team has its own Issue counter. Different Teams can both have 1, so QA-1 and SEC-1 can both exist in the same workspace.
Issue numbers are allocated by the server. Clients never choose the final number.
Team identifier changes
When a Team identifier changes, Issue rows are not mass-updated. New reads render the current Team identifier with the existing Issue number.
Old keys continue to resolve through Team identifier aliases. If you can access the Issue, an old key route redirects to the current key.
Issue detail URLs use the current projected Issue key, such as /workspace/{workspace-url}/issues/QA-1. Copy URL copies the current readable Issue URL when the Issue is visible to you. Hidden or unavailable Issues do not expose a copyable URL.
Private Teams
Private Team Issues are hidden from non-members unless the Issue is explicitly shared with them.
Direct-shared private Issues show the shared Issue title and primary document read-only without exposing private Team details. Direct-share-only viewers do not receive the private Team name, slug, identifier, Team route, or projected private key prefix in the rendered detail view.
Sharing an Issue does not grant access to the private Team, Team settings, Team member list, or Team Issue list.
Mutation boundary
Issue detail edits are enforced on the server. Updating title, primary document content, status, priority, assignee, primary Feature, labels, or icon color requires Issue edit access plus the owning Team visibility or membership boundary. Direct-share-only access is read-only in this slice, even when future share-management vocabulary includes editor grants. Archived and recoverably deleted Issue documents are also read-only; permanently deleted documents expose no content.
Direct-shared non-Team users may see selected display-safe Issue properties on the shared Issue. They cannot enumerate the private Team's full status list, Team labels, assignable roster, or Feature candidates unless they also have the required Team access.