fix(stories): project picker + resolved name on detail + create SID #141

Merged

zaelgohary merged 2 commits from development_fix_stories_project_link into development

2026-04-22 15:58:41 +00:00

zaelgohary commented

2026-04-22 15:45:07 +00:00

Member

Summary

Two things were broken when working with stories. There was no way to link a story to a project from the form, and the detail page showed an opaque ID where the project name should be. On top of that, creating a story or a milestone flashed a red "Method not found" banner even though the record actually saved — the service was looking the new record up by a placeholder ID instead of the real one the server assigned.

Closes #137
Closes #142

Changes

The story form now has a project picker (with a "— None —" option)
The story detail page shows the project's name instead of a raw ID
Stories can load the project list so the picker and the detail name lookup have a source
Creating a story or milestone no longer flashes a "Method not found" error — the service now looks up the saved record by the real ID, not the placeholder

Test Results

cargo check/clippy/fmt/test clean on both crates; wasm built and verified end-to-end on the shared test instance.

Manual verification

New Story form shows the Project picker with every project plus "— None —"
Creating a story with a project selected succeeds; detail view shows Project: <name>
Creating with "— None —" succeeds; detail view omits the Project row
New Milestone creation succeeds with no error banner

## Summary Two things were broken when working with stories. There was no way to link a story to a project from the form, and the detail page showed an opaque ID where the project name should be. On top of that, creating a story or a milestone flashed a red "Method not found" banner even though the record actually saved — the service was looking the new record up by a placeholder ID instead of the real one the server assigned. ## Related Issue Closes #137 Closes #142 ## Changes - The story form now has a project picker (with a "— None —" option) - The story detail page shows the project's name instead of a raw ID - Stories can load the project list so the picker and the detail name lookup have a source - Creating a story or milestone no longer flashes a "Method not found" error — the service now looks up the saved record by the real ID, not the placeholder ## Test Results `cargo check/clippy/fmt/test` clean on both crates; wasm built and verified end-to-end on the shared test instance. ## Manual verification - [ ] New Story form shows the Project picker with every project plus "— None —" - [ ] Creating a story with a project selected succeeds; detail view shows `Project: <name>` - [ ] Creating with "— None —" succeeds; detail view omits the Project row - [ ] New Milestone creation succeeds with no error banner

zaelgohary added 2 commits

2026-04-22 15:45:07 +00:00