Assign and Delegate Issues

Issue assignment gives each Team-owned Issue one accountable human owner. The assignee is the person currently responsible for driving the work, even when a future agent may help with part of the task.

Assign an Issue

You can assign an Issue from the Issue table row or from Issue detail.

The assignee picker only lists users the server allows for the Issue's workspace and owning Team. Private Team Issues can only be assigned to eligible users for that Team context, and direct-share-only readers cannot assign or reassign Issues.

Changing the assignee updates the current Issue row and writes assignment history. No history row is written for a no-op change.

My Issues

Open My Issues from the workspace sidebar. It sits with Team Issues and uses the same Issue table controls.

My Issues currently has five personal scopes:

Assigned, Created, Shared, Subscribed, and Activity keep separate local table preferences for filters, grouping, ordering, and visible properties. This lets you tune each view without changing the other.

My Issues reads through workspace-level aggregate readers instead of loading every Team list in the browser. Private Team rows stay hidden unless you have Team access or an active direct share, and direct-shared private rows use display-safe Team and key information. The Activity scope refreshes through private per-user realtime wake-ups when visible Issue activity changes.

Issue Subscriptions

Issue subscriptions are for Inbox delivery, not access. A notification never grants permission to an Issue.

Integrity automatically subscribes the Issue creator and the current assignee when an Issue is created. When the assignee changes, the newly assigned user is subscribed if they can view the Issue; clearing or changing the assignee does not remove earlier subscriptions.

Activity participation can also subscribe people. A top-level comment that mentions a user subscribes that user to the Issue, and reply mentions or replies subscribe the relevant users to the thread. Users can also subscribe or unsubscribe from Issue Activity manually.

Issue-level subscriptions receive internal Integrity Inbox notifications for meaningful Issue activity such as comments, replies, mentions, and visible property/lifecycle changes. Thread subscriptions stay scoped to that comment thread. Reactions do not create notifications, and actors are not notified about their own action.

Assignment History

Issue detail shows assignment history in the activity area. History can include:

Cleanup history avoids private Team names, slugs, identifiers, hierarchy, and projected private Issue keys for viewers who should not see them.

Delegation Boundary

Delegation is not active yet. The Issue detail property surface can show that delegation is unavailable, but it does not launch an agent session, create an agent assignment, or replace the human assignee.

Future delegation will stay separate from Assignee: the human remains accountable, while agent work will need its own permissioned delegation contract.

Related