color_fad5e429-4109-46d8-b740-b5fc936b54ac
Sign In
Sign Up
color_fad5e429-4109-46d8-b740-b5fc936b54ac
Sign In
Sign Up

FlowBoards Release 1.8

21st August 2026

This August release introduces important architectural and usability improvements, enabling more autonomous local design while making everyday collaboration more intuitive.

01

Autonomous design

Design permissions for ticket types and classes of service

Release 1.8 extends design access beyond central administrators. Members with Designer permissions can now create and design boards, ticket types, flows, and classes of service within their local context.

This enables delivery teams and flow managers to evolve their own processes without relying on a central administrator to approve or action every change. The underlying architectural update is designed to support enterprise-scale deployment while preserving local control and autonomy.

FlowBoards settings screen showing organisation design options.
Regular members can access the design controls for flows, ticket types, and classes of service.
Permissions management screen in FlowBoards.
Permissions can be configured locally across boards, bins, flows, ticket types, classes of service, and custom fields.
What this means: an administrator can grant a specific group User or Designer access to the elements it needs, allowing teams to act locally without affecting unrelated boards across the organisation.
02

Local familiarity

Short, context-relevant names without losing structure

Only the text after the final dot in a ticket type or class of service name is shown in the interface. This keeps selection lists short and familiar while the complete path retains the broader organisational context.

For example, KMM Appraisal.Not Implemented is displayed simply as Not Implemented on the KMM Practice Map board. In the same way, Department1.Expedite and Department2.Expedite remain separate classes of service while each local team sees the clear name Expedite.

Class of service picker showing full paths and short local labels.
The full organisational path is retained, while the local name stays concise in context.
FlowBoards display showing clear class-of-service labels at board level.
Classes of service are displayed with short, easy-to-read labels.
FlowBoards permissions view for ticket types in a local board context.
Local ticket types can retain their own configuration and permissions context.
Create ticket menu showing concise Outcome, Practice, and Value ticket-type choices.
Ticket types also use the simple post-dot display name in the create-ticket menu.
03

Everyday experience

More consistent ticket interactions

Ticket and board-label interactions now follow the same pattern: double-click a ticket to open its details in the left-hand-side panel. This aligns tickets with board labels and supports future board widgets such as timers and dice rollers.

It is also now possible to create a ticket association directly on the board. Drag one ticket onto another, then choose the appropriate association from the menu. The previous left-hand-side-panel workflow remains available.

1

Drag a ticket to another ticket

A ticket being dragged onto another ticket on a FlowBoards board.
2

Drop to open the association menu

Association menu appearing when one ticket is dropped onto another.
3

Choose the link type

FlowBoards association menu with link types available for selection.
4

When the menu closes, the ticket that was dragged automatically returns to its original location.

04

Board visibility

Visualise associations between tickets

A new floating board control in the lower-right corner lets you visualise ticket associations on the active board area. Choose Show all links to reveal every visible association, or use Show links for active tickets to highlight connections while you hover over or select a ticket.

Floating toolbar with the first control highlighted by a red outline.
The red outline identifies the floating control in the lower-right corner of the board.
Link-visibility menu in FlowBoards showing three display options.
Select the preferred link-visibility mode.
FlowBoards board displaying all ticket links simultaneously.
Show all links reveals every association on the visible board area.
FlowBoards board highlighting associations for the active ticket.
Show links for active tickets highlights connections while you hover over or select a ticket.

How each association is displayed

Peer relationship

A green dotted line with a circle at each end.

Peer relationship shown as a green dotted ticket link with circles at each end.

Parent–child relationship

A blue line with an arrowhead pointing toward the parent.

Parent-child relationship shown as a blue ticket link pointing to the parent.

Blocker relationship

A red line; the blocked ticket is marked with a red crossbar at the end.

Blocker relationship shown as a red ticket link with a red crossbar on the blocked ticket.

Proxy ticket

A thin black dotted line with the arrowhead pointing back to the original ticket.

Proxy ticket relationship shown as a thin black dotted link pointing to the original ticket.
Enclosed duplicate relationships shown in the FlowBoards left-hand-side panel.
Enclosed duplicate relationships appear in the left-hand-side panel.
Note: enclosed duplicate relationships are displayed in the left-hand-side panel only; they are not visualised on the board.
05

Design controls

Limit classes of service by ticket type

Ticket type designs can now restrict the classes of service that are available for that particular type. In the Ticket Type design dialog, select the permitted classes from the organisation-wide set. At runtime, the Class of Service selector then shows only the appropriate options.

Ticket Type design dialog with classes of service configuration options.
Select the permitted classes of service within the ticket type design.
Runtime class-of-service picker showing available options.
At runtime, users see a focused list of valid service classes.
06

Smooth collaboration

More stable, responsive shared work

Release 1.8 also strengthens the shared working experience. When Show Remote Pointers is enabled, multiple screen pointers should be faster and smoother, and users can observe one another dragging tickets.

Screen synchronisation has been improved to provide a more consistent experience, better stability, and less need to refresh the browser when an expected update does not appear. Designer Mode stability has also been improved relative to the July 1.7 release.

  • Faster, smoother remote pointers
  • Visible ticket dragging between collaborators
  • More consistent cross-user screen sync
  • Improved Designer Mode stability
Release 1.8 lays the groundwork for locally owned workflows: teams can design, adapt, and collaborate with more independence while retaining the structure needed across a wider organisation.