Move Issues To Backlog
jira.move_issues_to_backlog
ActionBusiness appsconnection required
Calls the Jira Cloud REST API with the connection's email and API token.
Move issues out of their sprint and back into a board's backlog.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Jira
- Secret shape
- {"email", "api_token"}
- Config it needs
- domain
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
board_id Numeric id of the board whose backlog the issues move to. | string | Yes | — | — | 10021 |
issues Comma-separated issue keys or ids to move, at most 50 per call. | string | Yes | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"board_id": "10021"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True when Jira accepted the call. | boolean | — |
board_id The board the issues were moved to. | string | — |
moved How many issue keys were sent. | number | — |
{
"board_id": "",
"moved": 0,
"ok": false
}Notes
- Boards, sprints and the backlog are Jira Software's API (/rest/agile/1.0), not the platform API — they exist only on a site with Jira Software, and only company-managed and team-managed software projects have boards.
- Jira caps one call at 50 issues; more than that is refused here.
See Move Issues To Backlog run in a workflow.
In a technical demo we add the Jira connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.