Skip to content

fix(dashboard): fold dropped milestones into one row on the conductor mode Board - #39201

Merged
KiroCrewCaptain merged 2 commits into
mainfrom
crew/slack/board-fold-dropped
Nov 21, 2026
Merged

KiroCrewCaptain merged 2 commits into
mainfrom
crew/slack/board-fold-dropped

Conversation

@buluoray

@buluoray buluoray commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: On the conductor mode Board, dropped milestones fold into one "N dropped" row below the open ones, so the live work stays on screen when the conductor changes course.

A user reported a run where the conductor changed course and dropped about 40 milestones. The Board's Status view folds done milestones into one "N done" row, but each dropped one stays as a full "Not done · dropped" row among the live ones. The Board became unusable and the user restarted the session to get a clean one.

Why it matters

The Board is where the owner checks what is running and what needs them. A long goal that changes plan collects many dropped milestones, and each one looks like work that has to be read and skipped. The goal board Dashboard page already folds abandoned tasks (#38300); the Board tab should match.

Not a goal

  • No change to the milestone count in the header, the Recap sentence or the run line: dropped milestones still count in the total.
  • No fold for a rejected milestone ("Not done · failed its check"): it stays in the open list, as on the goal board.
  • No change to the List view or to any other page.

What changed (motivation → approach → change)

Dropped milestones were never split out of the open list: the Status view folded only done rows, and everything else, closed ones included, was drawn as a row.

ConductorModeCrewPanel.tsx now takes the milestones closed as abandoned out of that list and draws them under one <details> row, "N dropped", below the open rows. The row is folded by default and opens to the same milestone rows as before. It works the same way as the existing "N done" fold. With no dropped milestone there is no row.

The new label conductor_mode_ms_dropped_fold is added in all twelve languages under website/src/i18n/locales/ (en.manual.json and the eleven translations, plus the regenerated en-XA.json). docs/system-specs/modules/crew-mode.md says how the fold behaves.

Backwards compatibility

Compatible: the panel reads the same board fields; only where dropped rows are drawn changes.

Reader: website/src/pages/chat/command-center/ConductorModeCrewPanel.tsx:ConductorModeCrewPanel -- crew page -- dropped rows are hidden behind one click, not removed; Milestones: dropped milestones fold into one "N dropped" row below the open ones checks they are all inside the fold

Tests

  • CrewWorkerList.test.tsx › Milestones: dropped milestones fold into one "N dropped" row below the open ones: two dropped milestones sit in a folded "2 dropped" row, the running and the rejected one stay in the open list above it, and the header still counts all four. It failed on main (no fold row) and passes with the fix. Turning the fold back into the open list makes it fail again.
  • CrewWorkerList.test.tsx › Milestones: the dropped fold opens on its own, and drops its top rule when only the done fold sits above it: toggling the dropped fold leaves the done fold closed, and the dropped fold has no top rule when no open row separates the two folds. Forcing the rule back on makes it fail.
  • npx vitest run src/pages/chat/command-center/ src/i18n/: all pass (247 and 1288 tests).

Proof: not provable -- frontend test (prove.py runs Python only)

Manual verification

tsc, eslint on the changed files, i18n:check against main and semgrep on the diff all pass.

Real-machine verification

N/A -- a dashboard rendering change; the component test drives the real panel.

Screenshots / video

Component render, not the live page. These come from website/capture/shoot-conductor-mode-dropped-fold.mjs, which mounts the real ConductorModeCrewPanel with mocked board data at side-panel width. To retake them: cd website && node capture/shoot-conductor-mode-dropped-fold.mjs.

Dark Light
Open list, dropped fold closed Open list with 2 dropped folded, dark Open list with 2 dropped folded, light
Dropped fold opened Dropped fold open, dark Dropped fold open, light
Only abandoned left: one divider between the folds Done fold above dropped fold, dark Done fold above dropped fold, light

Before (main): every row from the dropped fold sat in the open list, mixed in creation order with the running and failed rows.

Related Issues

Closes #39192

Sibling sweep

Swept: git grep -n "abandoned" -- website/src/pages/chat/command-center/ src/kiro_crew/dashboard_templates/builtin/goal-board/
Sibling: src/kiro_crew/dashboard_templates/builtin/goal-board/template.html -- not affected -- abandoned tasks already fold there since #38300
Sibling: website/src/pages/chat/command-center/ConductorModeCrewPanel.tsx -- changed here

Pattern harvest

Not generalizable: one list on one panel that folded one closed state and not the other.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@buluoray
buluoray requested review from a team and KiroCrewCaptain as code owners November 18, 2026 19:11
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Nov 18, 2026
@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 48dec1b239b25a23de259f7ff3cbafe1b28800c1 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing blocks: it is the same fold the done rows already use, it is reversible, and the screenshots committed in this revision show it.

Notes

  • The spec used to say an abandoned milestone "stays among the open rows", and this PR rewrites that line. No docs/decisions/ entry records it, so this PR can change it. Still, the PR body should say outright that it reverses what the spec described.

[DESIGN-REVIEWED] 48dec1b

Description read

[DESCRIPTION-READ] 03dd9d4f69daa28df65bf37eace588d79528cc6f5a3fb0e8316501a9367e83c6

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ PASS

UX-level review of 48dec1b239b25a23de259f7ff3cbafe1b28800c1 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

UX-Verdict: PASS

Nothing blocks. The blind reader identified the new "N dropped" fold in both its folded and opened states, said what a click does and would use it. The fold is the same expander as the existing "N done" row, so nothing is swapped out.

Notes

  • Inside the opened "N dropped" fold, each row still says "Not done · dropped", which repeats the fold's own label. Showing only the row's time inside that fold would drop the repetition.

[UX-REVIEWED] 48dec1b

Description read

[DESCRIPTION-READ] fdaaed39a5de975f804ee3ea85c82cb8d55ed3aa7a5c70ec6e0d4537a397fc0d

That sha256 names everything this verdict read: the PR description, plus the 9 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 48dec1b239b25a23de259f7ff3cbafe1b28800c1 — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

First-Principles-Verdict: PASS

Nothing blocks. The fold reverses the spec's "stays among the open rows" pin, and issue #39192 supports that with a user report of about 40 dropped rows making the Board unusable.

Not checked: the workflow patch spans about 180 files from main's history; I reviewed the PR's 25-file change against main.

Notes

  • Item 8 — undeclared: the capture entry drops import { PREVIEW_CREW_MODE } from '../src/utils/previewFlags', a symbol main no longer exports. One sibling still has the broken import: website/capture/conductor-mode-needs-input.tsx:19,24 (grepped PREVIEW_CREW_MODE, 1 left unfixed). Subtraction: delete those two lines there too, or move both deletions to their own change.

What this change ships

Inventory (9 items) — 8 justified

Intent: keep live milestones visible on the conductor mode Board after the conductor drops many. This is a FIX.

  1. Dropped milestones leave the open list for one "N dropped" row below it — justified
  2. The dropped row is folded by default and opens and closes separately from the done row — justified
  3. The dropped row has no top divider when the done row sits right above it — justified
  4. The Hide control on a dropped milestone now sits inside the fold — justified
  5. New "N dropped" label in all twelve locales — justified
  6. The done row and the dropped row are drawn by one shared helper — justified
  7. Spec text changes from "stays among the open rows" to "sits in the N dropped fold" — justified
  8. Capture fixture gains dropped and only-abandoned states and drops a broken preview-flag import — undeclared; one sibling left unfixed
  9. New screenshot script and six PNGs under temp-screenshots/ — justified

[FIRST-PRINCIPLES-REVIEWED] 48dec1b

Description read

[DESCRIPTION-READ] 0ef483f060c230e93afbf761a00977c4f56baa153a1fc34eab42bf4c22b96f2a

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 48dec1b239b25a23de259f7ff3cbafe1b28800c1 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 48dec1b

Verdict parsed from the review's SHA-scoped output markers for commit 48dec1b239b25a23de259f7ff3cbafe1b28800c1.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 48dec1b239b25a23de259f7ff3cbafe1b28800c1 false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings (all downgraded on adjudication)

GPT 6.1 flagged blocking issues on 48dec1b239b25a23de259f7ff3cbafe1b28800c1; Opus 5.5 adjudication downgraded every one of them. Downgraded: the remedy each one needs is disproportionate to the harm it prevents. Adjudication downgraded all 1 blocking finding(s): the remedy each one requires is disproportionate to the harm it prevents.

This comment is updated in place on each push.

Review details

BLOCKING -- website/src/components/SharedCrewsCards.tsx:107 -- Keep failed Crew opens on the error surface

<StatusNotice tone="info" message={refusal.text}
Trigger: A Kiro sign-in expires while the cached Crew list remains visible. Open/Connect calls openRelayCrewTab; the gateway’s SIGNED_OUT rejection reaches this branch and website/src/components/TeamCrewsGroup.tsx:190.
Outcome: The Crew fails to open, but both surfaces present the rejected action as informational status, removing the required ErrorNotice error presentation and explicit hand-off decision.
Anchor: errors-use-error-notice
Fix: Render both refusals through ErrorNotice, retain the sign-in action, and choose the sanctioned hand-off state for each surface.

[BLOCK-MERGE-DOWNGRADED] 48dec1b
[GPT-REVIEWED] 48dec1b

Adjudication (Opus 5.5) — is blocking on each finding proportionate?

F1 — LOW harm, and blocking this PR prevents none of it. Both lines the finding names, website/src/components/SharedCrewsCards.tsx:107 (StatusNotice tone="info") and website/src/components/TeamCrewsGroup.tsx:190 (<p role="status">), are already on main. git diff HEAD^1 HEAD shows no change to either file in this merge ref, so this PR did not write them, and main ships them whether this PR merges or not.
The signed-out refusal is visible, and the user can recover from it: there is a sign-in link at SharedCrewsCards.tsx:107 (KiroAccountLink) and a sign-in menu item at TeamCrewsGroup.tsx:191 (KiroSignInMenuItem). Every other refusal still goes through ErrorNotice (SharedCrewsCards.tsx:111, TeamCrewsGroup.tsx:196-199).
The real fix means reworking two surfaces this PR doesn't touch, outside its goal. Blocking costs the author that work and stops nothing. The finding cites the errors-use-error-notice rule, which is blocking: true in the base-branch rules, but that rule applies to code a PR adds or changes, and this PR changes neither line.

[ADJUDICATION] 48dec1b239b25a23de259f7ff3cbafe1b28800c1 total=1 uphold=0 downgrade=1
DOWNGRADE F1 website/src/components/SharedCrewsCards.tsx:107 reason=disproportionate-remedy
[GPT-ADJUDICATED] 48dec1b239b25a23de259f7ff3cbafe1b28800c1

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 48dec1b239b25a23de259f7ff3cbafe1b28800c1 false-positive: <reason, 20 to 500 characters>

@buluoray
buluoray force-pushed the crew/slack/board-fold-dropped branch from aa1a71f to fb175a6 Compare November 18, 2026 19:35
@buluoray

Copy link
Copy Markdown
Contributor Author

Rebased: main moved in docs/system-specs/modules/crew-mode.md (and other files under docs/system-specs/modules/) since this head went green (1171295 -> be0b414); CI re-running. The new head fb175a6 also takes both First Principles notes: the "When a run is done" spec clause now says an abandoned milestone sits in the "N dropped" fold, and the done and dropped folds share one local milestoneFold instead of two copied blocks.

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed readiness: checking Automated validation is still running labels Nov 18, 2026
@buluoray
buluoray force-pushed the crew/slack/board-fold-dropped branch from fb175a6 to c83df06 Compare November 18, 2026 20:56
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: passed Eligible automated validation passed for the current revision merge conflict Branch has merge conflicts with its base — author must resolve before merge labels Nov 18, 2026
@buluoray

Copy link
Copy Markdown
Contributor Author

Backend Tests shard 8 (Linux and Windows) fails on test/test_bare_session_handle_guard.py::test_no_test_builds_a_bare_session_handle_directly. That is main's red (#39261), not this diff: this PR changes no Python file. #39262 fixes it; this PR will rebase once that lands.

@buluoray
buluoray force-pushed the crew/slack/board-fold-dropped branch from c83df06 to 2478982 Compare November 18, 2026 22:02
@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention labels Nov 18, 2026

@KiroCrewCaptain KiroCrewCaptain left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this. The code and the new test look right on this head. One evidence item blocks the merge.

  1. website/src/pages/chat/command-center/ConductorModeCrewPanel.tsx:756-757, 783, 889: the PR changes the Status view. Abandoned milestones leave the open list, and a new "N dropped" <details> row now sits below the open rows. The PR has no image of this. The Design and UX reviews on head 2478982 both say they cannot evaluate it without a screenshot, and the UX blind read did not run. A review that cannot reach a verdict because evidence is missing counts as a block. Smallest fix: no code change is needed. The capture page website/capture/conductor-mode-run-states.tsx?state=done-some already mounts the real panel with one abandoned milestone, so it renders a "1 dropped" fold now. Capture the Status view on main (before) and on this head (after), with the fold both closed and open, at the default width. Dark and light would help. Attach the images to the PR body or commit them under temp-screenshots/, then re-run the Design and UX lanes on that head.

What the review checked on this head: only abandoned items are folded, and a rejected milestone stays in the open list. The header count, Recap and the stuck, quiet and moving checks still read the full lists. The done fold keeps its classes and test id through the shared milestoneFold helper. The new test pins what goes in the fold, its position and its closed default. The head also merges cleanly with current main.

Optional:

  • CrewWorkerList.test.tsx:615: the /0\D+4/ check matches the text of the whole milestones section, not just the heading. Scoping it to the h3 with an exact Milestones · 0 of 4 would make the pin tighter.
  • Nothing toggles the dropped fold open. A toggle step like the one in the done-fold test would catch a mix-up of the two folds' open state.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: passed Eligible automated validation passed for the current revision labels Nov 19, 2026
@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 21, 2026
@buluoray
buluoray force-pushed the crew/slack/board-fold-dropped branch from 2478982 to ea5b8d7 Compare November 21, 2026 02:27
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Nov 21, 2026
@KiroCrewCaptain

KiroCrewCaptain commented Nov 21, 2026 •

Copy link
Copy Markdown
Collaborator

Code change approver recommendation: A person should decide

Why: the decider estimates a 7% chance that this change introduces a defect, within the 12% limit for approving on its own, but it is held at tier 2: changes requested.

On the Board's Status view, this PR moves milestones closed as abandoned out of the open list and into a folded "N dropped" row below it. Rejected milestones stay in the open list, and the milestone count, Recap and run line are unchanged. Hiding a dropped row still works inside the fold, and the "N done" fold is unchanged now that both folds share one helper. The spec and all twelve languages are updated. Two new tests check the fold and its placement, the remove test was updated to the new row order, and CI is green. Nothing blocks.

Tier: 2, held for a person: changes requested.

An automated recommendation, not a review: a maintainer still decides. It approves on its own only when the estimated chance of a defect is at most 12% and the change has at most 400 changed lines. Decider v3c (217fe607) · commit 48dec1b239 · 163 changed lines. If this recommendation is wrong, reply here: replies are how the approver is evaluated.

@KiroCrewCaptain KiroCrewCaptain left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the rebase. The code still looks right on this head, but the evidence item from the earlier review is still open.

  1. website/src/pages/chat/command-center/ConductorModeCrewPanel.tsx:1108: abandoned milestones now leave the open list (line 972) and go into a new "N dropped" <details> row below the open rows, so the Status view looks different. The PR body still has no image, and the diff adds no file under temp-screenshots/. Because of that, the Design and UX reviews on ea5b8d7 both say they cannot evaluate the change, and the UX blind read did not run. When a review cannot reach a verdict because evidence is missing, that counts as a block. No code change is needed to fix this. website/capture/conductor-mode-run-states.tsx?state=done-some already mounts the panel with one abandoned item, so it renders a "1 dropped" fold. Capture the Status view on main (before) and on this head (after), with the fold both closed and open, at the default width. Dark and light would help. Attach the images to the PR body (or commit them under temp-screenshots/), then re-run the Design and UX lanes on that head.

Earlier review on 2478982:

  • Missing before and after screenshots: still stands. The rebase added no image, and there is no reply to the review.

What the review checked on this head:

  • Only abandoned items fold. A rejected milestone stays in the open list.
  • The header count, the Recap and the stuck, quiet and moving checks still read the full lists.
  • The done fold keeps its classes and test id through the shared milestoneFold helper.
  • The updated remove test re-pins the moved Hide target and the new row order without loosening any assertion.

Done well: one helper now draws both folds, with no copied <details> block, so the two folds cannot drift apart.

Optional:

  • CrewWorkerList.test.tsx:615: the /0\D+4/ check matches text anywhere in the milestones section. An exact Milestones · 0 of 4 check on the heading would pin the count more tightly.
  • No test toggles the dropped fold open. A toggle step like the one in the done-fold test would catch a mix-up between the two folds' open state.
  • When a settled run has only abandoned milestones left, the empty open list puts the done fold's bottom border right on top of the dropped fold's top border, so the divider looks doubled.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: passed Eligible automated validation passed for the current revision labels Nov 21, 2026
…ts screenshots

Pin the Milestones heading text exactly, toggle the dropped fold open
without opening the done fold, and drop the dropped fold's top rule when
only the done fold sits above it, so the divider is not doubled. Add a
component capture for the fold and its screenshots.
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Nov 21, 2026
@buluoray

Copy link
Copy Markdown
Contributor Author

Addressed in 48dec1b:

  1. Screenshots: the PR body now has six component renders, dark and light, each captioned "Component render, not the live page":

    • the open list with the dropped fold closed
    • the dropped fold opened
    • a run with only abandoned milestones left

    They come from the new website/capture/shoot-conductor-mode-dropped-fold.mjs, which mounts the real ConductorModeCrewPanel with mocked board data at side-panel width. The files are committed under temp-screenshots/conductor-mode-dropped-fold/. I added the dropped and only-abandoned states to conductor-mode-run-states.tsx. I also removed its import of PREVIEW_CREW_MODE, which main no longer exports, so the page loads again.

  2. Optional, count check: CrewWorkerList.test.tsx now checks the heading text exactly (Milestones · 0 of 4) instead of /0\D+4/.

  3. Optional, toggle test: a new test opens the dropped fold and checks that the done fold stays closed.

  4. Optional, doubled divider: the dropped fold drops its top rule when no open row sits between it and the done fold. The new test checks this. It fails if the rule is forced back on.

command-center vitest passes (247 tests). tsc -b and eslint are clean. Could you re-run Design and UX on this head?

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Nov 21, 2026
@KiroCrewCaptain
KiroCrewCaptain enabled auto-merge (squash) November 21, 2026 05:37

@KiroCrewCaptain KiroCrewCaptain left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving head 48dec1b. The review checked these points on this head:

  • Only abandoned milestones move into the new "N dropped" fold. Rejected ones stay in the open list.
  • The header count, the Recap and the stuck, quiet and moving checks still read the full milestone set.
  • Hide still works for rows inside the fold, and focus falls back to "Show again".
  • The new key is in all locale files.
  • The crew-mode spec line is updated in the same PR.

Earlier review on ea5b8d7, item by item:

  • Missing screenshots: fixed. Six renders are committed under temp-screenshots/, and the Design and UX lanes both pass on this head.
  • Heading count check: fixed. The test now checks the exact Milestones · 0 of 4 heading.
  • Dropped fold toggle: fixed. A new test opens the dropped fold and checks that the done fold stays closed.
  • Doubled divider: fixed. The dropped fold drops its top rule when it sits right under the done fold.

Done well: one milestoneFold helper now draws both folds, so their markup and toggle wiring cannot drift apart.

Optional:

  • website/capture/conductor-mode-needs-input.tsx:19,24 still imports PREVIEW_CREW_MODE, which main no longer exports. That is the same fix as the run-states entry, and you could add it here or send it as a small follow-up.
  • CrewWorkerList.test.tsx:595: an expect(fold).toHaveClass('border-t') in the test with open rows would pin the divider above the fold.
  • The screenshots could move to PR attachments with gh pr edit --attach, so they do not stay in main's history.

@KiroCrewCaptain
KiroCrewCaptain merged commit 0675855 into main Nov 21, 2026
112 of 116 checks passed
@KiroCrewCaptain
KiroCrewCaptain deleted the crew/slack/board-fold-dropped branch November 21, 2026 05:37
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Nov 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Conductor Mode Board: dropped milestones are not folded and bury the live ones

2 participants