GiteaInstall

Overview

This node operation allows you to add time tracking information to a specific issue in a repository hosted on a Gitea instance. It is useful for teams or individuals who want to log the amount of time spent working on an issue directly within their issue tracking system, helping with project management, billing, or productivity analysis.

Practical examples include:

• Logging hours spent fixing a bug.
• Tracking time dedicated to feature development.
• Recording time spent on code review or testing related to an issue.

Properties

Output

The node outputs JSON data representing the response from the Gitea API after adding the time entry to the issue. This typically includes confirmation details such as the updated issue information or the newly created time record.

No binary data output is involved in this operation.

Dependencies

• Requires access to a Gitea instance with API enabled.
• Needs an API authentication token credential configured in n8n to authorize requests.
• The base URL of the Gitea server must be set in the credentials.
• The node uses the Gitea REST API endpoint /api/v1 to perform operations.

Troubleshooting

• Common issues:

  • Incorrect repository owner or repo name can cause "Not Found" errors.
  • Invalid or missing API credentials will result in authentication errors.
  • Providing an invalid issue index may lead to failure in locating the issue.
  • Time value must be a positive number; zero or negative values might be rejected.

• Error messages and resolutions:

  • 401 Unauthorized: Check that the API key/token is valid and has sufficient permissions.
  • 404 Not Found: Verify the owner, repo, and issue index are correct.
  • 400 Bad Request: Ensure the time is provided in seconds and required fields are not empty.
  • 500 Internal Server Error: Could indicate server-side problems; retry later or check server logs.

Links and References

• Gitea API Documentation
• Gitea Issue Time Tracking
• n8n Documentation on Credentials