Verified:GitHub

issues

Manage GitLab project issues via the REST API.

Updated Apr 10, 2026

Search Tags:#automation #api #cli #issues #gitlab #triage #issue-tracking

One-click install

npx skills add https://github.com/theslashdojo/dojo --skill issues-theslashdojo

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: issues
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/gitlab/issues
Command: npx skills add https://github.com/theslashdojo/dojo --skill issues-theslashdojo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines project-scoped issue management in GitLab so agents and engineers can reliably create, find, inspect, update, close, and reopen issues without manual API fiddling.

Core Features & Use Cases

Search & Triage: List and filter project issues by state, labels, assignee, and full-text search to avoid duplicates before creating new issues.
Create with Metadata: Create issues with title, description, labels, confidentiality, due date, and issue type to standardize intake.
Inspect & Transition: Fetch a single issue by IID, update fields incrementally, and transition state via close and reopen operations for incident and release workflows.
Use Case: Automate bug triage for a release by searching open bug-labeled issues, creating missing tickets, and closing resolved items as CI pipelines land fixes.

Quick Start

Create a bug in project group/project titled Bug: deploy failed on main with labels bug and platform and include a clear description of the failure.

Frequently Asked Questions about issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate GitLab issue management for triage and release tracking?▼

Automate GitLab issue management by using an API-driven approach to create, list, inspect, update, close, and reopen project issues. This requires a project path or numeric ID and an access token to transition issues for triage workflows.

Can I filter GitLab project issues by labels, assignee, and state?▼

Yes, you can filter GitLab project issues by state, labels, assignee, and full-text search. This functionality helps search existing project issues to avoid duplicates before creating new tickets during bug triage.

What access token do I need to interact with the GitLab issue API?▼

You need to provide an access token via GITLAB_TOKEN, OAUTH_TOKEN, or CI_JOB_TOKEN to call the GitLab REST API. This token authenticates requests to manage project-scoped issues programmatically.

How do I create a GitLab issue with metadata like labels and due dates?▼

Create GitLab issues with standardized metadata by specifying the title, description, labels, confidentiality, due date, and issue type. This approach standardizes intake for bugs and incidents directly through API calls.

Does this approach work for updating and transitioning GitLab incident issues?▼

Yes, fetch a single issue by its project-scoped IID, update fields incrementally, and transition the state via close and reopen operations. This workflow supports incident response and release work tracking.

What is the best way to close resolved GitLab issues automatically as CI pipelines land fixes?▼

The best way to close resolved GitLab issues automatically is to search for open bug-labeled issues, create missing tickets, and close resolved items by calling the GitLab REST API as CI pipelines land fixes.