API reference / Sessions
Make a bug ticket of a problem
Makes an engineering ticket, kind bug and label sessions, that the Engineer analyzes and plans. The Engineer reads the problem, the events of its sessions and the links to their replays on its card. A person always approves its plan, and Troopy never releases it by itself, because what visitors did steers it. A problem has one open ticket: while it is open, a second call gives it back.
/api/v1/session-issues/{number}/ticketOther ways to call it
troopy sessions tickettroopy_file_session_ticketIdempotency-Key header. A retry with the same key gets the first answer back, and the operation runs one time.Path parameters
number*integerAt least 1
Response
201 · application/jsondata*object12 properties
number*integerProblem 14 is 14
title*stringseverity*enum<string>criticalhighmediumlow
evidence*stringWhat the events of the sessions show
area*stringThe page, the route or the part of the product
status*enum<string>fixed: its ticket is done, and no session showed it after that
openignoredfixed
seen*integerHow many sessions showed it
firstSeenAt*stringISO 8601 date and time
lastSeenAt*stringISO 8601 date and time
sessions*array<object>The sessions that showed it, newest first, 20 at most
6 properties
id*stringsource*enum<string>Where the session came from: troopy, Troopy's own script, or posthog
troopyposthog
replayUrl*string | nullThe replay in Sessions or in PostHog. Null: no replay of the session
replay*string | nullSource troopy: the id of the replay, for GET /session-replays
country*string | nullat*stringISO 8601 date and time
alert*object | nullWhy it needs a look: new, or came_back after its ticket was done
3 properties
why*enum<string>newcame_back
at*stringISO 8601 date and time
seen*booleanticket*object | nullIts latest bug ticket
3 properties
key*stringtitle*stringstatus*enum<string>backlogtodoin_progressneeds_youin_reviewdonecanceled