Fetch a list of Backlog issues with optional filters.

Returns a compact table + detailed summaries for each issue.

FILTERS:

• projectIdOrKey: project key (e.g. "MYPROJ") or numeric ID — auto-resolved. Highly recommended.

• statusId: 1=Open, 2=InProgress, 3=Resolved, 4=Closed

• priorityId: 2=High, 3=Normal, 4=Low

• assigneeId: filter by specific user ID(s)

• keyword: full-text search in summary and description

• parentChild: 0=all, 1=child only, 2=parent only, 3=no parent, 4=no child

Array fields accept CSV string ("1,2") or JSON array ([1,2]). PAGINATION: Use offset + count to paginate. Max 100 per request.

Fetch a single Backlog issue by key or ID and return its full details.

Returns: summary, description, status, priority, type, assignee, reporter, categories, milestones, versions, dates, estimated/actual hours.

Use backlog_get_comments separately to fetch comments.

Fetch comments for a Backlog issue.

Returns each comment with: author, date, text content, and field changes (changelog) showing what fields were modified in that activity entry.

PAGINATION: Use minId/maxId to page through comments:

• For next page (desc order): use maxId = (lowest comment ID from previous page - 1)

• For next page (asc order): use minId = (highest comment ID from previous page + 1)

Fetch all statuses defined for a Backlog project.

Returns each status with its ID, name, and color. Use the IDs to filter issues via backlog_get_issue_list (statusId param).

Fetch the global list of issue priorities for this Backlog space.

Priorities are space-wide (not project-specific). Returns each priority with its ID and name. Use the IDs to filter issues via backlog_get_issue_list (priorityId param).

Fetch all categories defined for a Backlog project.

Returns each category with its ID and name. Use the IDs to filter issues via backlog_get_issue_list (categoryId param).

Fetch milestones (versions) for a Backlog project.

Returns each milestone with its ID, name, start date, due date, and archived flag. By default, only active (non-archived) milestones are returned. Set archived=true to include all milestones. Use the IDs to filter issues via backlog_get_issue_list (milestoneId param).

Fetch the list of Backlog projects accessible to the authenticated user.

Returns each project with its numeric ID, project key, name, and archived status. Use the numeric ID in the projectId[] filter of backlog_get_issue_list.

Optional filter:

• archived: omit = all projects, false = active only (default), true = archived only

Fetch project members for a given Backlog project.

Returns a table of users with their numeric ID, userId, display name, email, and role. Use the ID column as assigneeId in backlog_get_issue_list to filter by assignee.

INPUT:

• projectIdOrKey (required): project key e.g. "MYPROJ" or numeric ID e.g. "12345"

• keyword (optional): filter by display name or userId, case-insensitive

EXAMPLE: List all members of project "MYPROJ" → { projectIdOrKey: "MYPROJ" } EXAMPLE: Find user named "Nguyen" → { projectIdOrKey: "MYPROJ", keyword: "nguyen" }

List all attachments on a Backlog issue.

Returns a table with attachment ID, filename, size, uploader, and upload date. Use the attachment ID with backlog_download_attachment to download a specific file.

INPUT:

• issueIdOrKey (required): issue key e.g. "BLG-123" or numeric ID e.g. "12345"

EXAMPLE: { issueIdOrKey: "BLG-123" }

Download an attachment from a Backlog issue and save it to the local filesystem.

Returns the absolute path where the file was saved, the filename, and the file size. Get the attachmentId from backlog_get_attachments first. The output directory is configured via ATTACHMENT_WORKSPACE in the server's environment.

INPUT:

• issueIdOrKey (required): issue key e.g. "BLG-123" or numeric ID

• attachmentId (required): numeric ID from backlog_get_attachments

EXAMPLE: { issueIdOrKey: "BLG-123", attachmentId: 42 }

Export a Backlog issue into a local raw context bundle for LLM summarization.

Fetches issue details, all comments (paginated), attachment metadata, downloads files, and writes:

• raw.md: full markdown context with complete metadata (type, status, resolution, priority, parent, assignee, reporter, categories, milestones, versions, dates, hours), description, attachments, comments, and extracted text

• manifest.json: machine-readable export metadata with placement confidence per attachment

Attachment placement is exact only when issue/comment text references the attachment; otherwise inferred by uploader/time or left unmatched. The output directory is configured via ATTACHMENT_WORKSPACE in the server's environment.

INPUT:

• issueIdOrKey (required): issue key e.g. "BLG-10474" or numeric ID

• outputDir (optional): override export root directory

• includeComments/includeAttachments/downloadAttachments (optional booleans, default: true)

• extractReadableFiles (optional boolean, default: false)

• skipChangelogOnlyComments (optional boolean, default: false) — skip comments with no text (only field changes)

• maxAttachmentBytes (optional): skip files larger than this (default: 10485760 = 10 MB)

• placementWindowMinutes (optional): time window for inferred comment placement (default: 10)

EXAMPLE: { issueIdOrKey: "BLG-10474" }