From 119c18a30bca66b5c3cfd3e4c28bcdd4dec43071 Mon Sep 17 00:00:00 2001 From: Dave Date: Wed, 25 Feb 2026 18:12:20 +0000 Subject: [PATCH] story-kit: create 198_story_distinguish_work_item_types_in_web_ui --- .../198_story_distinguish_work_item_types_in_web_ui.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.story_kit/work/1_upcoming/198_story_distinguish_work_item_types_in_web_ui.md b/.story_kit/work/1_upcoming/198_story_distinguish_work_item_types_in_web_ui.md index 4c12f1e..90d4561 100644 --- a/.story_kit/work/1_upcoming/198_story_distinguish_work_item_types_in_web_ui.md +++ b/.story_kit/work/1_upcoming/198_story_distinguish_work_item_types_in_web_ui.md @@ -17,6 +17,7 @@ As a project operator using the web UI, I want to visually distinguish between s - [ ] Each card displays a small uppercase text badge (STORY, BUG, SPIKE) next to the #ID, colored to match the left border - [ ] Item type is parsed from the story_id field by matching the segment after the numeric prefix (N_story_..., N_bug_..., N_spike_...) - [ ] Items with an unrecognised type prefix get a neutral border and no badge +- [ ] No backend changes — type is derived purely from the existing story_id on the frontend ## Out of Scope