Jira Cloud

Use Testiny as your Jira test management tool and connect test cases and results to Jira Issues. Testiny fully integrates into Jira Cloud — you can create, link and look up issues, requirements or defects from Testiny. You are also able to view linked testing activities directly from Jira — a full two-way integration.

Testiny further makes complex issue-type configuration (with all its custom fields etc.) unnecessary. Testiny reads your issue-configurations and performs the whole configuration in the background. Just link Testiny with Jira — and you’re done!

Configuration

info

Testiny connects to Jira Cloud using OAuth 2.0. If you have an existing integration that connects to Jira with an API token, we strongly suggest switching it to OAuth. See the Jira Cloud (API token) documentation for the legacy configuration and the upgrade guide.

For Testiny Server, OAuth 2.0 Jira integrations are available from version 1.39.0. For previous versions, see the Jira Cloud (API token) documentation.

To configure a new integration, you need to have admin rights in Testiny. Go to Settings > Integrations and click on ' Add integration' for Jira. A side panel opens where you need to define the following options for the connection:

• Jira Instance URL
  Enter the Jira Instance URL — it usually has the format: https://your_organization.atlassian.net

• Allow issue creation
  Choose which Jira account is used when creating issues from Testiny:

  • Using shared integration account — issues are created with the shared account that authorized the integration (see below). All Testiny users create issues on behalf of this account.
  • Using personal account — each user authorizes their own Jira account, and issues are created as the actual user. The first time a user creates or links an issue, Testiny shows an "Authorization required" dialog and redirects the user to the Atlassian consent screen.

  Both options can be enabled at the same time — users can then authorize their personal account, or fall back to the shared integration account. If the shared integration account is not allowed to create issues, users must authorize their personal account.

When the above fields are filled in, click Authorize (shown as Save & Authorize when there are unsaved changes). You are redirected to the Atlassian consent screen — sign in with the Jira account you’d like to use for the Testiny connection and grant access to your Jira instance. This account becomes the integration’s shared integration account: it is used for looking up and linking issues, and — if "Using shared integration account" is enabled — for creating them.

Testiny requests the following scopes in Jira:

• For linking and looking up issues: Viewing boards and backlogs, sprints, user information, project and issue data, and the currently logged-in user.

• For creating issues: Updating issues in Jira

After a successful authorization, the connection section shows the authorized account and Jira site. You can revoke the authorization at any time by clicking Remove authorization.

info

For Testiny Server, you need to provide your own Atlassian OAuth App. Set the OAuth credentials as environment variables, or see the section below on how to set the OAuth App in the integration settings.

Using your own Atlassian OAuth app

By default, Testiny uses its own Atlassian OAuth app for the authorization. If your organization prefers to control the OAuth client itself, you can use your own Atlassian OAuth 2.0 (3LO) app instead:

1. Create an OAuth 2.0 integration in the Atlassian developer console.

2. Under Authorization, set the callback URL to https://app.testiny.io/api/v1/oauth/redirect/jira-cloud (for a self-hosted Testiny Server instance, use <your Testiny Server URL>/api/v1/oauth/redirect/jira-cloud).

3. Under Permissions, grant the Jira API scopes:

   • Permissions for User identity API:
     read:me
   • Permissions for Jira API -> Jira platform REST API:
     Classic scopes: read:jira-work, read:jira-user, write:jira-work
     Granular scopes: read:board-scope:jira-software, read:sprint:jira-software, read:project:jira

4. In the Testiny integration settings, enable "Use your own Atlassian OAuth app" and paste the app’s Client ID and Client Secret.

note

Changing the OAuth client requires re-authorization — the shared integration account and all personal accounts need to authorize the integration again.

Connecting projects

When you’ve successfully connected Testiny with Jira, you can now also install the Jira Marketplace app for a full two-way integration or skip this step for now and configure which projects you want to connect. To configure the mapping of the projects, click "Continue" or directly go to the "Projects" tab. Here, you can define the scope of the integration for:

• Testiny Projects

  • All projects
    By default, the integration is configured for all existing and future projects of your Testiny organization.
    You can also choose whether to use this integration for defects only, requirements only, or both.

  • Only specific projects If you want to configure an integration for specific Testiny projects only, select this option. Now you can select for which projects you want to enable this integration.
    You can also choose whether to use this integration for defects only, requirements only, or both.

• Jira Projects

  • All projects
    By default, the integration is configured for all projects.

  • Only specific projects
    If you want to configure an integration for specific projects only, select this option. Now you can select which projects you want to enable this integration for.

Jira Marketplace app

For a full bi-directional integration, install the Jira Marketplace app on the official Atlassian Marketplace enabling backwards linking from Jira to Testiny. You’re able to view testing activities done in Testiny directly within Jira — e.g. see which requirements in Jira are covered by which test cases or which bugs are linked to a certain test-run. By activating this integration, you gain full traceability from Jira as well as from Testiny.

note

You need admin rights in Jira to install the Jira Marketplace app from the Atlassian marketplace.

info

To configure the Jira Marketplace app with Testiny Server, please refer to the Testiny Server Documentation.

Installation and Configuration

• Install the app from the official Atlassian marketplace. You can also navigate in Jira to Apps > Find new apps and search for "Testiny".

• After installing the app, select "Configure" in the Jira Marketplace app.

• Follow the instructions to allow access to Testiny.
  A confirmation page titled "Link Jira to Testiny" opens in Testiny, showing the Jira site, integration and organization that will be linked.
  Click Confirm Link to establish the connection.

  info

  If your Testiny organization has more than one Jira integration that matches the same Jira site, you’ll be asked to choose which one to link.

When you’ve successfully connected your Jira instance with Testiny, you’re able to view testing activities also within Jira issues.

Upgrade to Forge

Atlassian is deprecating Connect Apps in Q4 2026, so we recommend updating the Testiny Jira Marketplace App to a newer Forge version (2.0.0+) before it reaches end of life.

What stays the same

• All your linked work items and configured integrations in Testiny
• Features and functionality

How to upgrade

• As a Jira admin, update the Marketplace App.
• Then, re-connect the app to Testiny. See the configuration steps above.

Legacy installations (app versions before 2.0.0)

info

We recommend updating the Jira Marketplace App to a newer version (2.0.0+). Atlassian is deprecating Connect Apps and prior versions will reach end of life in Q4 2026.

Newer versions of the Jira Marketplace app (2.0.0 and later) connect to Testiny without an installation token, as described above. For existing legacy installations (versions before 2.0.0), establish the connection with an installation token instead:

• Create an installation token for the Jira Marketplace app in Testiny. Go to the "Details" tab of your Jira Cloud integration and click the button Create installation token.
• Copy the installation token, paste it inside the app’s configuration window in Jira into the field showing "Paste Testiny installation token" and press Connect.

Using the Jira Integration

Viewing Testiny Activities inside Jira

From any Jira issue you can see all Testiny entities that link the current issue (including test cases, test run results, etc.).
Using these links you can directly access the relating Testiny entry to lookup further details.

Creating or linking Jira Issues

Within Testiny, you can link test runs and executions to Jira issues. If you find a bug during your tests, you can create an issue in Jira directly from Testiny. It is also possible to link requirements in Jira to test cases or create requirements in Jira directly from Testiny to build up your test coverage matrix.

Jira issues can be created (or linked to) in Testiny from the following entities:

• Test cases
  It is possible to link requirements to test cases (a requirement can be any type of Jira issue) or to create a requirement that is automatically linked to the test case.

• Test runs and test executions
  Testiny provides the ability to create defects (or link an existing issue) directly from a test run or a test execution.

Creating issues

When creating a requirement or a defect from Testiny, a create dialog will open where you can set the fields for the Jira issue. In this dialog you can select the Jira project, the issue type and set any other fields that may be required. Click Create to confirm. If pop-ups are allowed, the newly created issue will open in a new browser tab. Otherwise, a small window with the details and a link to the issue will appear.

Depending on your configuration and the integration’s requirements, you can select

• a project via dropdown
• issue type via dropdown
• any relevant custom fields via multi-select (optional)

You can also choose to Add test steps to description, and if there are comments on the test case, an option to Add comments to description will appear.

Linking existing issues

When linking a requirement or a defect, a search dialog will open where you can search all existing issues directly in Testiny (no need to switch to Jira) and select the issue you want to link.

info

The Jira integration lets you include additional fields (for example a Reporter or Assignee) in the Create dialog. Use the Select fields dropdown to add any fields available through the external integration. Ensure that the necessary permissions are configured in Jira.

Accessing Jira Issues in Testiny

Connecting Jira with Testiny allows you to directly look up and access Jira issues.
Testiny shows essential information such as the issue status or the issue type inline.
Essential information like the issue title or issue status is synchronized into Testiny. This means that even if the integration is unavailable, Testiny remains unaffected and will still display the synchronized data.

For further details on linked issues, the issue can be opened directly from Testiny by clicking the issue ID. Testiny supports issue links in various places:

• Test cases
• Test runs
• Test results

If you have any further questions or need to get assistance, please do not hesitate to ask in the forum. Our support team is always available to assist you.

Technical details: How does the integration work?

If you’re curious how the integration works, the next section might be interesting for you :-)

• Testiny Jira Marketplace app:
  The Jira Marketplace app (an Atlassian app, installed from the Atlassian Marketplace) provides the functionality to authenticate with Jira and link a Testiny organization with a specific Jira instance. Inside Jira, details from Testiny (like status of a test run, a test result linked to a defect) are directly rendered by the Atlassian app (inside an iframe). Only the Jira instance that was linked to the Testiny organization is allowed to access the Jira interface for the respective organization.

• Looking up issues: Looking up issues in Testiny does not require the Jira Marketplace app. Testiny directly interacts with the Jira REST API and retrieves live data. Data is retrieved in the context of the shared integration account that authorized the integration (or, for legacy token-based integrations, the user the API token belongs to).

• Creating issues: Testiny automatically creates a new issue (using the default type from the Jira integration for requirements or defects) directly in Jira using the Jira REST API. If the browser settings allow opening a new window/pop-up, the issue is automatically opened in a new tab and can be adjusted immediately. Depending on the issue creation settings, the issue is created in the context of the integration’s shared integration account or the user’s personal Jira account.

• Linking existing issues: Searching for issues works directly using the Jira REST API. Users can directly link with existing issues.

Jira Server/Data Center

Testiny also supports an integration with Jira Server or Jira Data-Center. Please have a look at the Jira Server/Data-Center documentation.