Skip to main content
Glama

gitlab_get_user_resolved_issues

Retrieve issues closed or resolved by a specific user to track problem-solving contributions, analyze team productivity, and build knowledge bases for performance reviews.

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

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

Implementation Reference

  • The handler function that executes the core logic of the tool: extracts parameters from arguments and calls the GitLabClient method to retrieve user's resolved issues.
    def handle_get_user_resolved_issues(client: GitLabClient, arguments: Optional[Dict[str, Any]]) -> Dict[str, Any]:
        """Handle getting user's resolved issues"""
        user_id = get_argument(arguments, "user_id")
        username = get_argument(arguments, "username")
        since = get_argument(arguments, "since")
        until = get_argument(arguments, "until")
        complexity = get_argument(arguments, "complexity")
        sort = get_argument(arguments, "sort", "closed")
        per_page = get_argument(arguments, "per_page", DEFAULT_PAGE_SIZE)
        page = get_argument(arguments, "page", 1)
        
        return client.get_user_resolved_issues(
            user_id=user_id,
            username=username,
            since=since,
            until=until,
            complexity=complexity,
            sort=sort,
            per_page=per_page,
            page=page
        )
  • MCP tool schema definition specifying input parameters, types, descriptions, and validation rules for the gitlab_get_user_resolved_issues tool.
    types.Tool(
        name=TOOL_GET_USER_RESOLVED_ISSUES,
        description=desc.DESC_GET_USER_RESOLVED_ISSUES,
        inputSchema={
            "type": "object",
            "properties": {
                "username": {"type": "string", "description": "Username string"},
                "since": {"type": "string", "description": "Issues resolved after date (YYYY-MM-DD)"},
                "until": {"type": "string", "description": "Issues resolved before date (YYYY-MM-DD)"},
                "per_page": {"type": "integer", "description": desc.DESC_PER_PAGE, "default": DEFAULT_PAGE_SIZE, "minimum": 1, "maximum": MAX_PAGE_SIZE},
                "page": {"type": "integer", "description": desc.DESC_PAGE_NUMBER, "default": 1, "minimum": 1}
            },
            "required": ["username"]
        }
    ),
  • Maps the tool name to its handler function in the TOOL_HANDLERS dictionary, which is used by the MCP server to dispatch calls to the correct handler.
    TOOL_GET_USER_RESOLVED_ISSUES: handle_get_user_resolved_issues,
  • Constant defining the exact tool name string used throughout the codebase for consistency.
    TOOL_GET_USER_RESOLVED_ISSUES = "gitlab_get_user_resolved_issues"

Tool Definition Quality

Score is being calculated. Check back soon.

Install Server

Other Tools

Latest Blog Posts

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