Loadmill
Learn moreSchedule a demo
  • Introduction
    • Loadmill - AI - Powered Solution
    • Deviceless mobile testing
      • Capturing traffic with Loadmill MITM Proxy
      • Loadmill desktop recorder
        • Generating test flows
      • Installing certificate on mobile devices
        • iOS certificate installation
        • Android certificate installation
      • Configuring proxy on mobile devices
        • iOS Wi-Fi settings
        • Android Wi-Fi settings
      • Troubleshooting
    • What is an API
      • API - Data Fetching
      • Quick examples of API requests
      • What is an API endpoint?
    • API Server Testing
      • Contract testing
      • Regression Testing
  • Quick Guide
    • Create Account
    • Download Test Composer
    • Register your first API flow
    • Running Your API Test
  • Loadmill Test Composer
    • Quickstart
    • Composer Layout
    • Filter Settings
  • Test Editor
    • Layout
    • Flows
      • Generated Flow Code
      • Test Flow editor
      • Flow Controls
      • Add CSV to Flow
      • Flow Execution
    • Steps
      • Request step
      • Code step
      • Extraction & Assertion step
      • Web Socket step
    • Extractions - Set Parameters
    • Assertions - Verify Response
    • Parameters
      • Parameter Execution Order
      • Test Suite Parameters
      • Parameters Sets
    • ⨍(⨯) FUNCTIONS
    • Postscript
      • Running Postscript
      • Accessing w/ Postscript
      • Validating Postscript
    • Login/Authentication Flow
    • Before & After Hooks
  • Load Testing
    • Load Test Editor
    • Load Testing Guide
    • Analyzing Load Test Results
    • Parameterized Load Test
    • Domain Verification
    • Configuration Files
    • Load Testing FAQs
    • Load Testing Troubleshooting
  • User Behavior Testing
    • Overview
    • Setup
    • Recording troubleshooting
    • Additional recording methods
    • Recording settings
    • How to work with Recordings
  • Auth
    • Okta SSO integration
    • API Tokens
    • Testing with CORS
    • REST API
  • Integrations
    • Loadmill Agent
    • CI integration
    • GitHub
      • CI integration
      • Data sync
    • GitLab
    • Bitbucket
    • Jira
    • New Relic
    • Slack integration
    • TestRail integration
    • Database Testing
    • Kafka Testing
    • Datadog Integration
    • ✉️Email Testing
    • Webhook Testing
    • Integrations FAQs
    • XRay
    • TestRail
    • gRPC Support
  • Collaboration
    • Collaboration
    • Teams
    • Groups & Reports
    • Test Suite Collaboration
    • Reviews
    • Shared Flows
    • Labels
  • Reporting
    • API Catalog & Coverage
      • API Catalog
        • Unique Entity ID's Mapping
        • Domain Mapping and grouping
        • Endpoints grouping
        • OpenAPI upload
      • Test Coverage
        • Generating API test coverage report
  • General
    • Billing
      • Usage report
    • Settings
      • 📈Analytics
        • Flow Run History
      • 🧳Import & Export
    • General FAQs
    • General troubleshooting
    • Comparisons
      • Loadmill vs. SoapUI
      • Loadmill vs. JMeter
      • Loadmill vs. Blazemeter
      • Loadmill vs. WebdriverIO
      • Loadmill vs. Potato
    • Miscellaneous
      • Running a Test Suite
      • Test Plan
      • API Testing troubleshooting
      • API Testing FAQs
      • Test Editor
        • API Tests - Data from CSV files
Powered by GitBook
On this page
  • Prerequisites
  • Setting up your Jira integration
  1. Integrations

Jira

PreviousBitbucketNextNew Relic

Last updated 2 years ago

Loadmill's Jira integration is a great way to automatically create tickets when tests fail or the expected outcome is not what was planned. You can set your own automatic ticket information directly from the Loadmill platform, making it easy to keep track of your testing progress. This integration is a great way to improve your workflow and ensure that your testing is always on track.

Prerequisites

Loadmill supports Jira version 5 and later versions.

Setting up your Jira integration

Step 1 - Getting Jira Credentials

Project Key

  1. Login to your Jira account.

  2. Navigate to Projects > View all projects

You can see the project key on the second column after the project name.

You can also create a new project and gather the project key by following the same steps above.

Jira Server URL

The Jira server url is the origin url of your Jira account: https://companyname.atlassian.net

API Token

  1. Navigate to Settings > Atlassian account settings.

  2. Select Security on the left menu.

  3. Click on "Create and manage API tokens".

Email

The email is the account email used for your Jira account.

Setting up Issue Types

Many projects have their own default issue types. Make sure the issue type of your choice is created in the project.

You can verify this by going through the following steps:

  1. Navigate to Projects > View all projects.

  2. Select the "Project Settings" by clicking on the 3 dots [•••] of the project.

  3. Select "Issue Types" from the left menu.

Make sure the issue type is present. You can create a new issue type by clicking on the "+ Add issue type" button at the end of the issue types menu.

Step 2 - Configuring Jira on Loadmill

  1. Login to your Loadmill Account

  2. Navigate to Settings > Integration.

  3. Paste all the credentials copied from Step 1.

Setting up Fields

Loadmill automatically sets the test description on the default fields of the issue type. You can add fields to the ticket layout by dragging and dropping the field type from the fields section to your right.

You can also set the type of description you wish to have aside from the default ones assigned and custom your ticket message using the Loadmill dynamic variables.

The Loadmill dynamic variables are dynamic variables taken from the test run to help creating a ticket more comfortably without the copy/paste hassle.

Those variables are:

  1. Test Environment: ${environment}

  2. Test Description: ${test_description}

  3. Test URL: ${test_url}

  4. Run URL: ${run_url}

  5. Failed Assertion: ${failed_assertions}

  6. HTTP Status: ${http_status}

  7. Error Message: ${error_message}

Quick Example

  1. Login to your Jira account and into your issue type layout.

  2. Drag and drop the "Paragraph" component to the ticket layout.

  3. Give a title to the "Paragraph" component and click on "Save". ex: Test Update

  4. Login to your Loadmill account > Go to Settings > Integrations > Add Jira Field.

  5. Select the component name your created from step 2 and 3.

  6. Give the value a description using the dynamic variables. ex: Test Update on ${environment}: ${test_description}

Below is a more detailed example of using dynamic variables

Test Update

env: ${environment}

test url: ${test_url}

test run: ${run_url}

http status: ${http_status}

description: ${test_description}

error message: ${error_message}

Creating the ticket

Once your integration is complete you can now run your test cases (or use the current test runs) and open a Jira ticket based on fail criteria.

  1. Select and run your test case/flow.

  2. Select the failed API requests of your failed test.

This will open a new tab with the ticket information with the dynamic values already set on the ticket description. You can add more information if and when you see fit and when ready click on the "Create" button at the bottom of the Jira ticket to create your ticket issue.

Select the integration. A window will pop up.

Click

Click on the button.