Demo ·
Generate a playbook, with or without a ticket
Type the work you want automated. Generate YAML without creating a ticket first. Or check a box and create one in your default project.
Sprint 121 ships Create new playbook on the task list
- ITSM
- PLAYBOOK
What you are seeing
Playbook Review used to start only from a listed ticket. You picked a key. Generate fetched ITSM. GitHub and AAP followed that key. If the work was not already a ticket, you created one outside the SPA, waited for the list, then selected it.
Sprint 117 added comment and transition, but still deferred create. The SPA continued to have no “type what you want to automate next” entry point.
Sprint 121 ships Create new playbook… above the task list. Submit generates YAML from the typed summary. An optional checkbox also creates a task in your default ITSM project and then uses the ticket pipeline you already know.
| Before | After |
|---|---|
| Select a listed ticket or stop | Create new playbook… above the cards |
| Generate always fetches ITSM | Body-only generate from {summary, description?} |
| No in-app create | Optional create in the default project |
Every session is a real task_key | Unchecked uses a default PLAYBOOK- identity |
| GitHub / AAP follow the selected key | Ad-hoc: GitHub, AAP template, and ITSM transition stay disabled |
This is SPA only. After you take the appliance update, refresh the web UI so the field appears.
Generate from typed text
Type a summary. Leave the checkbox off. Submit.
The list selects a PLAYBOOK- session. The playbook panel shows New playbook plus the summary — not Task: PLAYBOOK-…. Generate does not call ITSM. Edit, refine, validate, and optional server draft still work. Save to GitHub, AAP template, transition, Open in ITSM, and check-playbook stay off.
If a ticket-keyed save, check, get, or AAP template request ever carries a PLAYBOOK- key, the server rejects it. That is a bug if the UI offered the button.
Optionally create a default-project task
Check Also create a task in {default_project_key}. Submit.
The SPA creates a task in your default project — not the project dropdown used to browse the list. Jira creates a Task. ServiceNow inserts short_description on the configured table. The list refreshes. The new key is selected. From there the existing ticket generate / details / GitHub / AAP path runs.
If default project is unset, the checkbox is disabled. Ad-hoc submit still works. Create errors stay on the form; they do not replace the list.
Why it matters
- For operators: type the work you want automated without creating a ticket first.
- For ticketed work: check the box and land a Task in the default project, then use the pipeline you already know.
- For the product: Playbook Review stays the ticket path. Ad-hoc autoincrements based on a default key.
Sprint 117 let you comment and transition a ticket. Sprint 121 lets you start without one.
Signed-in tour: UI features.
Try it (about five minutes)
Goal: generate YAML from typed text, then optionally create a default-project task and use the ticket pipeline.
1. Ad-hoc generate
Type a summary in Create new playbook…. Leave Also create a task… unchecked. Submit.
Confirm the panel header is New playbook plus your summary. Confirm YAML appears. Confirm Save to GitHub, AAP template, and transition stay disabled.
2. Optional default-project create
Check Also create a task in {your default project}. Type a summary. Submit.
Confirm a new row appears on page one. Confirm the playbook panel uses that real key. Generate, then Save to GitHub / AAP template as you would for any listed ticket.
Still open
On purpose, this slice does not add:
- MCP create-task or ad-hoc generate from the IDE
- Create in the dropdown-selected project
- An issue-type picker, or later bind of ad-hoc YAML onto a ticket
PLAYBOOK-files as a supported GitHub path- SPA Launch
post_aap_launch stays MCP-only with policy + confirm:true. The web UI still does not launch AAP jobs.
Available to customers
Will be available in the upcoming v2026.8.2 release. After you take the appliance update, refresh the web UI so Create new playbook… appears above the task cards.