makeplane / makeplane/plane

🚀 Feature: Auto-cascade status from a parent issue to its sub-issues on close

Open
#9,432 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Is there an existing issue for this?
  • I have searched the existing issues
Summary

Plane currently has no way to automatically update sub-issue statuses when a parent issue is closed. When a parent work item is moved to a Completed or Cancelled state, its sub-issues stay as-is and must be closed one by one.

Proposal

An optional, per-project automation: when a parent issue enters a Completed or Cancelled state, its non-terminal sub-issues are automatically moved to the same resolution — recursively through the sub-issue tree.

  • Direction: parent → children (v1). The reverse (all sub-issues done → parent auto-completes) would be a fast-follow, mirroring Linear's two independent toggles.
  • Opt-in via a project Automations toggle (default off), consistent with the existing Auto-archive / Auto-close automations.
  • Cancelled parent → sub-issues cancelled; Completed parent → sub-issues completed. Already-closed sub-issues are left untouched (idempotent).
Motivation

Common in hierarchical planning (epic → story → task): closing the parent should be able to close the tree. Linear ships this as "Auto-close parent and sub-issues"; related requests already exist here (e.g. #3137, #8512).

Are you willing to submit a PR?
  • Yes, I'm willing to submit a PR for this feature.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by locating the existing Auto-archive and Auto-close automations and the project Automations toggle, then trace parent/sub-issue status transitions and terminal-state handling. Done means the opt-in behavior recursively applies the matching Completed or Cancelled status while leaving terminal sub-issues unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
django, python, react, typescript
Domain
backend, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.