Actions15
Overview
This node integrates with the Redmine API to manage issues, projects, and users. Specifically, for the Issue - Update operation, it updates an existing issue in Redmine by modifying its properties such as assignment, category, description, due date, priority, status, and custom fields.
Common scenarios where this node is beneficial include:
- Automating issue tracking workflows by updating issue details based on external triggers.
- Synchronizing issue data from other systems into Redmine.
- Bulk updating multiple issues programmatically without manual intervention.
For example, you could use this node to update the status and assigned user of an issue when a related task in another system is completed.
Properties
| Name | Meaning |
|---|---|
| Issue ID | The unique identifier of the issue to update. |
| Additional Fields | A collection of optional fields to update on the issue: |
| - Assigned To ID | The user ID to assign the issue to. |
| - Category ID | The category ID of the issue. |
| - Custom Fields | One or more custom fields, each with an ID and value, to set on the issue. |
| - Description | The textual description of the issue. |
| - Due Date | The due date/time for the issue completion. |
| - Estimated Hours | The estimated number of hours required to resolve the issue. |
| - Parent Issue ID | The ID of the parent issue if this issue is a subtask. |
| - Priority ID | The priority level ID of the issue. |
| - Start Date | The start date/time of the issue. |
| - Status ID | The current status ID of the issue (e.g., open, closed). |
| - Tracker ID | The tracker ID categorizing the issue type (e.g., bug, feature). |
Output
The node outputs an array of JSON objects representing the updated issue(s) after the operation completes. Each output item contains the updated issue data as returned by the Redmine API.
If an error occurs during processing and "Continue On Fail" is enabled, the output will contain an object with an error field describing the failure for that particular input item.
No binary data is produced by this node.
Dependencies
- Requires access to a Redmine instance via its REST API.
- Needs an API key credential for authentication with Redmine.
- The node expects the Redmine base URL and API key to be configured in the credentials.
Troubleshooting
- Common Issues:
- Invalid or missing Issue ID will cause the update to fail.
- Incorrect API key or insufficient permissions can result in authentication errors.
- Providing invalid field values (e.g., non-existent user IDs or status IDs) may cause API errors.
- Error Messages:
- Errors returned from the Redmine API are passed through; typical messages include "Not Found" for invalid issue IDs or "Unauthorized" for authentication failures.
- Resolution Tips:
- Verify the Issue ID exists in Redmine before attempting an update.
- Ensure the API key has sufficient rights to modify issues.
- Validate all additional fields against Redmine's configuration (e.g., valid user IDs, categories).