# Review a CLI task change before applying it

Illustrative planning brief; no automatic product import.

Illustrative case: a lead proposes raising one task’s priority. A mistaken key would affect unrelated work.

## Decision

Review the identified target and changed field; apply only within an authorized task-edit workflow.

## Owned work

- Verify the target
  - Owner role: Editor
  - Acceptance evidence: Current task detail matches the intended key and workspace.
- Inspect the proposed change
  - Owner role: Editor
  - Acceptance evidence: Dry-run evidence names the target, before/after field and warnings.
- Plan readback
  - Owner role: Reviewer
  - Acceptance evidence: The workflow identifies how applied and verified outcomes will be reconciled after an authorized write.

## Workflow

1. Read the intended task first.
2. Preview the same scoped change with --dry-run.
3. Make the apply decision separately and reconcile uncertain outcomes through reads.

## Judgment

This page runs nothing. A preview is not a saved transaction or proof that an update was applied.


## Illustrative update review

Target: the confirmed task, not a guessed key.
Proposed field: priority HIGH.
Current result: preview only.
Apply decision: requires the task owner’s authorized scope and later readback.


## Illustrative commands (not executed)

```text
teamboost tasks get TB-120 --org ORGANIZATION_ID --environment production --json --no-input
teamboost tasks update TB-120 --priority HIGH --dry-run --org ORGANIZATION_ID --environment production --json --no-input
```


## Workflow questions

### Does --json apply the change?

No. JSON changes output presentation. The write requires explicit --apply.

### Can I combine --dry-run and --apply?

No. The source CLI treats those modes as conflicting.

## Product connection

The source-backed TeamBoost CLI example separates preview, authorized application and readback. A rendered command here performs none of them.

Confirm account availability before adopting this manual outline.