Ticket Lifecycle Workflow
Use the CLI to manage ticket context, plans, changes, and delivery artifacts.
Prerequisites
- CLI installed and authenticated
- Access to the GitHub repository for your work
Start and Plan
Start a ticket to prepare its local context and branch:
wseng start-ticket <ticket-key>
Ticket identifiers are GitHub issue identifiers, such as ws-eng-cli/123. Create a blank plan or load an existing plan, then save your changes:
wseng ws create-blank-plan
wseng ws load-plan <ticket-key>
wseng ws save-plan
Work and Finish
Commit code and update ticket artifacts as needed:
wseng commit
wseng generate-changelog
wseng record-demo
wseng finish
Use wseng git-sync to synchronize local branches. Use wseng fetch-context or wseng ws load-context to load context. The finish command publishes the local output and offers the ticket transition.
Ticket Fields
The CLI can update ticket fields and comments through its workflow commands. wseng tk update-computed-fields explicitly refreshes computed fields. Board status changes do not automatically refresh computed fields.
RCA Workflow
For a bug that needs root-cause documentation, create or edit .context/rca/rca.yaml, then save it:
wseng ws create-blank-rca
wseng ws save-rca
See the RCA workflow for the file structure.
QC
The registered QC commands are wseng qc start, wseng qc pass, and wseng qc fail. Use them for the ticket's review process.
