Todos los comandos · internal
pm plan update-step
Update one declared Plan step.
Update one declared Plan step.
Uso
pm plan update-step <plan-id> <step>Argumentos
| <plan-id> | item id value. | obligatorio |
|---|---|---|
| <step> | string value. | obligatorio |
Opciones
| --step-title <value> | Step title for add-step / update-step | opcional |
|---|---|---|
| --step-body <value> | Step body text | opcional |
| --step-owner <value> | Step owner | opcional |
| --step-status <value> | Step status: pending|in_progress|completed|blocked|skipped|superseded | opcional |
| --step-evidence <value> | Step evidence text (used by update-step/complete-step) | opcional |
| --step-blocked-reason <value> | Step blocked reason (required when blocking) | opcional |
| --depends-on <value> | Pm item ids the step depends on (repeatable, csv-friendly) | opcional |
| --allow-multiple-active | Allow multiple steps to be in_progress at once | opcional |
| --file <value> | Step linked file path=<value>[,scope=project|global,note=<text>] (repeatable) | opcional |
| --test <value> | Step linked test command=<value>[,path=<value>,note=<text>] (repeatable) | opcional |
| --message <value> | Mutation message | opcional |
| --force | Force ownership override | opcional |
Ejemplos
pm plan update-step pm-a1b2 plan-step-001Consejos
- Applicable flags: --allow-multiple-active, --depends-on, --file, --force, --message, --step-blocked-reason, --step-body, --step-evidence, --step-owner, --step-status, --step-title, --test.