Easy Redmine icon

Easy Redmine

Easy Redmine Operations

Actions37

Overview

This node integrates with Easy Redmine to update an existing issue. It allows users to modify various attributes of an issue such as its subject, description, status, priority, assigned user, dates, progress, and custom fields. This is useful in workflows where issue tracking needs to be automated or synchronized with other systems, for example:

  • Automatically updating issue status or progress based on external triggers.
  • Changing the assignee or due date when certain conditions are met.
  • Adding detailed descriptions or custom field values programmatically.

Properties

Name Meaning
Issue ID The numeric identifier of the issue to update.
Update Fields A collection of optional fields to update on the issue:
- Subject The new subject/title of the issue.
- Project Name or ID The project to which the issue belongs. Can be selected from a list or specified by ID via expression.
- Assigned To ID Numeric ID of the user to assign the issue to.
- Description Detailed description text for the issue.
- Done Ratio (0-100) Percentage completion of the issue.
- Due Date The due date/time for the issue.
- Estimated Hours Estimated time in hours to complete the issue.
- Private Issue Boolean flag indicating if the issue should be private.
- Parent Issue ID Numeric ID of a parent issue, if this issue is a subtask.
- Priority Name or ID Priority level of the issue, selectable from available priorities or specified by ID.
- Start Date The start date/time 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 of the issue, selectable from available trackers depending on project and issue context.
- Custom Fields Multiple custom fields can be updated by specifying their ID and corresponding value.

Output

The node outputs JSON data representing the updated issue entity as returned by the Easy Redmine API. This typically includes all current properties of the issue after the update, such as IDs, subject, status, assigned user, dates, progress, and any custom fields.

If the node supports binary data output (not indicated here), it would summarize that binary data corresponds to attachments or related files, but this node focuses on JSON issue data.

Dependencies

  • Requires an API key credential for Easy Redmine with appropriate permissions to update issues.
  • Needs the Easy Redmine domain URL configured in credentials.
  • Uses internal methods to load options dynamically for projects, priorities, statuses, and trackers.
  • Relies on n8n's HTTP request capabilities and error handling framework.

Troubleshooting

  • Common Issues:

    • Invalid or missing Issue ID will cause failure to locate the issue.
    • Insufficient permissions or invalid API key may result in authorization errors.
    • Providing invalid values for fields like dates or IDs not matching existing entities can cause API errors.
    • Dependency on dynamic option loading means if the project or other referenced entities do not exist or are inaccessible, updates may fail.

  • Error Messages:

    • Errors returned from the API are captured and presented; they often include validation messages or permission denials.
    • If "continue on fail" is disabled, the node execution stops on first error; enabling it allows processing subsequent items.
    • Common resolution steps include verifying credentials, ensuring correct IDs, and validating field formats.

Links and References

Discussion