shipper_set_priority

shipper_set_priority

Set a Shipper-managed issue’s store-authoritative scheduling priority. Returns structured applied versus already-set results; when issue mirroring is enabled, Shipper projects the matching GitHub priority label after committing the local store.

When to use

Use this when an agent must change the priority Shipper scheduling actually reads. The local issue-state store is authoritative: mirror-on repositories commit there first and then project the matching GitHub priority label, while store-only repositories succeed without an issue-side GitHub mutation. Optional mirror_pending records automatic scheduling state, deadline, stopped cause and recovery actions until verified delivery. Applied and already-set describe local-store outcomes. The structured outcome distinguishes a real change (applied) from an idempotent retry (already-set) and always includes both the resulting and previous priority. After adopting a pull request, use the backing issue identity returned by shipper_adopt rather than the PR reference.

Behavior hints

• idempotentHint: true — Retrying the same call is expected to be safe once the target state is reached.
• openWorldHint: true — The tool reaches GitHub or other external systems outside the MCP server.

Input schema

Name	Type	Required	Default	Description
issue	integer | string	yes	-	Shipper issue reference. S# (GitHub #) accepts ordinary surrounding whitespace and requires the current mirror. Bare numbers are Shipper local IDs first; S# is accepted; gh: and # explicitly target a mapped GitHub issue; GitHub issue URLs are accepted. Responses return S# first with GitHub # second when mapped.
priority	enum: high, normal, low	yes	-	Resulting scheduling priority: high, normal, or low.

Output schema

Name	Type	Required	Default	Description
mirror_pending	array	no	-	-
outcome	enum: applied, already-set	yes	-	Whether the requested priority changed the authoritative local store.
priority	enum: high, normal, low	yes	-	Resulting authoritative scheduling priority.
previous_priority	enum: high, normal, low	yes	-	Authoritative scheduling priority before this call.

Example call

{
  "issue": "S#42",
  "priority": "high"
}

Example result

{
  "content": [
    {
      "type": "text",
      "text": "Resolved issue: S#42 (GitHub #123): Generate MCP tool reference pages\nS#42 (GitHub #123) priority set to high."
    }
  ],
  "structuredContent": {
    "outcome": "applied",
    "priority": "high",
    "previous_priority": "normal"
  }
}

Error modes

• Local issue-state replica not initialized: Local issue-state replica is not initialized for owner/repo. Run shipper issue reconcile --repair to import/reconcile it.
• Local issue-state replica present but not fully reconciled: Local issue-state replica is present but not fully reconciled for owner/repo. Run shipper issue reconcile --repair to import/reconcile it.
• Local issue-state replica schema unsupported: Local issue-state replica has an unsupported schema for owner/repo. Locally reconstructable older replicas migrate automatically on first issue-state access. Run shipper issue reconcile --repair for supported local-ID V3 blocker imports requiring GitHub data or ordinary current-store repair. Numeric snapshots in issues/<GitHub-number>.json or _pending-blocker-imports/legacy/<GitHub-number>.json refuse the entire store, listing all affected records and leaving existing local issue state unchanged. This Shipper version no longer migrates GitHub-number issue snapshots. Use a Shipper release from before this change to migrate the store before retrying this version. Fresh or recreated stores retain initial blocked-state imports and interrupted-import retries after metadata becomes reconciled; local-ID V3 stored blocker lists can complete locally in store-only mode.
• Local issue-state replica malformed: Local issue-state replica is malformed for owner/repo. Run shipper issue reconcile --repair to import/reconcile it.
• Running issue-state reader stale: The running Shipper issue-state reader is stale for owner/repo: observed store schema v10 is newer than supported schema v9. Restart or reconnect the MCP client and server. If a freshly launched server remains incompatible, update the installed Shipper release or rebuild the source checkout before reconnecting. Preserve the issue-state store unchanged.
• Unknown or unmanaged issue: Could not find Shipper issue S#. / S# (GitHub #) is not in the shipper workflow.
• Pull request reference: PR # is a pull request, not a Shipper issue. When known, the error continues: Set priority on its backing issue S# (GitHub #).
• Closed issue: S# is closed. Mirrored records include (GitHub #<issue>); closed issues are rejected in both mirror modes before any priority write.
• Authoritative local-store failure: Local issue-state priority update failed: .
• Post-commit GitHub projection failure: The authoritative local priority was committed, but the GitHub label projection failed. Run shipper issue reconcile --repair; a retry reports already-set from the store.

Related tools

• shipper_get_issue
• shipper_adopt