September 13
Define your story map's color legend with your AI agent
Every story map can give its colors a meaning — Blue becomes Backend (Blue), Green becomes Team A (Green). Until now that legend could only be edited in the UI, so an agent building a map from a document had to stop and ask you to name the colors. Two new MCP tools close that gap:
List story map colors returns the map's colors with their current labels and the default color for each card type.
Update story map color sets or clears a color's label. Duplicate labels are rejected and no card's color changes as a side effect.
Label changes show up live on open next-gen boards, and the agent can use the new labels right away when creating or updating cards. The full agent flow now runs without interruption: create the map, name the colors, define the annotations, create the cards.
Create cards in their final state, in one call
Your agent can now set a subtask's status, priority, business value and effort, and any card's annotations, when it creates the card — no follow-up update needed. Creation is all-or-nothing: an invalid value means no card is created. Everything the agent sets on a new or updated card now appears on open boards instantly, personas and tracking-view position included.
Explicit Save and Cancel when editing cards and release goals
Card descriptions and release goals on next-gen boards used to save when you clicked outside the editor. They now have explicit Save and Cancel buttons right below the editor — Ctrl+Enter (⌘+Enter on Mac) saves, Esc cancels — and clicking anywhere else inside the card leaves your draft as it is.
If you close the card, open another one, switch editors, archive a release or push to Jira, GitHub or Azure DevOps with unsaved changes, you get one simple question: Save, Discard, or Keep editing. A failed save or an edit conflict keeps your draft open so nothing you typed is lost.
Cards unlink automatically when their GitHub issue is deleted
When a linked GitHub issue was deleted, the StoriesOnBoard card kept its link: it still looked synced, still offered "Open in GitHub", and its status couldn't be changed locally. That's fixed. Deleting the issue now unlinks the card, keeps it with all its content, resets it to the map's default status, and lets you edit the status locally or push the card again as a new issue. Cards in the trash lose the stale link too, so restoring them doesn't bring it back.