Actions15
Overview
This node integrates with the Redmine API to manage issues, projects, and users within a Redmine instance. Specifically, for the Issue - Create operation, it 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, due date, priority, and custom fields.
Common scenarios where this node is beneficial include:
- Automating issue creation from external systems or workflows.
- Creating issues based on form submissions or error reports.
- Integrating Redmine issue tracking into broader automation pipelines.
For example, you could use this node to automatically create a new issue in Redmine whenever a customer support ticket is received, populating the issue with relevant details and assigning it to the appropriate user.
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 provide 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 a value, to set additional metadata on the issue. |
| - Description | A detailed description of the issue. |
| - Due Date | The due date for resolving the issue (date/time). |
| - Estimated Hours | Estimated time in hours to complete the issue. |
| - Parent Issue ID | The ID of a parent issue if this issue is a sub-task. |
| - Priority ID | The priority level ID of the issue. |
| - Start Date | The start date of the issue (date/time). |
| - Status ID | The status ID representing the current state of the issue. |
| - Tracker ID | The tracker ID categorizing the issue type (e.g., bug, feature). |
Output
The node outputs an array of JSON objects corresponding to the created issues. Each output item contains the full JSON response from the Redmine API for the created issue, which typically includes:
- The unique ID of the newly created issue.
- All provided fields and their values.
- Metadata such as creation timestamps and links.
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 issue operation.
Dependencies
- Requires access to a Redmine instance with API enabled.
- Needs an API key credential for authentication with the Redmine API.
- The node expects the base URL of the Redmine server and a valid API key to be configured in its credentials.
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 user, category, or tracker may cause errors.
- Error Messages:
- Authentication failures usually indicate incorrect API key or insufficient permissions.
- Validation errors from Redmine will specify which field is invalid or missing.
- Resolutions:
- Verify that the API key has sufficient permissions to create issues.
- Double-check all required fields are provided and correctly formatted.
- Ensure referenced IDs (users, categories, trackers) exist in the Redmine instance.