The main advantage of this integration option is that it allows you to integrate your Jira Server or Jira DataCenter without any additional installations, and without using any plugins or add-ons.

On the other hand, if you choose to use the no-plugin integration with Jira, PractiTest panels (Linked Results and Linked Tests), that are available for users who are using the integration with PractiTest's plugin, will not be available for you in your integtated Jira tickets.

Note: The two-way integration is supported only under PractiTest’s Enterprise and Unlimited licenses

Page Table of Contents

Configuration
Report issues from PractiTest to Jira
Importing Requirements and Defects from JIRA into PractiTest

Configuration

Note: The configuration can only be set by a user with PractiTest account owner level permissions, and Jira admin-level permissions.

Configuration steps:

  1. As the first step, you need to create an Application Link in your Jira Server / Datacenter. Follow the instructions on this page to create the application link. Paste the values below for the following 3 fields:
    • Consumer key: PTOauthKey
    • Public Key:
      MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCz+mcc7WKJHBZtgLpiS93z1qtkBuvSC7oJgJTqFy2b9CbeSsjR+vkxCvwyATezaBmv8DmsfHV9Iitkjo/+Rwidcrcv0HP/LUBbPI8I297nOaaS+I0EV7uOL+GbZz9uI9ggSEhO2V3Q6dGMztZizjYJS3pYwQYeaoMhyRgW7KFvpwIDAQAB
    • Consumer Callback:

      [PT-server-url]/integrations/jira_oauth/set_oauth_verification

      PT-server-url : https://prod.practitest.com/ , https://prod-eu1.practitest.app ,etc.

      Note: There are some JIRA Server/DC versions that don't allow to insert Consumer Callback URL when creating the application link. In case you are experiencing the issue, first create the application link, then edit it, go to 'Incoming Authentication', press 'Delete' and insert relevant details including Consumer Callback URL

      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 (see #3 about Account Settings).

  2. In Jira, create a custom field of the type 'Number' and look for its ID (the custom field ID is requeired). Instructions for creating the field:
    • Goto Jira Settings - Issues - Custom Fields Create new Jira custom field
    • Add Custom Field Add new custom field - Jira
    • Choose the 'Number' type Number type custom field
      1. Enter a name for your custom field
      2. Get the custom field ID from the URL of the new field's page (in our example field id is : 10003) Custom field ID via URL
      3. Check the boxes next to the relevant screens and click 'Update' Link relevant jira screens
    * You can also get the custom field ID from the ‘Custom fields’ page, by navigating to the specific field and pressing settings - configure. From this screen, you can get a Url with the custom field's ID as shown in the figure below. Custom field configurationCustom field configuration retrieve ID
  3. In PractiTest, create an integration with 'Jira Server No Plugin'
    • Go to Account Settings - Integrations
    • Select ‘JIRA Server No Plugin’
      1. Paste your Jira Base URL
      2. Paste ID of the custom field you created in Jira
      3. Click the 'Create token and continue with JIRA Server no plugin integration'. Note:Only in case you would like to use the basic authentication method, check 'Use Basic authentication:' and enter username and password.
      The following screen will appear: Jira account level integration settings
  4. Create a WebHook in Jira
    • Go to Jira - Settings - System - Webhook
    • Click ‘Create a WebHook’
      1. Paste the WebHook URL you got on step 3 (from PractiTest's side)
      2. Go to Events - Issue related events and check 'created' and 'updated'. In the JQL text box, insert: cf[your custom field ID] != empty Webhook customization
  5. Connect your PractiTest user to your Jira user: Goto Project - Integrations. There, you will see a system message for linking the users. Click this message and the linkage will happen automatically. link jira and pt users Once done - you can set the project level integration settings.Note:this JIRA user linkage is irrelevant when using the basic authentication method.

Report issues from PractiTest to Jira

* The integration's first phase
  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.support_seeing_issues_in_JIRANote: Multi projects and Multi types – Set different project 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_project3. Having saved the Issue (step 2), 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 they are changed in JIRA
  • PractiTest Info section in JIRA: All JIRA Issues and Stories that were reported/imported via PractiTest will include the section within the description field displaying PractiTest information. Make sure not to remove if from entities in JIRA.

Importing Requirements and Defects from JIRA into PractiTest

    To import a requirement from JIRA, or to import an issue from Jira, press the arrow icon next to the ‘New ___’ button, and then press ‘Import a Requirement’ or ‘Sync a new issue from Jira’.
    import requirement from JIRA

    You will then have 2 options:

    IMPORT REQUIREMENTS Jira
  1. Import by tickets’ IDs - Enter the JIRA Issue key (Issue ID) to import into the PractiTest Requirements or Issues grid. You can import multiple tickets, separated by commas.
    ** While the requirement/Issue resides in PractiTest it is automatically updated when the JIRA ticket is updated.
  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 are filters that were starred by you.

<< Previous

Next >>