Actions15
Overview
This node integrates with the Redmine API to update existing issues in a Redmine project management system. It allows users to modify various attributes of an issue such as its subject, description, status, priority, assigned user, and custom fields. This is useful for automating issue tracking workflows, keeping issue data up-to-date, or synchronizing issue information from other systems.
Practical examples include:
- Automatically updating the status or notes of an issue when a related event occurs in another tool.
- Changing the assignee or due date of an issue based on external triggers.
- Adding private notes or comments programmatically during issue updates.
Properties
| Name | Meaning |
|---|---|
| Issue ID | The unique identifier of the issue to update (required). |
| Subject | The new subject/title of the issue. If left blank, the subject remains unchanged. |
| Notes | Comments or notes about the update to add to the issue. |
| Private Notes | Boolean flag indicating whether the notes should be private. |
| Additional Fields | A collection of optional fields to update, including: |
| - Assigned To ID | ID of the user to assign the issue to. |
| - Category ID | Category identifier for the issue. |
| - Custom Fields | One or more custom fields specified by their ID and value. |
| - Description | Detailed description of the issue. |
| - Due Date | Due date/time for the issue completion. |
| - Estimated Hours | Estimated time in hours to resolve the issue. |
| - Fixed Version ID | Target version or fixed version identifier. |
| - Parent Issue ID | ID of the parent issue if this is a sub-task. |
| - Priority ID | Priority level identifier of the issue. |
| - Start Date | Start date/time of the issue. |
| - Status ID | Current status identifier of the issue. |
| - Tracker ID | Tracker type identifier (e.g., bug, feature). |
Output
The node outputs JSON data representing the updated issue object returned by the Redmine API. This typically includes all the issue's current properties after the update has been applied.
If the operation fails and "Continue On Fail" is enabled, the output will contain an error message describing the failure.
No binary data output is produced by this node.
Dependencies
- Requires access to a Redmine instance URL.
- Requires an API key credential for authenticating requests to the Redmine API.
- The node expects these credentials to be configured within n8n prior to execution.
Troubleshooting
Common Issues:
- Invalid or missing Issue ID will cause the update to fail.
- Incorrect API key or URL configuration will result in authentication errors.
- Providing invalid field values (e.g., non-existent user IDs or status IDs) may cause the API to reject the update.
Error Messages:
- Authentication errors indicate problems with the API key or URL.
- Validation errors from the API usually specify which field caused the problem.
- Network or connectivity issues can cause request failures.
Resolutions:
- Verify that the Issue ID exists and is correct.
- Check API key and Redmine URL credentials.
- Ensure all referenced IDs (user, category, status, etc.) exist in the Redmine system.
- Use the "Continue On Fail" option to handle errors gracefully in workflows.