Task detail: Start or Finish as the primary action, and "Hand to an agent" from the task when a discussion is linked (KT-1901)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 58/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- developer-experience, frontend
Research direction
Start with pages/PlanningPage.tsx around line 1198 and components/DiscussionPlanPanel.tsx around line 1338 to trace the task detail actions and existing TaskLaunchDialog. Check how status changes and discussion links are handled, then add UI tests for the four status states and for linked and unlinked discussions. Done means the header actions work as specified and captures are shown to the owner.
Written by the indexing model from the issue text.
Description
Kronn task: KT-1901 (0.15.4), part of design-system lot 3 (the detail), KT-1859. Source: UI audit of 2026-11-18.
Design-system lot 3 (UI audit 2026-11-18). The only item of the lot that adds an entry point rather than moving one.
Today the task detail ends with a "Save" button at the bottom of a long form, not pinned (pages/PlanningPage.tsx:1198), while its subtasks save at once. A task cannot be handed to an agent from the task: TaskLaunchDialog requires a discussionId and is mounted only in components/DiscussionPlanPanel.tsx:1338.
How:
- Header primary action follows the status: Start (idea, todo), Finish (in progress), Reopen as a secondary action (done). It calls the existing status change.
- When the task has a linked discussion, the header shows "Hand to an agent" as a secondary action that opens the existing
TaskLaunchDialogwith that discussion (the first linked one, or a choice when several). With no linked discussion the action is shown disabled with its reason and a "Link a discussion" shortcut; no new launch path is created. - The save model of the form is handled by the forms lot (declared per screen); this ticket only moves the actions into the header.
Done when:
- The task detail header shows Start or Finish according to the status and it changes the status (UI tests for the four states)
- A task with a linked discussion opens TaskLaunchDialog from its own detail; without one the action explains why it is disabled (UI tests); captures shown to the owner
- Dominant language
- Rust
- Stars
- 18
- Forks
- 2
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 48
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DocRoms/Kronn
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug UI
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug UI
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug UI
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
bug UI
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
eventflux-io/eventflux#203 ·
Maintainers usually reply within 1 day
-
bug ui
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
userFRM/egui-charts#4068 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
trezor/trezor-firmware#8357 ·
Maintainers usually reply within 2 days
-
fuzz-crash review-followup
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day