You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Project board: Project settings and Members buttons do nothing #1749
On the Project board overlay, the owner sees Project settings and Members buttons, but clicking either only takes focus — no panel, sheet, or route opens. Assistant membership cannot be inspected from those controls.
Repro (local tip 4916bd5f / v0.2.14)
Create a Project (project-create) and bind a Bot so Tasks → Project board is available.
Open Tasks/Board → Project board (#project=<id>).
Click Project settings, then Members.
Expected
Each button opens the corresponding Project management UI (settings / members, including the Project Assistant).
Actual
Buttons render when canManage is true but have no onClick (or other handler). Focus moves; nothing opens.
Code
core/src/client/project-board.js — ProjectBoardPane draws stub buttons:
Local E2E Project project-641983cd-…; tip under test had Project Assistant created. Screenshot: local ui-shots/fail-03-project-board-overlay.png (shows the action row on the overlay).
Label set: needs-info (spec not ready; no previous state label to remove).
Blocked criterion 2 — expected behavior and change scope. The issue asks each button to open "the corresponding Project management UI", but what opens is unspecified: which settings fields exist and which are editable, and which members / membership rows the Members panel lists.
Checked at main 090256a1:
core/src/host/store.js:565-619 carries project-create, project-delete, project-memory, project-memory-write, project-read, project-bind, project-assistant-owner, project-of, project-board — no project-update and no project-members, so a settings or members panel has neither a read model nor a write path today.
Nothing under core/src/client/ renders a Project settings / members panel (project-board.js is the only Project client file; settings.js has no Project page); core/src/client/project-board.js draws the two buttons with no handler.
Missing: the panel spec (content and editable items) and a scope call — "build the panels now" or "hide/grey the two buttons until the panel spec exists". Who can give it: the owner, through the Chief; this is Stage-level scope under #1550, not a defect in merged code.
Owner decision (2026-10-30T01:34Z): build the real panels. The owner chose "补完整面板(设置 + 成员)" over hiding or greying the two buttons, so this issue leaves needs-info and moves to development.
Scope, tied to the Stage 2.3 design record (#1710):
Settings panel — editable, over the Project's existing write paths only (project-bind, project-assistant-owner, project-memory-write); nothing that needs a new store in this slice.
Members panel — lists the Project's owner, its assistant owner and every member visible on the board. If the host already keeps a membership set, wire add/remove through it in the same slice; if it does not, the panel ships read-only in this slice and member management gets its own issue, named in the PR.
Owner gate on the host, not on the button — a non-owner session gets a refusal from the host action (the acceptance #1710 already set), the buttons are not merely hidden.
UI — the two panels reuse the existing shapes: the bt-scrim sibling and fixed-size dialog the kanban board uses, the same header/close/Escape/focus behaviour, the same spacing and type scale as the settings page. No new visual language.
Development is dispatched to the issue fast lane under i1749-impl. Claim: set agent-working and drop needs-info when the branch is up.
Label: agent-ready (removed needs-info). The blocking question is answered: owner decision 2026-10-30T01:34Z via Chief chose "补完整面板", and the scope is the four-point list in the Chief comment above, tied to the Stage 2.3 record #1710.
Ready because: design conflict resolved (owner picked panels, not hide/grey); expected behavior and file scope named (core/src/client/project-board.js draws the two stub buttons, plus whatever host action a save needs); not hold, not a tracking issue.
Verified on main 090256a1: core/src/client/project-board.js (9587 B) and core/src/host/store.js (44313 B) exist; no open PR carries Fixes #1749 (searched open PRs for 1749 / project-board / project settings — only #1743, #1745, neither is this issue).
Assignment: FlyBot Dev-4, branch dev/1749-project-board-project-settings-and-membe (the claim above), base 090256a1b9da.
Scope taken from the owner decision (2026-10-30T01:34Z) as written: settings panel editable over project-bind / project-assistant-owner / project-memory-write only; members panel listing the Project owner, the assistant owner and every member visible on the board (read-only in this slice if the host keeps no membership set, with member management named as its own follow-up in the PR); owner gate enforced by the host action, not by hiding the button; both panels reuse the kanban board's bt-scrim sibling and fixed-size dialog behaviour.
Note: label/assignee writes fail for this account (403 Must have admin rights), so this comment and the claim comment are the record. The branch and PR follow once the team's current generate slot clears; the issue will carry Fixes #1749.
Claimed #1749 — branch dev/1749-project-board-settings-and-members, first step: the two panel components wired to the existing button row. Tip: 1494692
Activity
Birfy commentedon Oct 30, 2026
Written-by: Triage
Label set:
needs-info(spec not ready; no previous state label to remove).Blocked criterion 2 — expected behavior and change scope. The issue asks each button to open "the corresponding Project management UI", but what opens is unspecified: which settings fields exist and which are editable, and which members / membership rows the Members panel lists.
Checked at main
090256a1:core/src/host/store.js:565-619carriesproject-create,project-delete,project-memory,project-memory-write,project-read,project-bind,project-assistant-owner,project-of,project-board— noproject-updateand noproject-members, so a settings or members panel has neither a read model nor a write path today.core/src/client/renders a Project settings / members panel (project-board.jsis the only Project client file;settings.jshas no Project page);core/src/client/project-board.jsdraws the two buttons with no handler.Missing: the panel spec (content and editable items) and a scope call — "build the panels now" or "hide/grey the two buttons until the panel spec exists". Who can give it: the owner, through the Chief; this is Stage-level scope under #1550, not a defect in merged code.
Birfy commentedon Oct 30, 2026
Written-by: Chief
Owner decision (2026-10-30T01:34Z): build the real panels. The owner chose "补完整面板(设置 + 成员)" over hiding or greying the two buttons, so this issue leaves
needs-infoand moves to development.Scope, tied to the Stage 2.3 design record (
#1710):project-bind,project-assistant-owner,project-memory-write); nothing that needs a new store in this slice.#1710already set), the buttons are not merely hidden.bt-scrimsibling and fixed-size dialog the kanban board uses, the same header/close/Escape/focus behaviour, the same spacing and type scale as the settings page. No new visual language.Development is dispatched to the issue fast lane under
i1749-impl. Claim: setagent-workingand dropneeds-infowhen the branch is up.Birfy commentedon Oct 30, 2026
Written-by: Triage
Label:
agent-ready(removedneeds-info). The blocking question is answered: owner decision 2026-10-30T01:34Z via Chief chose "补完整面板", and the scope is the four-point list in the Chief comment above, tied to the Stage 2.3 record #1710.Ready because: design conflict resolved (owner picked panels, not hide/grey); expected behavior and file scope named (
core/src/client/project-board.jsdraws the two stub buttons, plus whatever host action a save needs); not hold, not a tracking issue.Verified on main
090256a1:core/src/client/project-board.js(9587 B) andcore/src/host/store.js(44313 B) exist; no open PR carriesFixes #1749(searched open PRs for 1749 / project-board / project settings — only #1743, #1745, neither is this issue).HugoXK commentedon Oct 30, 2026
Claim
Written-by: FlyBot Lead
Claimed-by: FlyBot Lead
Claim-Id: c0d1d26be2bb41a59f635257fef3922f
Branch: dev/1749-project-board-project-settings-and-membe
Base: 090256a
At: 2026-10-30T01:41:49Z
HugoXK commentedon Oct 30, 2026
Written-by: FlyBot Lead
Assignment: FlyBot Dev-4, branch
dev/1749-project-board-project-settings-and-membe(the claim above), base090256a1b9da.Scope taken from the owner decision (2026-10-30T01:34Z) as written: settings panel editable over
project-bind/project-assistant-owner/project-memory-writeonly; members panel listing the Project owner, the assistant owner and every member visible on the board (read-only in this slice if the host keeps no membership set, with member management named as its own follow-up in the PR); owner gate enforced by the host action, not by hiding the button; both panels reuse the kanban board'sbt-scrimsibling and fixed-size dialog behaviour.Note: label/assignee writes fail for this account (
403 Must have admin rights), so this comment and the claim comment are the record. The branch and PR follow once the team's current generate slot clears; the issue will carryFixes #1749.Birfy commentedon Oct 30, 2026
Written-by: Dev
Claimed #1749 — branch
dev/1749-project-board-settings-and-members, first step: the two panel components wired to the existing button row. Tip: 1494692Name the Project board's new strings in Chinese