Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node operation fetches tracked time entries for a specific repository from a Gitea instance. It is useful for project managers, developers, or team leads who want to monitor the amount of time logged against issues or tasks within a repository. For example, it can be used to generate reports on how much time was spent by different users on a repository's issues during a certain period.

Properties

Name Meaning
Owner The owner (user or organization) of the repository to query tracked times for.
Repo The name of the repository to retrieve tracked times from.
User Optional filter to show tracked times only for a specific user (typically an issue manager).
Since Filter to include only tracked times updated after this timestamp (RFC 3339 format).
Before Filter to include only tracked times updated before this timestamp (RFC 3339 format).
Page The page number of results to return (1-based pagination).
Limit The number of results per page (page size).

Output

The output contains JSON data representing the tracked time entries retrieved from the repository. Each entry typically includes details such as the user who logged the time, the amount of time tracked, timestamps, and possibly references to related issues or comments.

If binary data were involved (e.g., attachments), it would be summarized here, but this operation deals with JSON data only.

Dependencies

  • Requires connection to a Gitea instance via its API.
  • Needs an API authentication token configured in the node credentials to authorize requests.
  • The base URL of the Gitea server must be set in the credentials.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication errors.
    • Incorrect owner or repository names will result in "not found" errors.
    • Improperly formatted timestamps for Since or Before may cause request failures.
    • Pagination parameters (Page, Limit) set to zero or negative values might lead to unexpected results or errors.

  • Error Messages:

    • 401 Unauthorized: Check that the API key/token is valid and has sufficient permissions.
    • 404 Not Found: Verify that the owner and repo names are correct and exist on the Gitea server.
    • 400 Bad Request: Ensure that date filters follow RFC 3339 format and pagination parameters are positive integers.

Links and References

Discussion