Loading request...
Enable assigning multiple users to a single issue. All assignees should see the issue on their Kanban and "My Issues", receive notifications, and any status change should reflect for all. Current subscriber functionality lacks accountability and visibility in assignee-scoped views.
@linear feature requests: - Multiple assignees for issues. Some issues have multiple responsible parties but aren't sub-issueable. All assignees should see the same issue on their Kanban and in "My Issues", get the same notifications, and when any of them moves it (to "Done", "In Progress", etc.), it moves for everyone. Today, you can fake it with subscribers, but they don't carry accountability and don't appear in assignee-scoped views. - Finer-grained permissions within a team/project. Right now, it's basically "member or admin". We want to whitelist who can perform sensitive actions: move issues into specific statuses (e.g., "Dropped", "Released", "Won't Do"), add/remove specific labels, close milestones, etc. These permissions should be scoped to a team or project and enforced in the UI and the API (otherwise, automations just route around them). Today, the best we can do is write bots that post warning comments after the fact, which is reactive and noisy instead of actually preventing the action.