chain_issues
Create sequential relations between multiple Redmine issues in one call, enforcing execution order without manual per-pair setup.
Instructions
Chain a list of issues in sequence.
The first relates to the second, the second to the third, and so on. Useful for enforcing the execution order of a set of tasks without opening the relations form once per pair.
Args: issue_ids: IDs in the desired order (e.g. [22, 25, 49, 51]). relation_type: same set as create_issue_relation. Defaults to 'precedes'. delay: gap in days; only applies to 'precedes' and 'follows'.
Does not abort on the first error: it tries every pair and reports each result. Safe to re-run — Redmine rejects a duplicate relation with 422, which shows up as an error for that pair without affecting the others.
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": {
"issue_ids": "<issue_ids>"
},
"name": "chain_issues"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| delay | No | ||
| issue_ids | Yes | ||
| relation_type | No | precedes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |