December 16th
Never lose work to a concurrent edit
When two people edit the same card description at the same time, the last save used to silently win — quietly overwriting the other person's work. Now StoriesOnBoard detects when the description changed on the server while you were editing.
Instead of overwriting, you get a clear conflict dialog that lets you decide what happens: keep your version, keep the other person's version, or merge the two. Your edits are never thrown away without you choosing to.
This is especially handy during live workshops and grooming sessions, where several people are editing the same stories at once.
Paste markdown and watch it format itself
If you paste markdown into a card description — from another card, the version-history dialog, or any external markdown source — it now renders as properly formatted content instead of raw # and - [ ] characters.
Headings, bullet lists and task lists all come through formatted, matching how the editor displays a description when it loads. No more cleaning up stray markdown syntax by hand.
December 8th
Card description version history
From now on, you can easily see how a card's description has changed over time. Here's what you can do with the new version history:
View all previous versions of a card description
Restore clarity by seeing who changed what and when
Compare any two versions side by side, with changes highlighted (added text in green, removed text in red – just like on GitHub)
This makes it much easier to track edits, collaborate with your team, and keep your user stories clean and consistent. 🚀
Here are a few practical ideas for how and when to use card description version history:
✅ After a workshop or grooming session – check what changed in key user stories while the team was editing.
🧩 When something looks confusing – compare versions to see which part of the description was added, removed, or reworded.
👥 To understand team decisions – see who changed what and when, so you can follow the decision trail.
🔁 Before restoring older wording – compare a past version with the current one to make sure you bring back only what you need.
📝 For auditing and documentation – keep track of how requirements evolved over time for stakeholders or future reference.
Roadmap filter
Whenever your roadmap become crowded, you can focus on a selected topic by filtering your product roadmap by label. Open the filter menu and select one or more labels to filter relevant cards.
There is one more thing, filter works the same (back and forth) on the prioritization view.
Total number of cards and estionations
If you're interested in a high-level overview of the story map, in terms of all cards, simply open the about this board panel where you can get a quick statistic of your backlog.
