Namespace Reference
Tickets
Curated JQL namespaces and examples for tickets.
Ticket namespaces cover support categories, subcategories, tickets, custom question schema, comments, documents, transactions, pipeline stages, status logs, and ticket workflow nodes.
Key namespaces and models
tickets.Categorytickets.SubCategorytickets.Tickettickets.StatusLogtickets.Documenttickets.Commenttickets.ExternalCommenttickets.Activitytickets.TransactionCategorytickets.Transactiontickets.TransactionLogtickets.Sectiontickets.Questiontickets.Pipelinetickets.PipelineStagetickets.TicketPipelineHistorytickets.Workflowtickets.WorkflowNodeWrappertickets.WorkflowNode
Common controller intents
tickets.Ticket.saveQuestiontickets.Ticket.reorderQuestionstickets.Ticket.updateWorkflowNodetickets.Ticket.getQuickStatstickets.Ticket.getMyQuickStatstickets.Ticket.getMyBadgeCounttickets.Document.upload
Common model intents
Most listed model namespaces support retrieve, retrieveOne, retrieveV2, create, update/patch, deleteOne, metadata, and aggregate subject to model permissions. Use consequence only for models that implement an on_<consequence> hook.
Retrieve example
json
1{
2 "__meta__": {
3 "schema": "model",
4 "namespace": "tickets.Ticket",
5 "intent": "retrieve",
6 "authenticationClass": "jwt",
7 "ordering": "-created",
8 "limit": 20
9 },
10 "id": null,
11 "created": null
12}Create example
json
1{
2 "__meta__": {
3 "schema": "model",
4 "namespace": "tickets.Category",
5 "intent": "create",
6 "authenticationClass": "jwt",
7 "return": {
8 "id": null,
9 "name": null,
10 "alias": null
11 }
12 },
13 "name": "Support",
14 "alias": "support"
15}For examples that include foreign keys, numeric ids must refer to records in the same tenant and visible to the authenticated user.