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 have fields that are set to required in your integrated Jira projects, they will appear at the bottom of the modal box. If you want to update Jira fields that do not appear in the modal box, please contact PractiTest support team and ask them to add the fields to the modal box (You can read more about this option here). Then 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. Import a ticket from within Jira as a requirement, and create a new test to cover it from a Jira ticket (Not available for No-Plugin integration. For no-plugin, you will see a link inside the description for more information): Press on the ‘Add Test’ option on the right-hand side of the ticket.
    practitest in jira
    Add test from 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.

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.

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
  4. Embedded PractiTest Test cases and Test runs within your JIRA Issues (Not valid for Jira No-Plugin integration)

    Jira no plugin users will see a link for more information inside the description.

    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

    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