Jira Integration

This guide shows how to create an Atlassian API token, connect Jira inside Testifly, and then use that connection when you create a new feature from Jira.

1. Create an Atlassian API token

Testifly connects to Jira Cloud by using your Jira site URL, your Atlassian account email address, and an Atlassian API token.

What you need before you start

• Your Jira Cloud site URL, for example https://your-company.atlassian.net
• The email address of the Atlassian account that can access the Jira projects and issues you want to use
• Permission in Jira to view the projects and issues you want Testifly to read

Steps to create the token

1. Sign in to your Atlassian account.
2. Open the Atlassian security page for API tokens: https://id.atlassian.com/manage-profile/security/api-tokens
3. Select Create API token.
4. Give the token a name that helps you recognize it later, for example Testifly Jira Integration.
5. Copy the generated token and store it somewhere safe for the next step.

Keep the token private. Anyone who has the token and your account email can use it to access Jira with the same permissions as your Atlassian account.

If you want more background from Atlassian, you can also review their documentation here: https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/

2. Configure Jira in Testifly

After you create the token, you can save the Jira connection in your Testifly project.

Open the Jira integration settings

1. Open your project in Testifly.
2. Go to Settings.
3. Open Integrations.
4. In the Jira card, click Connect Jira.

Fill in the Jira connection details

The Jira setup flow in Testifly asks for the following values:

1. Jira site URL
   Enter your Jira Cloud URL, for example https://your-company.atlassian.net
2. Jira account email
   Enter the email address of the Atlassian account that owns the API token
3. Jira API token
   Paste the API token you created in the Atlassian account settings
4. Main Jira project
   Choose the Jira project that belongs to this Testifly project
5. Ready for testing status
   Choose the Jira status that means an item was deployed and is ready for testing. Testifly uses it for the daily report described below.

When you edit an existing connection, you can leave the token field empty to keep the saved token.

Connect with OAuth instead of an API token

On the Jira card you can also click CONNECT VIA OAUTH. You sign in to Atlassian and approve access, so you do not need to create an API token. The setup then skips the credentials step and asks only for the main project and the ready-for-testing status.

Save and verify the connection

1. Review the values in the final step of the setup dialog.
2. Click Save and check connection.
3. Wait for Testifly to validate the Jira connection.
4. After it succeeds, the Jira card should show the connection details, including the site URL, email, account, and last result.

If the connection fails, double-check these values first:

• The Jira site URL is correct and includes https://
• The Atlassian email matches the account that created the token
• The token was copied completely and has not expired or been revoked
• The Jira account has access to the Jira projects and issues you want to use

3. Use Jira when creating a new feature

Once Jira is connected successfully, you can create a feature in Testifly directly from Jira issues.

Create the feature from Jira

1. Open your project in Testifly.
2. Go to Features.
3. Start creating a new feature.
4. Enter the Feature URL.
5. In the Create From section, choose From Jira.
6. In the Jira section, click read from Jira.
7. In the Jira selector dialog:
   1. Optionally select one or more Jira projects to narrow the search.
   2. Enter a search term such as an issue key, summary text, or description text.
   3. Click Search.
   4. Click Add next to the Jira issue you want to connect.
   5. Click Connect Selected Issues to confirm your selection.
8. Save the feature.

What happens after you select a Jira item

• The selected Jira issue key and summary are used to populate the feature name
• The connected Jira issue keys are saved with the feature creation request
• Testifly can use the Jira-linked feature flow when the feature is created

4. Get a daily report of items ready for testing

Once a day, early in the morning, Testifly checks your main Jira project for issues that moved to your Ready for testing status during the last day. If it finds any, it emails a short report. For each issue, the report says what changed and which Testifly tests relate to it.

• The report is sent only when there is something to review.
• Only users who have Receive work item update emails turned on get it. See Notifications and Emails.
• No report is sent for a project whose trial has ended.

You can also ask Tessa which Jira issues are ready for testing right now.

5. Tips for a smoother Jira setup

• Use a dedicated Atlassian API token for Testifly so it is easier to rotate later
• Make sure the Atlassian account has access only to the Jira projects Testifly needs
• If you regenerate or revoke the token in Atlassian, update it again in Settings -> Integrations -> Jira
• If the From Jira option does not appear during feature creation, re-open the Jira integration and make sure the last connection check succeeded.