With PractiTest-Jira Integration, you can import or link requirements and issues from Jira into PractiTest and keep them automatically synchronized. You can also report a Jira issue directly from a PractiTest run.

Any PractiTest issue or requirement that is linked to a Jira issue will be updated when the value of the Jira issue status, name, description, comment, or any of your synchronized fields (Read about synching more Jira fields here) is changed or added. You can also define fields that can be edited in PractiTest and updated accordingly in Jira. In Jira Cloud - All attachments in the Jira issue will be synced to PractiTest and vice versa.

You can 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).

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.
    • At the bottom of the modal box you will find:
      • Jira fields that were mapped to PractiTest fields in project integration settings (read how to map Jira fields here)
      • Fields that are set to required in your integrated Jira projects
      • Linked Issues field in case the Jira project you are reporting to and the issue type you chose contain the linked issues field
    • Press the button to create the issue in Jira.

      • Jira Modal Box

    In case you defined your integration to allow internal PractiTest issue creation (that will not be created in Jira), your "Fail & Issue" button will open 2 options. The first will create the issue in PractiTest only, and the second will create the ticket in Jira as explained above.
    Fail & Issue options
    Read more about it here

  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 updating Jira when you change the value of the issue status, name, description, or any of your synchronized fields (Read about synching more Jira fields here) or when you add a comment. If you are using Jira Cloud, any attachments in PractiTest will also be updated in Jira. Deleting a synced-to-Jira attachment in PractiTest, will not affect the Jira attachment.
    • Manage Issues in PractiTest: All Issues connected to Jira will be seen in PractiTest and synced automatically as there are changes to the name, description, status, synced fields, or comments in Jira. If you are using Jira Cloud, any attachment in Jira (besides "Internal Note" in ITSM type project in Jira) will also be synced to PractiTest with an indication that the attachment is synced from Jira.

Importing and syncing Jira Tickets as PractiTest’s Requirements

There are 4 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 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: *This action will sync the current issues in the selected filter into PractiTest, but will not keep syncing the filter in case changes will be made to it (aka new issues that will be added to the filter will not be synced).*
    Click on the down arrow next to the “New Requirement” button and select “Sync a new 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 PractiTest with a Jira filter 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.
    sync jira filter to Practitest
    Choose the Jira filter you want to sync and the PractiTest entity you want to sync it to - Requirements or issues. Press “Update issue integration” and from now on, every 4 hours, PractiTest will sync to all the issues in this filter. You can add as many filters as you want but please note that if the filter contains issues from projects that are not integrated with PractiTest (as defined in the first tab “Jira Project info & issue type”), they will not be synced.
  4. 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 PractiTest plugin.

Importing and syncing Jira tickets into PractiTest’s Issues Module

There are 3 ways to import existing tickets from Jira as Issues in PractiTest

  1. Import by IDs - Paste the ID of your Jira ticket. You can Synch issues in bulk, separated by commas.
    sync issue jira
  2. Import by Jira filters - *This action will sync the current issues in the selected filter into PractiTest, but will not keep syncing the filter in case changes will be made to it (new issues that will be added to the filter will not be synced).*
    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
  3. Import by Jira filters and keep updating PractiTest with the filter’s 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.
    sync jira filter to Practitest
    Choose the Jira filter you want to sync and the PractiTest entity you want to sync it to - Requirements or issues. Press “Update issue integration” and from now on, every 4 hours, PractiTest will sync to all the issues in this filter. You can add as many filters as you want but please note that if the filter contains issues from projects that are not integrated with PractiTest (as defined in the first tab “Jira Project info & issue type”), they will not be synced.

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-hand side of the screen or from within a run.

New Issue button

Inside your run window, you can use the "Fail & Issue" button to report a bug to Jira or only to PractiTest.
fail n issue options

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 the ‘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.

Receiving 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 - The PractiTest plugin should be updated to version 3.0.5 to support the update Jira fields feature

PractiTest information 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 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, and 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

View Comments and attachments

*Attachments sync is available for Jira Cloud only

All the comments and attachments from the synced PractiTest issue/requirement will appear in Jira. Any change to a PractiTest comment will be reflected in Jira.

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