Actions66
- Branch Actions
- File Actions
- Group Actions
- Issue Actions
- Merge Request Actions
- Pipeline Actions
- Project Actions
- Raw API Actions
- Release Actions
- Tag Actions
Overview
This node operation allows you to close an issue in a GitLab project. It is useful when you want to programmatically mark an issue as resolved or no longer active directly from your workflow automation.
Typical scenarios include:
- Automatically closing issues after a successful deployment.
- Closing issues based on external triggers or conditions in your workflow.
- Managing issue lifecycle without manual intervention in the GitLab UI.
For example, you can configure this node to close a specific issue by its internal ID (IID) within a project, helping maintain streamlined project management and automated issue tracking.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose between using saved credentials ("Credential") or providing custom connection details ("Custom"). |
| GitLab Server | Base URL of your GitLab instance, e.g., https://gitlab.com. Used only if "Custom" authentication is selected. |
| Access Token | Personal access token with API permissions for GitLab. Used only if "Custom" authentication is selected. |
| Project Owner | Namespace or owner of the project. Ignored if "Project ID" is set. Used only if "Custom" authentication is selected. |
| Project Name | Project slug or name. Ignored if "Project ID" is set. Used only if "Custom" authentication is selected. |
| Project ID | Numeric project ID. Takes precedence over owner and name if provided. Used only if "Custom" authentication is selected. |
| Issue IID | The internal ID number of the issue to close. Must be a positive integer. This is required. |
Output
The node outputs the JSON response returned by the GitLab API after closing the issue. This typically includes the updated issue object with fields such as:
id: Unique identifier of the issue.iid: Internal issue ID.state: The new state of the issue, which will be"closed"after this operation.- Other metadata about the issue like title, description, labels, author, timestamps, etc.
The output is structured as an array of JSON objects, each representing the closed issue's data.
No binary data is produced by this operation.
Dependencies
- Requires access to a GitLab instance via its REST API.
- Needs either saved credentials or custom authentication details including:
- GitLab server URL (default: https://gitlab.com)
- A personal access token with appropriate API permissions to modify issues.
- No additional external dependencies beyond standard HTTP requests to GitLab API.
Troubleshooting
- Invalid or missing Issue IID: The issue number must be a positive integer. Ensure the "Issue IID" property is correctly set.
- Authentication errors: If using custom authentication, verify that the access token is valid and has sufficient permissions to update issues.
- Project identification issues: When using custom authentication, ensure that either the numeric project ID is provided or both project owner and project name are correctly specified.
- API request failures: Network issues or incorrect GitLab server URLs can cause failures. Confirm the server URL and network connectivity.
- Permission denied: The access token must have rights to modify issues in the target project.
Common error messages usually come from the GitLab API and may indicate unauthorized access, resource not found, or validation errors. Review the error message details and adjust credentials or parameters accordingly.
Links and References
This summary covers the "Close" operation for the "Issue" resource in the GitLab Extended node based on the provided source code and properties.