Create a new ITSM ticket.
Vendor ID fields (project_vendor_id, assigned_user_vendor_id, parent_ticket_vendor_id) are passed straight through to the vendor without extra DB resolution. The ticket is always persisted locally and the full DB record is returned.
Name/Title of the Ticket
Leen project UUID. Either project_id or project_vendor_id must be provided.
Vendor's project identifier (e.g., Jira project key 'PROJ'). Alternative to project_id.
Type of the Ticket (e.g., Task, Bug, Story)
Vendor issue type ID (e.g., Jira issue type ID). Alternative to type — at least one must be provided. Preferred over type when both are given.
Deprecated: use type_vendor_id instead. Vendor issue type ID.
Description of the Ticket
Status of the Ticket. Note: Jira does not support setting status at creation time — tickets are always created with the workflow's default status. Use the update endpoint to change status after creation.
Priority of the Ticket
Leen user UUID. Either assigned_user_id or assigned_user_vendor_id can be provided.
Vendor's user identifier (e.g., Jira accountId). Alternative to assigned_user_id.
Parent Ticket ID (for sub-tasks)
Vendor's ticket identifier (e.g., Jira issue key 'PROJ-123'). Alternative to parent_ticket_id.
User-provided tracking identifier (auto-generated from project-type-hash if not provided)
Successful Response
Response model for ticket creation. Extends ScopedITSMTicketRespModel with vendor ID fields that are echoed back when vendor IDs were provided in the request (rather than Leen UUIDs).
Leen's UUID for the Ticket
Name of the Ticket
Status of the Ticket
Vendor-specific attributes of the Ticket
Whether the Ticket is active
Type of the Ticket (e.g., Epic, Story, Task, Bug)
Vendor-specific type ID (e.g., Jira issue type ID)
Parent Ticket ID (for sub-tasks)
Description of the Ticket
Creation time of the Ticket in the vendor system
Due date of the Ticket
Closing time of the Ticket
User ID assigned to the Ticket
User ID who created the Ticket
Last status update time
Project ID the Ticket belongs to
Tags associated with the Ticket
Priority of the Ticket
URL of the Ticket
User-provided tracking identifier for the Ticket
Vendor key of the parent ticket (e.g. 'PROJ-42'). Populated when the request used parent_ticket_vendor_id.
Vendor account ID of the assigned user (e.g. Jira accountId). Populated when the request used assigned_user_vendor_id.
Vendor issue type ID (e.g. '10034'). Populated when the request used type_vendor_id.