Easy Redmine icon

Easy Redmine

Easy Redmine Operations

Overview

This node integrates with Easy Redmine to create a new time entry record. It is useful for tracking the amount of time spent on projects or tasks within Easy Redmine, allowing users to log hours worked along with optional details such as comments, project association, activity type, user assignment, and custom fields.

Typical use cases include:

  • Automatically logging billable hours from external time tracking tools.
  • Recording time spent on specific projects or activities as part of workflow automation.
  • Adding detailed time entries with contextual information like comments or dates for reporting and analysis.

Properties

Name Meaning
Hours Number of hours spent (required).
Create Fields Optional additional fields to specify more details about the time entry:
  Comment A comment describing the time entry.
  Spent On The date when the time was spent, formatted as YYYY-MM-DD.
  Project Name or ID The project associated with the time entry. Can be selected from accessible projects or specified by ID.
  Activity ID Numeric ID representing the activity type related to the time entry.
  User ID Numeric ID of the user to whom this time entry belongs.
  Custom Fields Custom field values as pairs of ID and value, allowing further customization of the time entry.

Output

The node outputs JSON data representing the created time entry object as returned by the Easy Redmine API. This typically includes the time entry's unique identifier, hours logged, associated project and user IDs, comments, date spent, and any custom fields set.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Easy Redmine instance.
  • The node expects the base URL of the Easy Redmine domain to be configured in the credentials.
  • Uses Easy Redmine REST API endpoints to perform the creation of time entries.
  • The "Project Name or ID" property dynamically loads accessible projects via a method integrated into the node.

Troubleshooting

  • Common Issues:

    • Missing required "Hours" input will cause the operation to fail.
    • Invalid project or user IDs may result in API errors.
    • Date format errors if "Spent On" is not provided in YYYY-MM-DD format.
    • Insufficient permissions or invalid API credentials can cause authentication failures.
  • Error Messages:

    • Errors returned from the API are captured and presented in the node output.
    • If multiple errors occur, they are concatenated and shown in the error message.
    • To resolve errors, verify that all required fields are correctly filled, check API credentials, and ensure the user has permission to create time entries in the specified project.

Links and References

Discussion