Before You Start
You need a finished blueprint. Running the conversion without one returnsCAB blueprint not found. Generate the blueprint first.
Running the Conversion
1
Open the blueprint preview
Go to CAB and generate a blueprint if you have not already. See Step-by-Step Workflow.
2
Select Generate Tickets
The control sits in the preview toolbar. On a Web project the Tickets appear straight away. On a low-code project the work is handed to an external service and a banner reports progress while it runs.
3
Open Tickets
Every generated Ticket carries a Source of
CAB and a CAB Reference pointing back at the blueprint element it came from.What the Conversion Produces
On a Web project, the conversion reads the User Stories section and creates one Ticket per story. Each keeps the story’s title, its acceptance criteria, and its steps in the description, and each is stampedOpen, Medium priority, and a work type of User Story.
Nothing is merged or skipped. The count of Tickets matches the count of user stories in your blueprint.
On low-code projects the conversion is handled by different process which caters to the unique properties of each low code platform. As a result, the work types and the level of breakdown differ from what is described here.
Running It Again Replaces What Is There
Regenerating deletes every Ticket with a source ofCAB and creates a fresh set. Manual Tickets are untouched.
Anything you changed on a generated Ticket goes with it: status, assignee, priority, epic assignment, and any note you added. Selecting “Generate Tickets” when tickets already exist will result in the warning message below. Please note that this change is permanent and cannot be undone.
Tickets already exist from this Blueprint. Regenerating will replace all previously generated CAB tickets. Are you sure?
What You Should See
The Tickets list fills with entries numberedTKT-001 upward, each showing CAB in the Source column. Opening one shows the user story it came from, with its acceptance criteria and steps in the description and the originating element in CAB Reference.
Your Next Step
Generated Tickets arrive ungrouped. Epics put them in build order.Put your Tickets in build order
How Epics group work into waves, and how they are generated.
Adjust what came out
Editing, reassigning, and deleting Tickets by hand.