With PractiTest-Jira Integration, you can import or link requirements and issues from Jira into PractiTest and keep them automatically synchronized. You can then complete the end-to-end testing process using more PractiTest traceability functionalities like linking requirements to tests in the test library, test runs, reporting etc.

Table of Contents

Running tests in PractiTest, seeing issues in Jira

Note: On the first time you report an issue to Jira from a test run, you will see ‘click here to link your Jira User’ and once you click, the linkage between your PractiTest user and your Jira user will be formed (according to the GDPR regulations).

Jira No-Plugin Users Note: If you are using No Plugin, the same linkage will happen when you go to Project Integration Settings

Basic Authentication Method Accounts Note: For basic auth configured accounts - there’s no linkage of PractiTest user to Jira user. For each interaction the service account supplies, username and password will be used.

  1. Run your tests normally.
    • When you encounter an issue click the 'Fail & Issue' icon (or prior to that, save the “Step’s Actual Results”). Fail & Issue
    • Choose the Jira project and issue type you want to report the issue to from the drop down ‘Project’ list in the modal box (this drop down is adjusted according to your project integration settings).
    • You will see all the test data already pre-entered, including the summary and description pre-filled with steps you’ve executed, and the failed “Step’s Actual Results” (if this information was already entered in PractiTest).
    • You may add more details to the issue.
    • If you mapped more Jira fields to PractiTest fields in project integration settings (read how to map Jira fields here) or if you have fields that are set to required in your integrated Jira projects, they will appear at the bottom of the modal box.
    • Press the button to create the issue in Jira.

    • Jira Modal Box
  2. You can also link existing issues to your step run- this option allows you to link your failing test step to existing Jira tickets. You can link to more than one issue at a time, using commas between the issues IDs. link existing jira issue
  3. After creating the Issue, the plugin does the rest, keeping the issue and test step synchronized.
    • PractiTest will continue to be updated when you change the value of the issue status, name, description or any of your synchronized fields (Read about synching more Jira fields here).
    • Manage Issues in PractiTest: All Issues connected to Jira will be seen in PractiTest and synced automatically as there are changes in Jira.

Importing and synching Jira Tickets as PractiTest’s Requirements

There are 3 ways to import & Sync Jira Tickets as requirements to PractiTest:

  1. Import & Sync by tickets’ IDs from PractiTest: Click on the down arrow next to the “New Requirement” button and select “Sync a new a Requirement from Jira”.
    Import requirements from Jira
    In the requirements import modal box, choose import by tickets’ IDs - you can import either an individual ticket or multiple tickets separated by commas. Import requirements from Jira
  2. Import by Jira filters from PractiTest: Click on the down arrow next to the “New Requirement” button and select “Sync a new a Requirement from Jira”, as written above. In the requirements import modal box, choose 'Jira Filter Name' then choose the name of the relevant Jira filter you want to import. The drop-down list of filters that you see in the modal box, is a list of filters that were either created by you or starred by you.
    Note: If there are tickets from projects that are not integrated with PractiTest within those filters, they won't get imported.
  3. Sync a Jira ticket to a PractiTest requirement from within Jira, and create a new test in PractiTest to cover it (Not available for No-Plugin integration. For no-plugin, you will see a link inside the description for more information): Press on the ‘Create Test & Link a Requirement’ option on the top-right side of the PractiTest panel (Please note you might need to scroll down the panel to get to the button).
    practitest in jira
    The ticket will automatically be imported to PractiTest as a requirement, and you will be redirected to a newly created test that will be automatically linked to this requirement (can be viewed in the traceability tab). The requirement will also appear under the Requirements module in PractiTest with the ticket name and with a link to the Jira ticket.
    *In case you do not see the ‘Create Test & Link a Requirement’ option in your PractiTest panel in Jira, your PractiTest plugin in Jira might not be up to date. Please go to Settings > Apps > Manage Apps and press 'Update' under the PractiTets plugin.

Synching Jira tickets into PractiTest’s Issues Module

In order to import existing tickets from Jira as Issues in PractiTest, click on the down arrow next to “New Issue” button, and select “Sync a new Issue from Jira” option.
sync issue jira
You have two options for synching new Jira tickets.

  1. Import by IDs - Paste the ID of your Jira ticket. You can Synch issues in bulk, separated by commas.
  2. Import by Jira filters - check the 'Jira Filter Name' on the import modal box and then choose the name of the relevant Jira filter you want to import. The drop-down list of filters that you see in the modal box displays filters that were either created by you or starred by you. Synch issues from Jira filter

Note: If there are tickets from projects that are not integrated with PractiTest within those filters, they won't get imported.

Creating new issues in PractiTest internal issues module

You can also decide to create issues in PractiTest’s internal issues module directly. To enable this option, navigate to Settings - Integrations. Then click on ‘Settings’ next to ‘Current Issue Integration’.

Project Integration Settings

Then, tick the ‘Allow to create Issues in PractiTest that are not linked to Integration’ box.

Enable internal issues creation

Once this option is enabled, you would be able to create new issues in the PractiTest issues module, using the ‘New Issue’ button on the top left end side of the screen.

New Issue button

If you want to link an issue that was created in the PractiTest issues module to Jira later on, you can do that from the 'Actions' section of the issue.

Create new issue in Jira

When clicking the ‘Create issue on Jira’ item, a new modal window will open. Fill in the issue’s information, and click ‘Create the issue in Jira’ item.

Issues Modal Box

The issue will be then created in your Jira project, and will be linked with the issue created in PractiTest.

Please note, that the information you fill in the modal window will override the information existing for the fields you filled in the internal issues.

Linking existing Requirements in PractiTest to Jira Issues

  1. Select an existing Requirement in PractiTest.
  2. Click on the “Actions” button and then “Link to Jira issue” in the upper right corner.
  3. Enter the Jira Issue key. * You can choose to un-link or link back any Requirement at any point. link existing requirement

Working with mapped Jira fields in PractiTest

To configure the mapping between your Jira fields to your PractiTest fields, follow these simple configuration steps.

Changing field value in PractiTest or Jira

Working with mapped fields allows you to update your fields from either PractiTest or Jira. Once the mapping is configured, when populating a field from a PractiTest Requirement or Issue, the field value change will be reflected in the Jira ticket automatically. When updated from Jira, the change will be reflected in PractiTest.

Adding fields to issue/bug report from PractiTest to Jira

In addition to Issues and Requirements, you can also decide to display your Jira fields in the modal box that comes up when you report an issue from a test run, and populate your Jira fields directly from the modal box.

Recieving field information from Jira to PractiTest entity's description field

You can also map Jira fields to the description field of either your requirements, or your issues. However, when using this type of mapping, you will only be able to update the field on the Jira side.

Editing Jira field values in PractiTest

Once the mapping is configured between fields, a new section will appear in your requirements and issues, depending on the visibility you decided on. The new section will include the mapped Jira fields. To edit the fields’ values, click on ‘Edit Jira Fields’, enter the relevant values, then click on ‘Update Jira’. The value change will be reflected in PractiTest, and the relevant Jira Ticket.

Field mapping section

Field mapping popup

* For Jira Server users - PractiTest plugin should be updated to version 3.0.5 to support the update Jira fields feature

PractiTest panel inside Jira (Not valid for Jira No-Plugin integration)

*Jira no plugin users will see inside the description a link to PractiTest with the panel information .

*Jira Server users: If you cannot see the panel as described below, Please make sure your PractiTest plugin in Jira is up to date. In Jira, go to Settings > Apps > Manage Apps and press 'Update' under the PractiTets plugin.

A Jira ticket can be connected to PractiTest in 2 main ways - as a user story/requirement covered by tests in PractiTest, and/or as a bug/issue that originated from a test run in PractiTest. In both cases, you will see live updates from PractiTest in your Jira ticket.

View test runs information

If the ticket in Jira was originated in a run in PractiTest, you will have the link to the test run and you will see its details including Run date, Run status, run steps colored according to their status (up to 5 steps will appear including the step that created the issue that will be bold), tester and a link to the original test in the test library. jira panel test run

View covering tests information

If the ticket in Jira is synced to a PractiTest requirement and covered by tests, you will have a link to the tests covering the requirement and see information about them including the test steps, last run date, last run status and test author. jira panel test information

Sync Jira ticket to a PractiTest Requirement and create a test that covers it from Jira

Inside this panel, you also have the ability to sync the Jira ticket you are at to a PractiTest Requirement and create a test that covers it - all by pressing the ‘Create Test & Link a Requirement’. Read more about it here jira panel create test

How to use PractiTest Jira plugin version up to 2.4.x:

Importing Requirements and Defects from Jira into PractiTest

  1. To import a requirement from Jira, go to the Requirements module, press the icon next to the ‘New Requirement’ button, press ‘Sync a new Requirement’. Synch requirements
  2. Enter the Jira Issue key (Issue ID) to import into the PractiTest Requirements grid. You can import multiple tickets, separated by commas.
    ** While the requirement resides in PractiTest it is automatically updated when the Jira ticket is updated.
    Import Requirements Successful
  3. To sync a defect from Jira, go to the Issues module, press the icon next to the ‘New Issue’ button, press ‘Sync a new issue from Jira’.
  4. Enter the Jira Issue key (Issue ID) to import into the PractiTest Issues grid. You can synch a few defects at a time separated by commas
    ** While the issue resides in PractiTest it is automatically updated when updated in Jira.

Linking existing Requirements in PractiTest to Jira Issues

  1. Select an existing Requirement in PractiTest.
  2. Click on the “Link” icon in the upper right corner.
  3. Enter the Jira Issue key.
    * You can choose to un-link or link back any Requirement at any point. Link existing requirement

The PractiTest-Jira Integration means you can import or link requirements from Jira into PractiTest and then complete the end-to-end testing process using other PractiTest traceability functionalities by linking requirements to tests in the test library, test runs, reporting etc.

Running tests in PractiTest, seeing issues in Jira

  1. Run your tests normally.
    When you encounter an issue click the Fail & Issue icon (or prior to that, save the “Step’s Actual Results”).
  2. A new browser tab or window (based on the configuration of your browser) will be launched opening your Jira new issue page. You will see all the test data already pre-entered, including the summary and description pre-filled with steps you’ve executed, and the failed “Step’s Actual Results” (if this information was already entered in PractiTest). You may add more details to the issue. Then Save. Fail & Issue

    Note: Multi projects and Multi types – Set different projects and different issue types to open directly in Jira. Once you run the test, when you put your mouse over ‘Fail and Issue’ you can select which project or type (based on your previous configuration) you’ll open in Jira.
    Jira multi-projects and issue types

  3. After saving the issue, the plugin does the rest, keeping the issue and test step synchronized.

    • PractiTest will continue to be updated even when you change issue status, name or description.
    • Manage Issues in PractiTest: All Issues connected to Jira will be seen in PractiTest and synced automatically as there are changes in Jira. Synch an issue from Jira

Embedded PractiTest Test cases and Test runs within your Jira Issues (Not valid for Jira No-Plugin integration)

  1. View live updated information from PractiTest directly in Jira.
  2. See the Test runs from practiTest that are linked to any Jira issues.
  3. See the linked Test cases from Practitest that cover any Jira user story or requirement. Jira pannels