Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node operation retrieves tracked time entries associated with a specific issue in a repository hosted on a Gitea instance. It is useful for project managers, developers, or team leads who want to monitor the amount of time logged against particular issues for tracking progress, billing, or reporting purposes.

Typical use cases include:

  • Extracting time tracking data for an issue to analyze how much effort has been spent.
  • Filtering tracked times by user or date ranges to generate detailed reports.
  • Paginating through large sets of time entries when many have been logged.

Properties

Name Meaning
Owner The owner (user or organization) of the repository containing the issue.
Repo The name of the repository where the issue exists.
Index The index (number) identifying the specific issue within the repository.
User Optional filter to retrieve tracked times only for a specific user (requires appropriate rights).
Since Optional timestamp (RFC 3339 format) to show only tracked times updated after this time.
Before Optional timestamp (RFC 3339 format) to show only tracked times updated before this time.
Page Optional page number for paginated results (1-based).
Limit Optional number of results per page (page size).

Output

The output JSON contains an array of tracked time entries related to the specified issue. Each entry typically includes details such as the user who logged the time, the amount of time tracked, timestamps, and possibly comments or descriptions associated with each time entry.

If binary data were involved (e.g., attachments), it would be summarized here, but this operation deals solely with JSON data representing time tracking records.

Dependencies

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

Troubleshooting

  • Common Issues:

    • Incorrect owner, repo, or issue index values will result in no data or errors.
    • Insufficient permissions may prevent access to time tracking data, especially when filtering by user.
    • Invalid date formats for Since or Before parameters can cause request failures.
    • Pagination parameters (Page, Limit) set incorrectly might return empty results or errors.

  • Error Messages:

    • "Not Found" or similar indicates the issue or repository does not exist or is inaccessible.
    • "Unauthorized" or "Forbidden" suggests missing or invalid API credentials or insufficient permissions.
    • "Bad Request" may indicate malformed query parameters, such as invalid timestamps.

To resolve these, verify all input parameters, ensure correct API credentials are used, and confirm that the authenticated user has necessary access rights.

Links and References

Discussion