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