Create Issue
create_issueCreate a new MantisBT issue with a summary, description, project ID, and category; optionally set priority, severity, assignee, versions, and custom fields.
Instructions
Create a new MantisBT issue. Returns the full created issue object including the assigned id, summary, status, priority, severity, category, reporter, created_at, and view_url. With response: "short" only id, summary, project, category, status, handler, created_at and view_url (default "full"; it changes to "short" in 2.0.0).
Required fields: summary, description, project_id, category. All other fields are optional with sensible defaults (priority: "normal", severity: "minor").
Recommended workflow:
Call get_project with include: ["categories"] to obtain a valid category name
Optionally add "versions" to include to obtain version names
Optionally call get_project with member_query to resolve the assignee's username
Both priority and severity accept canonical English names or localized labels from the connected MantisBT instance — call get_issue_schema to see all available values.
For the handler, prefer the username field (resolved server-side) over handler_id when working interactively.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"summary": "<summary>",
"description": "<description>",
"project_id": "<project_id>",
"category": "<category>"
},
"name": "create_issue"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| handler | No | MantisBT login name of the assignee. The server resolves the name to a user ID from the project member list. Use get_project with member_query or include: ["users"] to look up valid login names. | |
| summary | Yes | Issue summary/title (required) | |
| version | No | Affected product version name. Use get_project with include: ["versions"] to list available version names for the project. | |
| category | Yes | Category name (required). Use get_project with include: ["categories"] to list available categories for the project. | |
| priority | No | Priority level. Canonical English names: none, low, normal, high, urgent, immediate. Default: "normal". Use get_issue_schema to see localized labels. | normal |
| response | No | "full" (default): the whole issue as MantisBT returns it, including description, notes and history. "short": only the fields that confirm the change — far fewer tokens. The default changes to "short" in 2.0.0. | full |
| severity | No | Severity level. Canonical English names: feature, trivial, text, tweak, minor, major, crash, block. Default: "minor". Use get_issue_schema to see localized labels. | minor |
| handler_id | No | Numeric user ID of the assignee. Alternative to the handler field — use one or the other, not both. | |
| project_id | Yes | Project ID the issue belongs to — use list_projects to discover project IDs | |
| view_state | No | Visibility of the issue: "public" (visible to all, default) or "private" (restricted to higher-access users). | |
| description | Yes | Detailed issue description (required). Do not create issues without a description. Plain text or Markdown. | |
| custom_fields | No | Custom field values: [{field: {id|name}, value: "<string>"}]. Use get_issue_schema or get_metadata to discover available custom fields per project. | |
| target_version | No | Target fix version — version in which the issue is planned to be resolved. Use get_project with include: ["versions"] to list available version names. | |
| reproducibility | No | How reliably the issue reproduces. Canonical English names: always, sometimes, random, have not tried, unable to reproduce, N/A. Use get_issue_schema to see localized labels. | |
| fixed_in_version | No | Version in which the issue was fixed. Use get_project with include: ["versions"] to list available version names. | |
| steps_to_reproduce | No | Step-by-step instructions to reproduce the issue. Plain text or Markdown. | |
| additional_information | No | Additional context or notes about the issue. Plain text or Markdown. |