Actions15
Overview
This node integrates with the Redmine API to manage issues within Redmine projects. Specifically, the "Issue - Create" operation allows users to create new issues in a specified project by providing essential details such as the project ID and issue subject, along with optional additional fields like description, assigned user, priority, status, and custom fields.
Common scenarios for this node include:
- Automating issue creation from external systems or forms.
- Creating issues programmatically based on events or triggers in other workflows.
- Bulk creating issues with varying attributes using n8n workflows.
For example, a user could set up a workflow that listens for customer support requests and automatically creates corresponding issues in Redmine with relevant metadata.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project the issue belongs to (required). |
| Subject | The subject/title of the issue (required). |
| Additional Fields | Optional extra fields to specify more details about the issue: |
| - Assigned To ID | The ID of the user 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 add custom metadata to the issue. |
| - Description | A detailed description of the issue. |
| - Due Date | The due date for the issue (date and time). |
| - Estimated Hours | Estimated hours required to resolve the issue (number). |
| - Fixed Version ID | The fixed/target version ID for the issue. |
| - Parent Issue ID | The ID of a parent issue if this is a sub-task or related issue. |
| - Priority ID | The priority level ID of the issue. |
| - Start Date | The start date for the issue (date and time). |
| - Status ID | The current status ID of the issue. |
| - Tracker ID | The tracker ID categorizing the issue type (e.g., bug, feature). |
Output
The node outputs JSON data representing the created issue as returned by the Redmine API. This typically includes the issue's unique ID, subject, project association, status, and any other fields accepted during creation.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the issue, but this is not applicable for the create operation.
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 in n8n under a generic API key authentication method.
Troubleshooting
- Common Issues:
- Invalid or missing Project ID or Subject will cause the API to reject the request.
- Incorrect API key or URL will result in authentication errors.
- Providing invalid IDs for fields like Assigned To, Category, or Status may cause errors.
- Error Messages:
- Authentication failures usually indicate incorrect API key or URL configuration.
- Validation errors from Redmine will specify which field is invalid or missing.
- Resolution Tips:
- Verify all required fields are provided and correctly formatted.
- Confirm API key and Redmine URL are correct and accessible.
- Check that referenced IDs (users, categories, versions) exist in Redmine.