GitLab API

GitlabTool
Join our community

Actions905

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 tracked time spent on a merge request, for example, if the time tracking was incorrect or needs to be restarted. Practical use cases include time management corrections and project tracking adjustments in GitLab.

Use Case Examples

  1. Resetting the spent time on a merge request after a task was re-estimated.
  2. Clearing time tracking data on a merge request before starting a new phase of work.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
Authentication Type of authentication used, default is GitLab API key.
baseUrl Base URL of the GitLab instance, default is https://gitlab.com.
Method HTTP method to use for the request, default is GET but POST is used for this operation.
Path Parameters Parameters required in the request path to identify the project and merge request.

Output

JSON

  • id - The ID or URL-encoded path of the project.
  • merge_request_iid - The internal ID of the merge request.
  • reset_spent_time_response - Response from the API confirming the spent time reset on the merge request.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the project ID and merge request IID are correctly provided and exist in the GitLab instance.
  • Verify that the API key has sufficient permissions to reset spent time on merge requests.
  • Check the base URL if using a self-hosted GitLab instance to ensure it is correct.
  • Common error: 404 Not Found - The project or merge request does not exist or is not accessible with the provided credentials.
  • Common error: 401 Unauthorized - Authentication failed, check the API key or token.

Links

Discussion