wetrack_create_support_ticket
Create a support ticket in WeTrack by providing title, status, priority, organisation, and project. Optionally add description, assignee, dates, and estimate.
Instructions
Create a legacy support ticket (not an EPIC/STORY/TASK/BUG work item).
Args: title: Ticket title e.g. 'Login issue on portal'. request_status_id: Integer status ID. request_priority_id: Integer priority ID. organisation_id: UUID of the client organisation. project_id: UUID of the project. description: Rich HTML description (up to 2MB). request_type_id: Optional ticket type ID. category_id: Optional category ID. assigned_to: Optional user integer ID to assign. reporting_to: Optional reporter user integer ID. due_date: ISO datetime for due date. start_date: ISO datetime for start. estimate: Estimated hours (float).
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": {
"title": "<title>",
"request_status_id": "<request_status_id>",
"request_priority_id": "<request_priority_id>",
"organisation_id": "<organisation_id>",
"project_id": "<project_id>"
},
"name": "wetrack_create_support_ticket"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | ||
| due_date | No | ||
| estimate | No | ||
| project_id | Yes | ||
| start_date | No | ||
| assigned_to | No | ||
| category_id | No | ||
| description | No | ||
| reporting_to | No | ||
| organisation_id | Yes | ||
| request_type_id | No | ||
| request_status_id | Yes | ||
| request_priority_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |