redmine_create_issue
Create a Redmine issue with key fields: project, tracker, priority, assignee, dates, attachments, and structured description.
Instructions
Create a new Redmine issue. The description should be well-structured: brief statement of what needs to be done, context/why, scope, and links. For bugs: include steps to reproduce, environment, and screenshots.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| subject | Yes | Issue title -- concise but descriptive | |
| due_date | No | Due date (YYYY-MM-DD) | |
| status_id | No | Status ID (1=New, 2=Assigned, 3=Solved, 5=Closed, 17=Review, 19=30_InProgress, etc.) | |
| done_ratio | No | Done percentage (0-100) | |
| project_id | Yes | Project identifier (e.g. 'panama') or numeric ID | |
| start_date | No | Start date (YYYY-MM-DD) | |
| tracker_id | No | Tracker ID (1=Bug, 2=Feature, 3=Support, etc.) | |
| attachments | No | Absolute file paths to attach (images, PDFs, etc.) | |
| category_id | No | Issue category ID (project-specific) | |
| description | Yes | Issue description. Structure as: brief statement, Context, Scope, Links. For bugs: Steps to reproduce, Environment, Screenshots. | |
| priority_id | No | Priority ID (1=Low, 2=Normal, 3=High, 4=Urgent, 5=Immediate) | |
| custom_fields | No | Custom field values, e.g. [{"id": 5, "value": "3. Major"}] | |
| assigned_to_id | No | User ID to assign the issue to | |
| estimated_hours | No | Estimated hours for the task | |
| parent_issue_id | No | Parent issue ID (for sub-tasks) | |
| fixed_version_id | No | Target version / milestone ID (project-specific) |