GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node operation resets the spent time on a specific merge request within a GitLab project. It is useful for project managers or developers who want to clear the logged time spent on a merge request, for example, to correct time tracking errors or start fresh time tracking for a new phase of work.

Use Case Examples

  1. Resetting spent time on a merge request to correct time tracking errors.
  2. Clearing logged time before starting a new review or development phase on a merge request.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the API request.
Authentication The authentication method used for the API request, typically an API key credential.
baseUrl The base URL of the GitLab instance to which the API request is sent.
Method The HTTP method used for the API request.
Path Parameters Parameters required in the API request path to identify the project and merge request.

Output

JSON

  • id - The ID of the merge request.
  • project_id - The ID of the project containing the merge request.
  • spent_time - The total spent time on the merge request after reset, typically zero.
  • message - A confirmation message indicating the spent time has been reset.

Dependencies

  • GitLab API authentication token or API key credential

Troubleshooting

  • Ensure the project ID and merge request IID are correct and exist in the GitLab instance.
  • Verify that the API authentication token has sufficient permissions to reset spent time on merge requests.
  • Check the base URL to ensure it points to the correct GitLab instance.
  • Common error: 404 Not Found - The project or merge request does not exist or is not accessible.
  • Common error: 401 Unauthorized - Authentication failed or token lacks required permissions.

Links

Discussion