Actions37
- Issue Actions
- Lead Actions
- Opportunity Actions
- Account Actions
- Attendance Actions
- Personal Contact Actions
- Time Entry Actions
- User Actions
Overview
This node integrates with Easy Redmine to create a new issue within a specified project. It is useful for automating task and issue tracking workflows by programmatically adding issues based on dynamic inputs or triggers from other systems. For example, you could use this node to automatically log bugs reported via a form submission or to create tasks from customer support tickets.
Properties
| Name | Meaning |
|---|---|
| Subject | The title or subject of the issue being created. |
| Project Name or ID | The target project where the issue will be created. Choose from a list of accessible projects or specify an ID dynamically. |
| Create Fields | Additional optional fields to customize the issue creation: |
| - Assigned To ID | User ID to whom the issue will be assigned. |
| - Description | Detailed description of the issue. |
| - Done Ratio (0-100) | Percentage completion status of the issue. |
| - Due Date | Deadline date for the issue completion. |
| - Estimated Hours | Estimated time in hours to resolve the issue. |
| - Private Issue | Boolean flag indicating if the issue should be private. |
| - Parent Issue ID | ID of a parent issue if this is a sub-task. |
| - Priority Name or ID | Priority level of the issue, selectable from available priorities or specified by ID. |
| - Start Date | Starting date of the issue. |
| - Status Name or ID | Current status of the issue, selectable from available statuses or specified by ID. |
| - Tracker Name or ID | Tracker type for the issue, dependent on the selected project. |
| - Custom Fields | Collection of custom field IDs and their values to further customize the issue. |
Output
The node outputs JSON data representing the newly created issue entity as returned by the Easy Redmine API. This typically includes the issue's unique ID, subject, project association, status, priority, and any other fields set during creation. The output can be used downstream in workflows for logging, notifications, or further processing.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for Easy Redmine with appropriate permissions to create issues.
- The node uses the base URL configured in the credentials to connect to the Easy Redmine instance.
- Dynamic option loading depends on API calls to fetch accessible projects, priorities, statuses, and trackers.
Troubleshooting
Common Issues:
- Invalid or missing project ID: Ensure the project exists and the user has access.
- Permission errors: Verify that the API key has rights to create issues.
- Invalid field values: Check that numeric fields like done ratio are within valid ranges (e.g., 0-100).
- Missing required fields such as subject or project ID may cause the API to reject the request.
Error Messages:
- Errors returned from the API are captured and presented in the node output. If multiple errors occur, they are concatenated into a single message.
- If the node is set to continue on failure, errors will appear in the output JSON under an
errorproperty instead of stopping execution.