Skip to main content
Glama

get_issue

Retrieve detailed information about a specific issue in Backlog projects using its ID or key for efficient tracking and management.

Instructions

Returns information about a specific issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueIdOrKeyYesIssue ID or issue key

Implementation Reference

  • The core handler function for the 'get_issue' tool that resolves the issue identifier (ID or key) and fetches the issue data from the Backlog API.
    handler: async ({ issueId, issueKey }) => { const result = resolveIdOrKey('issue', { id: issueId, key: issueKey }, t); if (!result.ok) { throw result.error; } return backlog.getIssue(result.value); },
  • Input schema for the 'get_issue' tool, defining optional issueId (number) or issueKey (string) parameters with descriptions.
    const getIssueSchema = buildToolSchema((t) => ({ issueId: z .number() .optional() .describe( t('TOOL_GET_ISSUE_ISSUE_ID', 'The numeric ID of the issue (e.g., 12345)') ), issueKey: z .string() .optional() .describe( t('TOOL_GET_ISSUE_ISSUE_KEY', "The key of the issue (e.g., 'PROJ-123')") ), }));
  • Output schema (IssueSchema) used by the 'get_issue' tool for validating the structure of the returned Backlog issue object.
    export const IssueSchema = z.object({ id: z.number(), projectId: z.number(), issueKey: z.string(), keyId: z.number(), issueType: IssueTypeSchema, summary: z.string(), description: z.string(), resolution: ResolutionSchema.optional(), priority: PrioritySchema, status: ProjectStatusSchema, assignee: UserSchema.optional(), category: z.array(CategorySchema), versions: z.array(VersionSchema), milestone: z.array(VersionSchema), startDate: z.string().optional(), dueDate: z.string().optional(), estimatedHours: z.number().optional(), actualHours: z.number().optional(), parentIssueId: z.number().optional(), createdUser: UserSchema, created: z.string(), updatedUser: UserSchema, updated: z.string(), customFields: z.array(CustomFieldSchema), attachments: z.array(IssueFileInfoSchema), sharedFiles: z.array(SharedFileSchema), stars: z.array(StarSchema), });
  • The 'get_issue' tool is instantiated and registered in the 'issue' toolset returned by the allTools function.
    getIssueTool(backlog, helper),
  • Helper utility function called in the handler to resolve either a numeric issue ID or string key into a usable identifier, with error handling.
    export const resolveIdOrKey = <E extends EntityName>( entity: E, values: { id?: number; key?: string }, t: TranslationHelper['t'] ): ResolveResult => resolveIdOrField(entity, 'key', values, t);

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/nulab/backlog-mcp-server'

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