Redmine icon

Redmine

Consume Redmine API

Actions17

Issue → Get Many

AI-generated

Overview

This node operation retrieves multiple issues from a Redmine project management system. It is useful for scenarios where you need to fetch a list of issues based on various filters, sorting, and pagination options. For example, you can get all open issues assigned to a specific user, or fetch issues created within a certain date range, including related data like attachments or issue history.

Use Case Examples

  1. Fetch all issues assigned to the current user with their attachments included.
  2. Retrieve the first 50 open issues sorted by creation date in descending order.
  3. Get issues filtered by custom fields and specific project ID.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit.
Limit Maximum number of results to return when not returning all.
Offset Number of issues to skip in the response, useful for pagination.
Sort Column to sort the results by, with option to invert order by appending ':desc'.
Include Associated data to include in the response, such as attachments, children, journals, relations, and watchers.
Filters Various filters to narrow down the issues returned, including assigned user, author, category, creation and update dates, custom fields, status, priority, project, and more.
Options Additional options such as impersonating a user for the API request.

Output

JSON

  • id - The unique identifier of the issue.
  • subject - The subject or title of the issue.
  • description - Detailed description of the issue.
  • status - Current status of the issue (e.g., open, closed).
  • assigned_to - User to whom the issue is assigned.
  • priority - Priority level of the issue.
  • created_on - Date and time when the issue was created.
  • updated_on - Date and time when the issue was last updated.
  • attachments - List of attachments included if requested.
  • children - List of child issues if included.
  • journals - History of changes to the issue if included.
  • relations - Related issues if included.
  • watchers - Users watching the issue if included.

Dependencies

  • Redmine API key credential

Troubleshooting

  • Common issues include authentication errors due to invalid or missing API key. Ensure the API key is correct and has necessary permissions.
  • Filtering by dates requires correct date format; invalid dates may cause errors or empty results.
  • Using 'Return All' with a large dataset may lead to performance issues or timeouts; consider using pagination with 'Limit' and 'Offset'.
  • Impersonation requires admin API key; using a non-admin key will cause authorization errors.

Links

Discussion