pub const ISSUE_MOVE: &str = "\
Move an issue to another queue.
```
ytcli issue move PROJ-1 --to OPS --yes
ytcli issue move PROJ-1 --to OPS --keep-fields --yes
ytcli issue move PROJ-1 --to OPS --dry-run
ytcli issue move PROJ-1 PROJ-2 --to OPS --yes
```
**The key changes.** `PROJ-1` becomes `OPS-N`, every link and every note that
referred to the old key now refers to a redirect, and no request moves it back
to the key it had. That is why `--yes` is required for a single issue here,
where an ordinary update is not.
Tracker drops fields the target queue does not define. `--keep-fields` carries
them across instead. `--initial-status` restarts the issue at the beginning of
the target queue's workflow rather than keeping the status it has, which
matters when the two workflows do not share one.
The new key is printed, and is the only thing that still addresses the issue.
Several issues go in one request, and the confirmation names every one of them
before anything moves. The answer is then a tally — `changed N of M` — and the
id of the change, with a reason for each issue that did not move; `--no-wait`
returns that id immediately instead of waiting. A list spanning two
organisations cannot be one request, so it is moved one issue at a time and
stops at the first failure.";