Skip to main content
Glama

MCP GitLab Server

by Vijay-Duke

gitlab_get_user_open_issues

Retrieve and prioritize open GitLab issues assigned to or created by a specific user. Filter by severity, SLA status, and sort by priority, due date, or recent updates for effective workload and compliance management.

Instructions

List open issues assigned to or created by a specific user.

Use this tool to see what issues a user is currently working on or responsible for.

Retrieve all currently open issues assigned to the specified user across all accessible projects, with intelligent priority sorting.

Returns prioritized issue list with:

  • Issue details: title, description, labels
  • Priority indicators: severity, SLA status
  • Context: project, milestone, due date
  • Activity: recent updates, comment count
  • Assignment: other assignees, collaboration info

Use cases:

  • Personal issue dashboard and inbox
  • Workload management and planning
  • SLA compliance tracking
  • Sprint and milestone planning

Parameters:

  • user_id: Numeric user ID
  • username: Username string (use either user_id or username)
  • severity: Filter by severity level
  • sla_status: Filter by SLA compliance (at_risk, overdue, ok)
  • sort: Sort order (priority, due_date, updated)
  • per_page: Results per page (default: 20)
  • page: Page number (default: 1)

Example: Get overdue issues for user

{ "username": "johndoe", "sla_status": "overdue", "sort": "priority" }

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination Type: integer Range: ≥1 Default: 1 Example: 3 (to get the third page of results) Note: Use with per_page to navigate large result sets
per_pageNoNumber of results per page Type: integer Range: 1-100 Default: 20 Example: 50 (for faster browsing) Tip: Use smaller values (10-20) for detailed operations, larger (50-100) for listing
severityNoFilter by severity level
sla_statusNoFilter by SLA compliance
sortNoSort orderpriority
user_idNoNumeric user ID
usernameNoUsername string

Input Schema (JSON Schema)

{ "properties": { "page": { "default": 1, "description": "Page number for pagination\nType: integer\nRange: ≥1\nDefault: 1\nExample: 3 (to get the third page of results)\nNote: Use with per_page to navigate large result sets", "minimum": 1, "type": "integer" }, "per_page": { "default": 50, "description": "Number of results per page\nType: integer\nRange: 1-100\nDefault: 20\nExample: 50 (for faster browsing)\nTip: Use smaller values (10-20) for detailed operations, larger (50-100) for listing", "maximum": 100, "minimum": 1, "type": "integer" }, "severity": { "description": "Filter by severity level", "type": "string" }, "sla_status": { "description": "Filter by SLA compliance", "enum": [ "at_risk", "overdue", "ok" ], "type": "string" }, "sort": { "default": "priority", "description": "Sort order", "enum": [ "priority", "due_date", "updated" ], "type": "string" }, "user_id": { "description": "Numeric user ID", "type": "string" }, "username": { "description": "Username string", "type": "string" } }, "type": "object" }

Other Tools from MCP GitLab Server

Related Tools

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vijay-Duke/mcp-gitlab'

If you have feedback or need assistance with the MCP directory API, please join our Discord server