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 reopens a previously closed issue in a GitLab project. It is useful when an issue that was mistakenly closed or needs further attention must be reopened to continue tracking and resolving it.
Typical scenarios include:
- Reopening a bug report after new information is discovered.
- Resuming work on a feature request that was prematurely closed.
- Managing issue lifecycle programmatically within automated workflows.
For example, you can automate reopening issues based on external triggers such as customer feedback or test failures.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose between using saved credentials ("Credential") or specifying 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 authentication. 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 reopen. Must be a positive integer. This is required. |
Output
The output is a JSON object representing the reopened issue as returned by the GitLab API. It typically includes fields such as:
id: Unique identifier of the issue.iid: Internal issue number.title: Title of the issue.description: Detailed description.state: Current state of the issue (should be"opened"after reopening).- Other metadata like labels, assignees, timestamps, etc.
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 parameters including a valid personal access token with appropriate API permissions.
- No additional external services are required beyond GitLab itself.
Troubleshooting
- Invalid or missing Issue IID: The issue number must be a positive integer. Ensure the correct issue IID is provided.
- Authentication errors: Verify that the access token or credentials have sufficient permissions to modify issues.
- Project identification issues: When using custom authentication, ensure the project is correctly identified either by numeric ID or by owner and name.
- API errors from GitLab: These may occur due to network issues, permission problems, or invalid parameters. Check the error message for details and verify API access.
- Empty or malformed responses: Confirm that the GitLab server URL is correct and reachable.