Roadmap Studio

1.32.112026-09-07

• A roadmap scoped to picked cards opens without reading the whole inventory. Opening a scenario whose scope names specific cards used to page through every card of those types and keep the ones inside the picked branches — on a large estate, hundreds of milliseconds spent on cards the roadmap was never going to show. It now reads exactly the picked cards and their children. A scope that is a whole card type, or one that picks so many cards that reading them one by one would cost more, still takes the single pass it always did.

1.32.102026-09-07

• The «On a card» switch now actually saves. In 1.32.9 the switch flicked back to on the moment you released it, and the roadmap row stayed on every card: the setting was silently dropped on the way in and never stored. Turn it off and it stays off — on the switch, after a reload, and on the cards. Reproduced and re-verified in a real browser against a running Turbo EA.

• The roadmap opens faster on estates with many owners. Naming the owner of each card used to be one lookup per owner, one after another, inside every roadmap open — on a hosted database that is the number of owners multiplied by its round trip. It is one directory read now.

1.32.92026-09-07

• You can now turn the roadmap row on a card off. Settings gains an «On a card» section with a single switch: leave it on and every card keeps its «In roadmap scenarios» line, turn it off and card pages read exactly as they did before Roadmap Studio was installed. It is on by default, so nothing changes on upgrade unless you switch it.

• The roadmap row on a card now asks whether you may see that card. It used to ask only whether you may see the roadmap, which was wrong in both directions: someone with roadmap access could read which plans touch a card they are not allowed to open, while a colleague whose access to a card comes from a stakeholder role on that card was refused the row entirely. Both are fixed — the row now appears for exactly the people who may open the card and see the roadmap.

• This release requires Turbo EA 2.130.0 or later. The per-card permission check above is a platform capability that arrived in that version; on an older Turbo EA the extension would fail to start rather than fall back, so it is refused at install instead. Stay on 1.32.8 until you have upgraded.

• French: a card is once again «fiche», not «carte». Four labels — the dashboard card count, the Card column in a plan's changes, and the «Selected cards» scope option and its hint — used the wrong word for the entity. «Carte» keeps its place where it genuinely means a map.

1.32.82026-09-07

• The roadmap scenarios on a card now keep their own line at any window width. The «In roadmap scenarios» row sat below the card's other chips only because the window happened to be narrow enough to push it there — on a wider screen it joined them, crowding the line. It now asks for a line of its own, so the card reads the same whatever the width, and the spacing above it comes from the card rather than from the extension.

1.32.72026-09-07

• Settings stops rearranging itself while it opens. The Demo data section appeared first, on its own, and was then shoved down the page as the cost model and governance sections arrived above it — each section waited for its own data before drawing anything, and they did not arrive together. All four sections are now in place from the moment the tab opens, greyed until their values land, and the settings they share are read once instead of twice. A section whose data cannot be read says so instead of silently staying invisible, and opening a link straight to Settings no longer bounces you back to the roadmap. There is no step to take on upgrade.
• A milestone's diamond now sits exactly on its dotted line. On the roadmap timeline the diamond was drawn a few pixels to the left of the dashed line marking the same date, so the two never quite met and the mark looked misplaced against the plan behind it. The diamond is centred on its line again. There is no step to take on upgrade.

1.32.52026-09-05

• The build checks run again. A recent change moved the extension's table-name prefix behind an import that only resolves inside a running Turbo EA, so the automated checks that protect every release could not even start — four of the suites failed before running a single test. The prefix now lives in a small module of its own that resolves everywhere. Nothing changes in the product; there is no step to take on upgrade.

1.32.42026-09-05

• A build check could fail for no reason. The test covering the review-only apply dialog read the screen before the dialog had finished rendering, so it failed on a slow runner now and then. Nothing changes in the product.

1.32.32026-09-05

• This extension now ships a changelog. Every release from here on documents what changed for you in this file, and it travels inside the signed bundle so it is on disk wherever the extension is installed. The version notes that used to be stamped through the README have moved here.

1.32.22026-09-05

• The French interface calls a card «fiche» rather than «carte», matching Turbo EA's own vocabulary.

1.32.12026-09-04

• The history filters no longer render with the field's border drawn through the label.

1.32.02026-09-04

• The review board decides. A board was an address list; it now votes. A scenario is submitted to a named board, each member records a decision with their reasoning, and the thread of the discussion stays on the record.

1.31.12026-09-04

• Pros and cons are off the comparison slide and onto their own, so a dense comparison stays readable; the deck exports as one document; Governance is review only.

• A loop when editing plateaus.

1.31.02026-09-04

• Named, reusable review boards — the board was a single global setting; there can now be as many as you have decisions to take.
• A complete decision record, and it is optional: a scenario can be approved without one.
• Initiatives are recorded at approval.

1.30.02026-09-03

• «Do nothing» as a comparison pill, so the column arguing for inaction sits beside the scenarios rather than being assumed.
• Present mode walks the deck.

• The page boots frame-first, so there is something to look at immediately.

1.29.02026-09-03

• A workbench that is readable on a phone, an optional «Do nothing» scenario, filters that reach the exported deck, and one slide per argument.

1.28.32026-09-03

• The deck's cost curve is drawn in full, and its icons survive the capture.

1.28.22026-09-03

• The review board is judged only once the reviews have been read.

1.28.02026-09-03

• Pros and cons on a scenario, a recommended scenario, and an activity history of everything the plan has been through.

1.27.02026-09-03

• The review board lives in Governance, the recommendation is set from a dialog, and the demo carries two competing scenarios rather than one.

1.26.02026-09-02

• The workbench fits the room it has rather than assuming a wide screen.

1.25.02026-09-02

• The tabs feel instant.

1.24.02026-09-02

• The decision on the record — every approval files what was decided and why.

1.23.02026-09-02

• The deferred list, closed. Everything the earlier rounds recorded and left is either done or explicitly dropped.

1.22.12026-09-02

• A crash on the Architecture tab.

1.22.02026-09-02

• Money on the picture — costs on the roadmap itself, formatted in the workspace currency, with a discount setting.

1.21.02026-09-02

• A decision that holds — an approval that survives later edits to the scenario.

1.20.02026-09-02

• Where the plan meets the card — the roadmap is reachable from the cards it plans, and the card panel opens from the roadmap.

1.19.02026-09-02

• The roadmap you can read — a filter bar, a range control, and a packed marker band.

1.18.02026-09-02

• The edges, finished — plateau and milestone editing, first-run copy, and the remove and duplicate prompts.

1.17.02026-09-02

• One Lifecycle, a visible arrow switch, arrows that stop at the card edge, and the card panel opening from the inventory.

1.16.02026-09-02

• The panel says everything about a card, and the bands stop colliding.

1.15.02026-09-02

• A guide line while dragging a date.

1.14.02026-09-02

• The dependency arrows and the lifecycle line are drawn by core's own routing, so they match the rest of Turbo EA exactly.

1.13.02026-09-01

• The arrows were drawn under the cards.

1.12.42026-09-01

• One icon size across the toolbar.

1.12.32026-09-01

• A plateau gets a glyph.

1.12.22026-09-01

• The demo shows what constraints are for — it now carries a sequencing error the roadmap is meant to catch, so the warning, the violation count and the one-click Align can be seen without drawing a constraint first.

1.12.12026-09-01

• Icons stay icons, and the plan says what it moved.

1.12.02026-09-01

• The Gantt view is finished, and the plan states its purpose.

1.11.02026-09-01

• The canvas gestures work.

1.10.02026-09-01

• The roadmap becomes a canvas — drag, drop and draw the plan instead of filling in a form.
• Dependencies you can draw: switch on constraint mode and connect two cards.

1.9.02026-09-01

• Measure the plan against what actually happened.

1.8.02026-09-01

• A plan holds what its cards depend on, and the loop closes after a plan is applied.

1.7.02026-09-01

• One gesture, a stated purpose, and a story per plateau.

1.6.02026-09-01

• Authoring without friction, and the approver on the record.

1.5.02026-08-31

• The real approval gate, and an honest comparison between scenarios.

1.4.02026-08-31

• Scope is edited through core's shared card browser, so picking cards works the way it does everywhere else in Turbo EA.

1.3.02026-08-31

• Dates are entered through core's shared date field everywhere.

1.2.02026-08-31

• A guided create-scenario wizard, a core-style right-click menu on the planning inventory, and real content on the exported slides.

• A new scenario no longer swallows the whole inventory — scope modes decide what it covers, with honest counts and an empty state that says what to do next.

1.1.12026-08-31

• A crash on first render, a broken Edit-scenario dialog layout, and a roadmap window that reached arbitrarily far into the past.

1.1.02026-08-31

• Apply a scenario to the live inventory.
• Transformations — the grouping level above scenarios.
• Scenario scoping pulls existing cards into the plan, and the Compare tab charts the scenarios you pick rather than all of them.

1.0.02026-08-31

• First release. Plan the target landscape as scenarios on a timeline: plateaus, replacements, costs, dependencies and a comparison between competing plans — with one-click demo data so a trial instance has something to show on every screen.