Skip to main content
Glama

MCP GitLab Server

by Vijay-Duke

gitlab_get_user_resolved_issues

Retrieve and analyze issues closed or resolved by a specific user on GitLab. Track contributions, assess impact, and analyze resolution details for performance reviews, knowledge sharing, or productivity insights.

Instructions

Get issues closed/resolved by a user

Find all issues that were closed or resolved by the specified user, showing their problem-solving contributions and impact.

Returns resolved issues with:

  • Issue details: original problem, resolution
  • Resolution info: how it was closed, related MRs
  • Timeline: resolution time, effort indicators
  • Impact: complexity, stakeholders affected
  • Recognition: contribution to project health

Use cases:

  • Track problem resolution contributions
  • Performance reviews and recognition
  • Knowledge base building
  • Team productivity analysis

Parameters:

  • user_id: Numeric user ID
  • username: Username string (use either user_id or username)
  • since: Resolved after date (YYYY-MM-DD)
  • until: Resolved before date (YYYY-MM-DD)
  • complexity: Filter by resolution complexity
  • sort: Sort order (closed, complexity, impact)
  • per_page: Results per page (default: 20)
  • page: Page number (default: 1)

Example: Get issues resolved this quarter

{ "username": "johndoe", "since": "2024-01-01", "until": "2024-03-31", "sort": "closed" }

Input Schema

NameRequiredDescriptionDefault
complexityNoFilter by resolution complexity
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
sinceNoResolved after date (YYYY-MM-DD)
sortNoSort orderclosed
untilNoResolved before date (YYYY-MM-DD)
user_idNoNumeric user ID
usernameNoUsername string

Input Schema (JSON Schema)

{ "properties": { "complexity": { "description": "Filter by resolution complexity", "type": "string" }, "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" }, "since": { "description": "Resolved after date (YYYY-MM-DD)", "type": "string" }, "sort": { "default": "closed", "description": "Sort order", "enum": [ "closed", "complexity", "impact" ], "type": "string" }, "until": { "description": "Resolved before date (YYYY-MM-DD)", "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