Stories: new stories are orphaned from any project and detail shows raw SID #137

New issue

Closed

opened 2026-04-22 13:29:30 +00:00 by zaelgohary · 0 comments

zaelgohary commented

2026-04-22 13:29:30 +00:00

Member

Two related bugs in the Stories island combine to make stories unusable in a multi-project setup:

new_story_view.rs passes project_sid: None to StoryForm, and story_form.rs has no project picker field. Every created story is persisted with project_sid = None so no story can ever be linked to the project the user intended it for.
story_detail_view.rs renders the stored project_sid value verbatim (e.g. proj_01HX…) instead of looking the project up via ProjectService and showing its name.

Fix:

Add a project picker to story_form.rs (sourced from ProjectService::list), defaulting to the currently-selected project if any.
In story_detail_view.rs, resolve project_sid to a project and render project.name; fall back to — when no project is set.

Two related bugs in the Stories island combine to make stories unusable in a multi-project setup: 1. `new_story_view.rs` passes `project_sid: None` to `StoryForm`, and `story_form.rs` has no project picker field. Every created story is persisted with `project_sid = None` so no story can ever be linked to the project the user intended it for. 2. `story_detail_view.rs` renders the stored `project_sid` value verbatim (e.g. `proj_01HX…`) instead of looking the project up via `ProjectService` and showing its name. Fix: - Add a project picker to `story_form.rs` (sourced from `ProjectService::list`), defaulting to the currently-selected project if any. - In `story_detail_view.rs`, resolve `project_sid` to a project and render `project.name`; fall back to `—` when no project is set.