Beta: Private issue sharing⁠

Overview

Access to Linear issues is managed at the team level by default—a user in a private team has access to all issues in that team, and a user who is not a member of that team has no visibility.

This works well for the vast majority of cases but there are some workflows that require access to a very limited set of issues. Consider a private Security team sharing a vulnerability with specific developers—or an HR team that needs a manager to fulfill a sensitive task.

To address these and similar scenarios, we’ve added support for sharing individual issues directly.

Sharing an issue⁠

Share an issue on a private team through the ⌘/Ctrl + K menu, or by selecting the Share action in an issue’s overflow menu.

Issues can be shared with workspace members who are not part of the team.

When an issue is shared, a banner at the top of the issue indicates whom it’s shared with. People with permission to share issues in the team can share or stop sharing an issue.

Access can be removed from the issue’s Share menu. If access comes from a shared parent issue, that inherited access may need to be disabled on the child issue first.

Interacting with shared issues⁠

When an issue is shared with you, it appears in My issues under the Shared tab. You can view and update the issue and any of its sub-issues on the same team, but you can’t change team- or planning-related fields such as the team, project, cycle, or milestone, and you can’t share the issue with others.

See Private teams for more on team privacy and sharing rules.

Users in the private team can filter for all shared issues, or issues shared with a particular user.

Sub-issues⁠

When you share a parent issue, you’re also sharing its sub-issues. Because of this:

• If a sub-issue is in a different team than its parent, the parent issue can’t be shared.
• You’ll be warned if you try to make another issue a sub-issue of a shared issue, to help prevent accidental oversharing.