Request Tracker (RT)

Add a private internal comment to an RT ticket. The comment creates a durable transaction that REST2 cannot remove; RT scrips may still notify staff.

Create a durable RT ticket in a queue. Creation may run RT scrips or send notifications and cannot be fully erased through REST2.

Retrieve one visible RT queue by id or exact name, including lifecycle and capability-sensitive links.

Retrieve one visible RT ticket, including its current fields and capability-sensitive links for allowed follow-up operations.

Return one page of detailed ticket history, including transaction types, field changes, comments, creators, and timestamps.

List queues visible to the connected RT user so an agent can select a queue for ticket search or creation. Returns one bounded page.

List attachment metadata references associated with a visible RT ticket without downloading attachment content.

Send public correspondence on an RT ticket. This can email requestors or other recipients according to RT configuration and creates a durable transaction that REST2 cannot remove.

Search visible RT tickets with an explicit TicketSQL expression and return one bounded page. Use a condition such as `id > 0` when listing tickets; an omitted search does not list all tickets.

Search RT users with structured field conditions and return one bounded page of user references or selected fields for requester and owner lookup.

Update selected metadata on an existing RT ticket and verify every requested field by reading it back. Omitted fields are unchanged.