Actions37
- Issue Actions
- Lead Actions
- Opportunity Actions
- Account Actions
- Attendance Actions
- Personal Contact Actions
- Time Entry Actions
- User Actions
Overview
The node integrates with Easy Redmine to perform various operations on its resources. Specifically, for the Issue resource and the Get Many operation, it retrieves multiple issues from Easy Redmine based on a specified query filter. This is useful when you want to fetch a list of issues matching certain criteria, such as status, priority, or custom filters defined in Easy Redmine.
Common scenarios include:
- Fetching all open issues assigned to a team.
- Retrieving issues filtered by a saved query for reporting or dashboard purposes.
- Paginating through large sets of issues for batch processing or synchronization.
Example: You might use this node to get all issues from a specific project that are due this week, then process them further in your workflow (e.g., send notifications or update statuses).
Properties
| Name | Meaning |
|---|---|
| EasyRedmine Issues Query Name or ID | Selects a predefined query to filter which issues to retrieve. You can choose from a dropdown list of saved queries or specify a query ID via expression. |
| Return All | Boolean flag indicating whether to return all matching issues or limit the number of results. |
| Offset | Number specifying the starting point in the result set (used when not returning all). |
| Limit (1-100) | Maximum number of issues to return when not returning all. Must be between 1 and 100. |
Output
The node outputs an array of JSON objects representing the retrieved issues. Each object corresponds to one issue and contains its properties as returned by Easy Redmine's API, such as issue ID, subject, status, priority, assignee, and other relevant fields.
If binary data were involved (not applicable here), it would be summarized accordingly, but this operation deals solely with JSON data.
Dependencies
- Requires an active connection to an Easy Redmine instance.
- Needs an API authentication token configured in the node credentials to authorize requests.
- The base URL for the Easy Redmine API must be set in the credentials.
- The node uses Easy Redmine's REST API endpoints to fetch issues.
Troubleshooting
- No issues returned: Verify that the selected query exists and returns results in Easy Redmine. Also, check if the API credentials have sufficient permissions.
- Authentication errors: Ensure the API key/token is valid and has access rights to read issues.
- Limit and offset misuse: When
Return Allis false, ensureLimitis within 1-100 andOffsetis non-negative; otherwise, the API may reject the request. - API rate limits or timeouts: Large queries might hit API limits; consider using pagination (
Return Allfalse with offset/limit) to mitigate. - Error messages containing "errors": These usually come from the API response; review the error details for invalid parameters or permission issues.