GiteaInstall

Overview

This node interacts with the Gitea API to reset the tracked time on a specific issue within a repository. It is useful in scenarios where you want to clear or reset the time tracking data associated with an issue, for example, when starting a new work period or correcting previously logged time.

Practical examples:

• A project manager wants to reset the tracked time on an issue before a new sprint begins.
• A developer needs to clear incorrect time entries on an issue to maintain accurate records.

Properties

Output

The node outputs JSON data representing the result of the reset time operation on the specified issue. This typically includes confirmation that the tracked time has been reset and may include updated issue details reflecting the cleared time tracking.

No binary data output is involved.

Dependencies

• Requires an API key credential to authenticate with the Gitea instance.
• Needs the base URL of the Gitea server configured in the credentials.
• Depends on the Gitea REST API being accessible and the user having appropriate permissions to modify issues.

Troubleshooting

• Common Issues:

  • Incorrect repository owner or name can cause "not found" errors.
  • Providing an invalid issue index may result in errors or no action.
  • Insufficient permissions on the Gitea server will prevent resetting time.
  • Network connectivity problems can cause request failures.

• Error Messages:

  • 404 Not Found: Check if the owner, repo, and issue index are correct.
  • 401 Unauthorized: Verify that the API key credential is valid and has necessary scopes.
  • 400 Bad Request: Ensure all required parameters are provided and correctly formatted.

Resolving these usually involves verifying input properties, checking credentials, and confirming API access rights.

Links and References

• Gitea API Documentation - Issues
• Gitea Official Website