Skip to content

🚀 Feature: Restrict a member to managing only their own issues #10172

Open

Description

@noralane

Is there an existing issue for this?

  • I have searched the existing issues

Summary

Please add an option to restrict a member so they can create issues and manage only issues they created, but cannot edit or delete other members' issues.

Why should this be worked on?

Members should be restricted to managing their own issues without changing other members' issues.

Activity

  1. changed the title [-]Restrict a member to managing only their own issues[/-] [+]🚀 Feature: Restrict a member to managing only their own issues[/+] on Nov 2, 2026
  2. AnshSable commented on Nov 3, 2026

    @AnshSable

    Hi! I'd be interested in contributing to this feature.

    I'm exploring Plane's existing workspace/project permission architecture and would like to understand how this restriction should interact with the current member roles.

    A few things I'd like to clarify before proposing an implementation:

    1. Should this restriction apply only to regular members, or should admins and guests be configurable too?
    2. Should ownership-based restrictions cover all issue modifications, including status, priority, assignee and labels?
    3. Should this be configurable at the workspace level or project level?

    I'd be happy to investigate the existing authorization flow and propose a minimal implementation that preserves current permission behavior.

    Is anyone already working on this feature?

  3. noralane commented on Nov 3, 2026

    @noralane
    Author

    Thanks for offering to help. For this use case, I'd suggest a project-level restriction for regular members; admins keep their existing permissions. Restricted members can create issues and manage all fields of their own issues, but cannot modify or delete anyone else's.

    I don't see anyone assigned yet, but the Plane maintainers should confirm contribution plans.

  4. AnshSable commented on Nov 3, 2026

    @AnshSable

    Thanks for clarifying! That makes the expected behavior much clearer.

    I'll investigate Plane's existing project-level permission and issue authorization flow to understand how this can fit into the current architecture.

    I'll also check the relevant API endpoints and test coverage before proposing an implementation.

    I'll wait for maintainer confirmation before starting any code changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions