From January 2023, old versions of the PractiTest plugin for Jira (below 3.0), are no longer supported.
If your integration is already configured and you want to learn about the actual usage of the integration, please go here
Seamless management of a comprehensive end-to-end QA and development process using PractiTest and Jira great solutions. Following this simple setup, your JIRA Server instance will be automatically updated with issues arising during testing with PractiTest, though you can still add details in JIRA about each issue. PractiTest also allows users to present a single, uniform view covering requirements, tests, and issues.
Table of Contents
- PractiTest Jira Server/DC Plugin ver 3.0.x - Jira Server versions 7.3.1 and above and Jira DC versions 7.5.0 and above
- Upgrade from PractiTest Jira plugin version up to 2.4.2 - to plugin version 3.0.x
- How to use JIRA 2 way integration
- JIRA – Two way integration troubleshooting
PractiTest Jira Server/DC Plugin ver 3.0.x - Jira Server versions 7.3.1 and above and Jira DC versions 7.5.0 and above
Note: The configuration can only be set by a user with PractiTest account owner level permissions, and Jira admin-level permissions.
Configuration Steps
- Account integration settings
- Create and configure Application Link in Jira
- Create a Webhook in Jira
- Project integration settings
- Field mapping configuration
Account integration settings
In PractiTest:-
Go to Account settings - Integrations tab - select JIRA Server and click the 'Create token and continue with JIRA Server integration'.
Note: Only in case you would like to use the basic authentication method, check 'Use Basic authentication:' and enter username and password. This option is less recommended -
The following screen will appear:
-
Click on the “Administration” link on the top right (Settings). Click on apps/add-ons (depends on the Jira version you are using) - 'Find new apps/add-ons'
- Search for PractiTest in atlassian marketplace.
-
In the manage apps/add-ons window, click PractiTest - Configure.
-
Fill in the API-Token you got in the PractiTest Account Settings - Integrations tab into the Plugin configuration page.
-
By default, all Jira projects will appear as manageable in PractiTest. If you want to include only part of your Jira projects in PractiTest integration and exclude others, please check “Enable PractiTest addon for the following projects only”, and check the specific projects that you wish to integrate. Any project that you don’t check will not be integrated.
-
In the same page press show more
-
Fill in the URL fields as follows:
- The Host should be https://api.practitest.com/ for prod users (USA), and https://eu1-prod.practitest.app/ for EU users.
- The Proxy should be wss://proxy.practitest.com:443/ for prod users (USA), and wss://eu1-jira-proxy-prod.practitest.app:443/ for EU users.
- Press save.
If you are working on PractiTest Jira plugin version up to 2.4.2, please scroll down for next steps.
Create an Application Link in your Jira Server / Datacenter
-
In Jira Administration (Settings), Select Applications and then select application links.
- In the Enter the URL of the application you want to link field, enter the base URL for your PractiTest App. Your app base URL can be found in PractiTest under Account Settings - Integrations.
- Click 'Create new link'
-
Fill in the fields with the data below:
- Application Name box type : PractiTest
- Application Type: accept the default value of Generic Application
- Click Continue
NOTE: If you’re prompted with the following message: ‘The supplied Application URL has redirected once. Please check the redirected URL field to ensure this is a URL that you trust’, check ‘Use this URL’ checkbox , click Continue and leave the new URL as is.
Configure the Application Link in Jira
Note: You’ll need to have the Public key, Consumer key and Callback URL from the PractiTest integration settings page
-
Locate the PractiTest Application Link that you created in the previous section and click the Edit (pencil) icon.
- In the Configure dialog box, click Incoming Authentication on the bottom left and paste the following in the appropriate boxes:
- Consumer key: PTOauthKey
- Consumer Name: PractiTest Application
-
Public Key:
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxi5O5khVZEpqaVUG13mQw2PM/SCAdx8b2IvkOIJIBGgQe1UBATCUnENlbfAmU1y5VmzzlLxtnHq4E6gTtwCNQjPzwLtFV60Ys4kQG73j78CHw+oRGuza+PQiHZb6exwbaZmaNXaDbV0TuZzO4J/A3Qxo5vFWKlG0VI4Q3xfrv1fN6WJMeJLBlhbyFuC6qNTcYmXfIxPLMsTvvHvco/9ZjME+lyivUOHUj1YY4pqI4sIotLVjF5RXYfHQrLYJ/+3FBKnH0uAwj4dSyp+mVq3/IB5lI0GSnJo41xr1z0jY0M0bJEri+56rQqc0qs5lDWtDVvuzok4XvaCIy3MDnhOkPQIDAQAB -
Consumer Callback URL:
*Please find your Consumer Callback URL in the PractiTest Account Integrations Settings window*
-
Click the Save button, and then click Close
Note: In case you are not allowed to configure integrations by using application links, use the basic authentication method (less preferred) instead where username and password will be used.
Create a WebHook in Jira
-
Go to Jira - Administration (Settings) - System - scroll down to Webhook
-
Click ‘Create a WebHook’
- Paste the WebHook URL you got on the Integration Settings screen in PractiTest
-
In the same window, scroll down to Events section - Issue related events. In the JQL text box, insert: project in ("your integrated projects separated by commas").
In the 'Issue' column underneath, check 'updated'. In the 'Issue Link' column, check 'Created' and 'Deleted'. In the 'Comment' column check 'created', 'Updated' and 'Deleted'. - Press 'Create'
Go back to PractiTest - Account Settings - Integrations - and verify that the connection status is 'Connected' by pressing “Test Connection”.
Configure your integrated JIRA projects:
- In PractiTest, go to Settings - Integrations - press 'Activate' on issue integration section - and then press ‘activate’ again on the Jira integration configured in your account.
-
Add a new row for each of the Jira projects you want to integrate with this PractiTest project, select the relevant project and issue type.
-
At the bottom of the page you can allow PractiTest to create internal issues that will not be synced to Jira. If you choose this option you will also have the choice to present the PractiTest ID for all issues including the Jira synced issues. If you do not choose to allow PractiTest to create internal issues, PractiTest will present the Jira ID for each issue.
Mapping your Jira fields to your PractiTest fields
Note: Field sync needs to be configured for each PractiTest project separately.
Note: Linked Issue field (for example "is blocked by" or "relates to") will be automatically added to the "Fail & Issue" modal box in case the project and the issue type you choose contain it, and you don't need to map it here.
In the project Integration settings window, press settings and choose the ‘Jira project mapped fields’ tab.

- Choose the Jira field you want to map. You can choose Text Fields, Single select lists (text, number, users), Multi-lists, Number, Date, Sprint, Epic link or Team type fields. (Team field can only be maaped when using Jira Cloud).
- Tick the “Add to ‘Fail & Issue’” box if you want this field to appear when reporting an issue from PractiTest to Jira.
- Choose if and where you want to map this Jira field to - to a PractiTest dedicated field, or to the description of the PractiTest entity. Please note: If you choose to map it to a field - the list of PractiTest fields that will appear will contain only custom fields that match the type of the Jira field you chose (text-text, number-number etc. Sprint, Epic link and Team fields can be mapped to list type fields in PractiTest) and are also linked to either requirements or issues. If you chose the Jira Priority field, you will be able to map it to PractiTest Priority system field.
- Once you choose to map to fields, you will need to choose whether to present the data in the issues field or in the requirement field, or both. If the PractiTest field you chose is linked only to one of them, then you will have only that option to map to.
Syncing Jira filters to keep updating PractiTest with its issues
To sync a Jira filter into PractiTest in a way that will keep syncing the issues in it to PractiTest, go to your project integration settings, choose the “Auto sync filters” tab.
Your PractiTest user will connect to your Jira user upon the first time of either Import Issue/filter or Create Issue.
Upgrade from PractiTest Jira plugin version up to 2.4.2 - to plugin version 3.0.x
Configuration Steps
- Update plugin in Jira
- Create and configure Application Link in Jira
- Create a Webhook in Jira
- Delete pt_id
Update plugin in Jira
- Click on the “Administration” link on the top right (Settings). Click on apps/add-ons (depends on the Jira version you are using)
- Click ‘Manage add-ons/Apps’
- In the ‘Manage add-ons/Apps’ window, click PractiTest - Update.

Create an Application Link in your Jira Server / Datacenter
-
In Jira Administration (Settings), Select Applications and then select application links.
- In the Enter the URL of the application you want to link field, enter the base URL for your PractiTest App. Your app base URL can be found in PractiTest under Account Settings - Integrations.
- Click 'Create new link'
-
Fill in the fields with the data below:
- Application Name box type : PractiTest
- Application Type: accept the default value of Generic Application
- Click Continue
NOTE: If you’re prompted with the following message: ‘The supplied Application URL has redirected once. Please check the redirected URL field to ensure this is a URL that you trust’, check ‘Use this URL’ checkbox , click Continue and leave the new URL as is.
Configure the Application Link in Jira
Note: You’ll need to have the Public key, Consumer key and Callback URL from the PractiTest integration settings page
-
Locate the PractiTest Application Link that you created in the previous section and click the Edit (pencil) icon.
- In the Configure dialog box, click Incoming Authentication on the bottom left and paste the following in the appropriate boxes:
- Consumer key: PTOauthKey
- Consumer Name: PractiTest Application
-
Public Key:
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxi5O5khVZEpqaVUG13mQw2PM/SCAdx8b2IvkOIJIBGgQe1UBATCUnENlbfAmU1y5VmzzlLxtnHq4E6gTtwCNQjPzwLtFV60Ys4kQG73j78CHw+oRGuza+PQiHZb6exwbaZmaNXaDbV0TuZzO4J/A3Qxo5vFWKlG0VI4Q3xfrv1fN6WJMeJLBlhbyFuC6qNTcYmXfIxPLMsTvvHvco/9ZjME+lyivUOHUj1YY4pqI4sIotLVjF5RXYfHQrLYJ/+3FBKnH0uAwj4dSyp+mVq3/IB5lI0GSnJo41xr1z0jY0M0bJEri+56rQqc0qs5lDWtDVvuzok4XvaCIy3MDnhOkPQIDAQAB -
Consumer Callback URL:
*Please find your Consumer Callback URL in the PractiTest Account Integrations Settings window*
-
Click the Save button, and then click Close
Note: In case you are not allowed to configure integrations by using application links, use the basic authentication method (less preferred) instead where username and password will be used.
Create a WebHook in Jira
-
Go to Jira - Administration (Settings) - System - scroll down to Webhook
-
Click ‘Create a WebHook’
- Paste the WebHook URL you got on the Integration Settings screen in PractiTest
-
In the same window, scroll down to Events section - Issue related events. In the JQL text box, insert: project in ("your integrated projects separated by commas").
In the 'Issue' column underneath, check 'updated'. In the 'Issue Link' column, check 'Created' and 'Deleted'. In the 'Comment' column check 'created', 'Updated' and 'Deleted'. - Press 'Create'
Delete pt_id
- In Jira administration (Settings) window, go to ‘issues’, then scroll down on the left to ‘custom fields’
- On the ‘pt-id’ custom field, click the settings icon on the right and press ‘Delete’. Press ‘Delete’ in the following screen as well.
Go back to PractiTest - Account Settings - Integrations - and verify that the connection status is 'Connected' by pressing “Test Connection”.