baron_issue_move
Advance work items through the workflow using semantic roles, reconcile status conflicts, and block or unblock items with reasons.
Instructions
Move a work item through the workflow, or flag it. ops: transition (id, role, optional fields) — the semantic role layer, resolving an abstract role to the provider’s native state/column/label; on a provider whose transition carries a screen (Jira) a refusal with code TRANSITION_FIELDS_REQUIRED names the fields to pass back, verbatim, as fields; reconcile (id) — clear a role label the provider’s own state contradicts, commanding no role; block (id, reason — required) and unblock (id, optional reason), which set and clear an ORTHOGONAL flag and leave the role alone, so an item keeps the role it is blocked in.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"op": "<op>"
},
"name": "baron_issue_move"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | ||
| op | Yes | Which operation to perform. | |
| role | No | ||
| fields | No | Answers for the fields a gated transition demands, keyed by the provider-native names a TRANSITION_FIELDS_REQUIRED refusal reported. Pass only what the refusal asked for: a provider may reject a field its transition screen does not carry (Jira does). | |
| reason | No |