Easy Redmine icon

Easy Redmine

Easy Redmine Operations

Actions37

Overview

This node integrates with Easy Redmine to update an existing time entry record. It allows users to modify details such as the number of hours spent, comments, date of work, associated project, activity, user, and custom fields for a specific time entry identified by its ID.

Common scenarios include:

  • Correcting or adjusting logged time entries after initial input.
  • Adding additional context or comments to a time entry.
  • Changing the project or activity linked to a time entry.
  • Updating custom metadata related to time tracking.

Practical example:

  • A project manager realizes that a developer logged incorrect hours on a task yesterday. Using this node, they can update the "Hours" field and add a clarifying comment without creating a new time entry.

Properties

Name Meaning
Time Entry ID The unique numeric identifier of the time entry to update.
Update Fields Collection of fields to update in the time entry:
- Hours Number of hours spent (numeric).
- Comment Text comment describing the time entry.
- Spent On Date when the time was spent, formatted as YYYY-MM-DD.
- Project Name or ID Selectable list or expression to specify the project associated with the time entry.
- Activity ID Numeric ID of the activity linked to the time entry.
- User ID Numeric ID of the user who owns the time entry.
- Custom Fields Multiple custom fields, each with an ID and string value, allowing extended metadata updates.

Output

The node outputs JSON data representing the updated time entry object as returned by the Easy Redmine API. This typically includes all standard fields of the time entry, reflecting the changes made.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to an Easy Redmine instance via an API key credential.
  • The node expects the base URL of the Easy Redmine server to be configured in the credentials.
  • The "Project Name or ID" field dynamically loads accessible projects from the connected Easy Redmine account.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Time Entry ID will result in errors.
    • Incorrect date format for "Spent On" may cause validation failures.
    • Insufficient permissions for the API key to update time entries will lead to authorization errors.
    • Specifying invalid project or activity IDs not accessible by the user can cause failures.

  • Error messages:

    • Errors returned from the API are captured and presented; if multiple errors occur, they are concatenated into a single message.
    • If the node is set to continue on failure, error details are included in the output JSON under an error property.
    • To resolve errors, verify the correctness of IDs, date formats, and API credentials' permissions.

Links and References

Discussion