redmine_bulk_update_issues
Apply the same field updates to many Redmine issues in one call, including status, priority, assignee, custom fields, and dates. Returns counts of succeeded, failed, and skipped issues.
Instructions
Apply the same field updates to many issues in one call.
Args:
issue_ids: list of numeric issue ids (≤ 100 per call).
subject, description, status, priority, assigned_to_id, notes:
same semantics as redmine_update_issue — at least one
must be supplied.
custom_fields: raw custom-field entries (list of {"id": N, "value": "..."} dicts). Merged into each issue's PUT.
difficulty: convenience for the Difficulty custom field
("Unclassified" / "Easy" / "Normal" / "Hard").
held: True marks every issue as held. False (default)
means unchanged.
held_until: ISO-8601 date for the Held Until custom field.
due_date: ISO-8601 date to set on every issue.
start_date: ISO-8601 date to set on every issue.
done_ratio: 0-100 progress percent; -1 (default) means
unchanged.
stop_on_error: if True, halt at the first failure (remaining
ids land in skipped); otherwise best-effort across the
whole batch.
Returns {total, succeeded, failed, skipped}. Honors
REDMINE_MCP_READ_ONLY. Sequential — Redmine has no batch endpoint.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| held | No | ||
| notes | No | ||
| status | No | ||
| subject | No | ||
| due_date | No | ||
| priority | No | ||
| issue_ids | Yes | ||
| difficulty | No | ||
| done_ratio | No | ||
| held_until | No | ||
| start_date | No | ||
| description | No | ||
| custom_fields | No | ||
| stop_on_error | No | ||
| assigned_to_id | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |