Skip to main content

JIRA Reporting

F
Written by Flakron Bajrami
Updated over a week ago

1. Overview

This document explains how to integrate Jira Cloud with the Usetrace application, including configuration steps, generating API tokens and functionalities we provide.
​
​2. Prerequisites

Before starting, make sure you have:

Access to your company’s Jira Cloud instance

Example: https://tarmac-test-2.atlassian.net
​

3. Jira API Configuration

3.1 Generate an API Token

  1. Log in to your Atlassian account.
    ​

  2. Go directly to the API Token page:
    ​ 🔗 https://id.atlassian.com/manage-profile/security/api-tokens​
    ​

  3. Click Create API token.
    ​

  4. Give it a descriptive name — for example:
    ​ Integration with Usetrace
    ​

  5. Click Create, then Copy the token.
    ​
    ​ Important: Store the token securely — you won’t be able to view it again later.​

3.2 Identify Your Jira Site (Host URL)

Your Host URL is based on your company’s Jira Cloud site name.

How to find it:

  1. Log into your Jira Cloud.

Check your browser’s address bar — it will look like:
​

https://<your-site-name>.atlassian.net

  1. Copy everything up to .atlassian.net.​


​Example:
​

If your Jira opens at

https://tarmac-test-2.atlassian.net/jira/for-you,

then your Host URL is:

https://tarmac-test-2.atlassian.net

You will need this URL in the Usetrace configuration.
​

3.3 Create a Jira Project

You should use a dedicated project for Usetrace issues:

  1. In Jira, go to Projects → Create Project.
    ​

  2. Select a template (e.g., Software Development → Scrum / Kanban).
    ​

  3. Set the project name, key, and project lead.
    ​

Save and note the project key — you’ll use it during setup.
​
​

4. Configure Jira Access in Usetrace

  1. In Usetrace, go to Preferences → Project.
    ​

  2. Check the box Enable JIRA integration.
    ​
    ​This checkbox is visible only if your plan includes capabilities for the Jira report type.
    ​

  3. After enabling, fill out the following fields:

Field

Description

Example

Host URL

Your Jira Cloud site URL

https://tarmac-test-2.atlassian.net

Email

The email linked to your Jira account

you@company.com

API Token

The token generated in step 3.1

••••••••••••

Project Key

The key of your Jira project

QA, DEV, UTRACE

5. Functionalities with Jira

5.1 Scheduling & Reporting

In Scheduling & Reporting, when you create a new Automatic Report and choose Jira, you can:

  • Either configure new Jira settings that will belong only to this reporter
    ​

  • Or reuse the project-level Jira configuration by enabling Use General Configs
    ​

Once configured, Usetrace will automatically create Jira tickets for failed traces.
​


5.2 Trace Details → Screenshot Tab

In the Screenshot Tab, a JIRA button (Create Ticket) is available.

When clicked:

  • A redirect page on jira opened and some fields are prefilled with suggested info.
    (Summary, Issue Type, Description and Reporter)
    ​

  • When submitted, a new Jira issue is created directly in the configured project.

Then after you have created new issue for that specific error on that specific trace, you can view the existing jira ticket by clicking on existing link above the Create jira button in the usetrace app.

5.3 Run Results → Overview Tab

Similarly, in the Overview Tab, a JIRA button appears.

Clicking it opens a modal identical to the Screenshot Tab version:

Prefilled Summary, Issue Type, Description and Reporter
​


5.4 Using Jira Email for Automatic Issue Creation

Instead of using the Jira API, Usetrace also supports creating issues via Jira’s email-to-ticket feature.

Jira Cloud provides a dedicated email address (ending with @atlassian.net) that automatically creates a new issue in a specific project whenever an email is received.
​

How it works

  1. In your Jira project, go to:
    ​Project Settings → Email requests

  2. Copy the email address provided by Jira (example: project-key@your-site.atlassian.net)

  3. In Usetrace:

    • Create a new Automatic Report

    • Select Email as the reporter type

    • Use the Jira-provided email as the recipient

When Usetrace sends an email for a failed trace:

  • Jira receives it

  • A new issue is automatically created in the project configured for that email address

  • The email subject and body become the issue’s summary and description

  • Attachments (such as screenshots) are also included

When to use this method

This option is useful when:

  • You prefer not to manage API tokens

  • Your Jira admins restrict API access

  • You want a simpler setup with minimal configuration

This method works alongside the standard API-based Jira integration and can be configured per reporter.
​

Did this answer your question?