Connecting
A workspace owner or admin connects ClickUp or Jira once, over OAuth, from Workspace → Integrations. Tokens are stored encrypted and only used on the server. Each project then picks where its tickets go: a ClickUp list or a Jira project, on the same page. Different projects can file to different places.
Nothing to install on the tracker's side. On a red, the + Ticket menu offers the connected tracker, a link to connect the other, and Copy issue.
What a ticket holds
On a red, press Create ticket. The ticket is titled with the journey's code, its name and the failing step, and its body carries:
- The journey's steps, with the failing one marked and what Burhan expected there.
- What Burhan saw instead, in plain words, and whose it likely is: front end, back end, or a product ruling the docs don't settle.
- A link to the run in Burhan: the video at the failing step, with taps drawn on it.
- The API calls made during the step (method, path, status) and the console errors and uncaught exceptions the page threw.
- The account and environment it ran on, and the language.
One ticket per red, kept up to date
A journey has at most one open ticket per account. If it fails again on the next run, Burhan doesn't file a second one; the button shows the open ticket instead. When a later run passes, Burhan writes a comment on the ticket saying so, with the run's date, and the slot is free again.
Filing a ticket also tells Burhan the red was real. Together with your "Not a bug" verdicts, that's how it learns to judge your app.
No tracker?
Copy the report instead: the same text, as Markdown, for Slack, email or any other tool.