Integrations

Connecting Jira

Create Jira issues straight from any Tirs session — every issue links back to the replay, logs and environment automatically.

آخر تحديث ١٦‏/٠٨‏/٢٠٢٦

The Jira integration turns any Tirs session into a Jira issue in one click. The issue comes pre-filled from the session and links straight to the full replay, console logs, network requests, environment details and AI-written reproduce steps. Your developers open the issue and see the whole picture — no back-and-forth asking for steps.

What the integration does

  • Create a Jira issue from any session in your workspace.
  • The issue is pre-filled with a title and description from the session, editable before you create it.
  • AI writes reproduce steps from the recorded session — they live on the session your issue links to.
  • Every issue links back to the full session in Tirs — replay, console logs, network requests and environment details included.

Connect Jira Cloud (OAuth)

If your team is on Jira Cloud, you connect with OAuth. All you need is a Jira account with access to the projects you want to use.

  1. Open app.tirs.dev and go to Development tools, then Integrations.
  2. Find Jira and click Connect Jira.
  3. Sign in to Atlassian and authorize Tirs for your Jira site.
  4. Back in Tirs, select the Jira site you want to connect.

The connection applies to the whole workspace, so your teammates can start creating issues right away. If permissions change later, you can reconnect from the same page at any time.

Self-hosted Jira connects through an Application Link using OAuth 1.0a instead of Jira Cloud's OAuth 2.0. A Jira admin needs to set this up once.

  1. A workspace owner or admin sets your Jira base URL in Tirs once — Tirs detects self-hosted Jira from the URL automatically.
  2. Ask your Jira admin to create an Application Link in Jira administration using the consumer key and public key provided by Tirs.
  3. In Tirs, go to Development tools, then Integrations, and click Connect Jira.
  4. Approve the authorization prompt in Jira to finish.

Set a default project and issue type

After connecting, pick the Jira project and issue type — usually Bug — that new tickets should use. Every ticket you create starts with these defaults, and you can change them on any individual ticket before it is created.

What a created ticket looks like

When you create a ticket from a session, Tirs creates the issue in Jira with:

  • A title and description pre-filled from the session, editable before the issue is created.
  • A link back to the session in Tirs, so anyone can watch the replay in full.
  • Through that link: the AI-written reproduce steps, console logs and network requests with method, status and URL.
  • Plus the browser, OS and screen details captured with the session.

You can edit the pre-filled title and description before creating the issue if you want to adjust the wording.

Next steps

Using Azure DevOps as well? See Connecting Azure DevOps to send sessions there too.