ci: flip an epic to In Progress on any started sub-issue #362

Merged
manlycucumber merged 1 commit from fix/rollup-any-progress into develop 2026-07-02 05:52:02 +00:00
manlycucumber commented 2026-07-02 05:50:56 +00:00 (Migrated from github.com)

What

The board rollup only promoted an epic to In Progress once one of its sub-issues was completed (closed). An epic with active-but-unmerged work therefore sat in Todo — the opposite of the goal ("show In Progress as soon as we begin work on one").

Verifying the newly-added PROJECTS_PAT surfaced this: the first authenticated rollup reverted Epic #38 from In Progress back to Todo, because #38's children are underway but none are closed yet.

Change

Treat an epic as In Progress when any sub-issue has started — i.e. is closed OR has an open linked PR — by reading each epic's subIssues in the GraphQL query and checking them. Individual-issue and closed→Done behaviour is unchanged.

Refs #360.

## What The board rollup only promoted an **epic** to *In Progress* once one of its sub-issues was **completed (closed)**. An epic with active-but-unmerged work therefore sat in *Todo* — the opposite of the goal ("show In Progress as soon as we begin work on one"). Verifying the newly-added `PROJECTS_PAT` surfaced this: the first authenticated rollup reverted Epic #38 from *In Progress* back to *Todo*, because #38's children are underway but none are closed yet. ## Change Treat an epic as *In Progress* when **any** sub-issue has *started* — i.e. is **closed** OR has an **open linked PR** — by reading each epic's `subIssues` in the GraphQL query and checking them. Individual-issue and closed→Done behaviour is unchanged. Refs #360.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Directorium/Core!362
No description provided.