Create Issue
create_issueCreate a new issue in MantisBT with required summary, description, project ID, and category; optional fields include 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.
Required fields: summary, description, project_id, category. All other fields are optional with sensible defaults (priority: "normal", severity: "minor").
Recommended workflow:
Call get_project_categories to obtain a valid category name
Optionally call get_project_versions to obtain version names
Optionally call find_project_member 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_enums to see all available values.
For the handler, prefer the username field (resolved server-side) over handler_id when working interactively.
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 find_project_member or get_project_users to look up valid login names. | |
| summary | Yes | Issue summary/title (required) | |
| version | No | Affected product version name. Use get_project_versions to list available version names for the project. | |
| category | Yes | Category name (required). Use get_project_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_enums to see localized labels. | normal |
| severity | No | Severity level. Canonical English names: feature, trivial, text, tweak, minor, major, crash, block. Default: "minor". Use get_issue_enums 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_fields 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_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_enums to see localized labels. | |
| fixed_in_version | No | Version in which the issue was fixed. Use get_project_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. |