November 9
Your board stays up to date, and tells you when it isn't đ
On a next-gen board, your teammates' changes appear live. Until now, that live connection didn't always come back after a network drop, a laptop sleep or a tab left in the background, and nothing told you: the board quietly stopped showing what others were doing.
It reconnects on its own. After a network drop, a server restart or a paused background tab, the board connects again by itself, right away when you return to the tab or your network comes back.
It tells you when you missed something. If your board really missed a change, from a teammate, an integration, an import or an AI agent, you'll see "This map may be out of date." Click Reload to catch up. Only your own board reloads, but text you're still typing in an open editor is lost, just like when you refresh the page.
It lets you know about updates. After we release a new version, you'll see "A new version of StoriesOnBoard is available" once, with a Reload button.
Large story maps are much faster âĄ
If your next-gen story map has grown to thousands of cards, for example because your AI agent breaks big stories into many small ones, you'll notice the difference right away. In our tests with real-size maps:
Story map | Opening the map | Switching views | Longest pause while dragging |
1,000 stories | 15 s â 4 s | 2â3 s â 0.3 s | 1.3 s â 0.05 s |
2,000 stories | 30 s â 5 s | 7â12 s â under 1 s | 4 s â 0.15 s |
5,000 stories | couldn't open â about 10 s | a few seconds | under 0.2 s |
Large maps no longer crash the browser tab when you reload or filter them.
Opening the editor of a new card is close to instant, even on the largest maps.
On maps with 300 or more cards, the board builds the parts you're looking at first and the rest as you scroll. Cards look and behave exactly as before.
When you switch views on a large map, the board dims right away, so you can see it's working.
Good to know
Your browser's own find (from its menu) only sees the part of a large map that's already built. Press Ctrl+F (Cmd+F on a Mac) on the board to use the StoriesOnBoard search instead, which finds every card.
If a map grows past 300 cards while you have it open, the faster mode starts after your next reload or view switch.
Closing a workspace is reliable now đď¸
Closing a large workspace could spin for a long time and end with an error; now it runs in the background, always finishes, and you can follow its progress on a status page.
Smaller improvements and fixes đ ď¸
Imports skip issues in archived releases
When you imported from GitHub, Jira or Azure DevOps, an issue whose release was archived (a closed GitHub milestone or an archived Jira version) became a card hidden in that archived release, and the import counted it as imported. Now:
These issues are skipped, and the import message tells you how many: "N items were not imported because their release is archived." On the next-gen board, More details lists them with the reason.
The count of imported cards only includes cards that were really created.
A skipped issue comes in by itself with a later import once its release is no longer archived.
When no new card was imported but existing cards were updated, the message now says so, instead of "There are no new or updated items".
Delete warnings show how many cards go with it
On the next-gen board, deleting a goal or a step now tells you how many cards are deleted with it, for example: "Are you sure you want to delete the card "Checkout" and its 12 children?" If there are none, the warning doesn't mention children at all.
Long code and wide tables stay inside the description
A long URL or file path in inline code, or a wide table, no longer pushes the card description past the edge of the dialog. Inline code wraps to the next line, and wide tables scroll sideways inside the description. This applies to card and release descriptions.