Example
Turn a whiteboard into tickets and track the build
Once a whiteboard is published, a developer lead turns its shapes into tickets, links each shape to what was built for it (a system, an API, a logic, a flow) and follows the build progress until every shape is done.
You will build
- A ticket per shape, linked both ways
- Each shape linked to what it became
- Build progress from to do to done
Part 1: Make the tickets
- 1.
Open the Refund requestwhiteboard and click Start building. The status reads In development. - 2.
Click Refund form, then Shift-clickPick the order and the reason,Payments refunds the cardandSend the refund email. - 3.
Right-click one of them → Create tickets for 4 shapes… → Create tickets.
Check:
Part 2: Link shapes to what was built
- 1.
Right-click Payments refunds the card→ Link to what it became…. In Link to…, find the API or the logic that does it and pick it. - 2.
Link Refund formto the website’s logic, and the whole journey to its flow once it exists. - 3.
In the side panel, set each shape’s Build status: To do, In progress or Done. A ticket closing moves it too.
Part 3: Follow the progress
- 1.
Click Build progress. Every shape is coloured by its status, and the header shows how many are done. - 2.
Right-click a shape → Discuss in chat… to talk about it in the whiteboard’s own channel, with a link back to the shape. - 3.
When every shape is done, a green banner offers Mark the whiteboard done.
Check:
