Introducing Agentic Testing — describe Salesforce tests in plain English.Learn more →
Partner IntegrationVerified by SimpleTest

Native Jira Software

Works where you work.

Automatically sync test results and generate bug tickets with rich context directly in Jira.

Turnkey Setup
Bi-directional Sync
Enterprise SLA
Defect Management

Stop manually filing bugs.

When a test fails, SimpleTest AI automatically creates a Jira ticket populated with screenshots, network logs, and a step-by-step reproduction path.

Auto-Bug Creation

Configure rules to automatically create bugs when critical regression suites fail.

Rich Context

Tickets include DOM snapshots, Console logs, and MP4 video recordings of the failure.

Two-Way Sync

When a developer closes the Jira ticket, SimpleTest automatically re-runs the failed test.

BUG-4012
[Regression] Opportunity Stage Cannot Be Changed to Closed Won
AssertionError: Expected 'toastMessage' to contain 'Saved', but got 'FIELD_CUSTOM_VALIDATION_EXCEPTION'
Steps to Reproduce (Auto-generated):
  1. Navigate to Opportunity 'Global Acme'
  2. Click 'Edit'
  3. Change Stage to 'Closed Won'
  4. Click 'Save'
  5. Validation Error Triggers (See attached video)

How to connect with Jira Software

Get up and running in minutes with our turnkey integration. No complex setup or maintenance required.

1

Generate API Key

Log into your SimpleTest dashboard, navigate to Settings > API Keys, and generate a new key with CI/CD permissions.

2

Install Jira Software Integration

Install the native SimpleTest plugin/app from the Jira Software marketplace or add our CLI package to your pipeline.

3

Configure & Run

Add your API Key to your environment variables and point the integration to your specific Salesforce test suite ID.

Connect to Jira

Connected Jira execution.

Watch Jira connect, run Salesforce object paths, and open a ticket with steps, org, and evidence if a path fails. Passing runs sync back to the project.

Test Cases

TitleResult
Connect Jira ProjectQueued
Open the browserQueued
Enter Salesforce instanceQueued
Login - enter credentialsQueued
Click Sign InQueued
Go to Sales appQueued
Preparing the test dataQueued
Search Lightning recordsQueued
Validate LeadQueued
Validate AccountQueued
Validate ContactQueued
Validate OpportunityQueued
Validate QuoteQueued
Validate CaseQueued
CI quality gateQueued

Test execution

Waiting for run

0%

Starting

00:00.000/15 steps0 passed0 healedQueued
Starting Salesforce journey…
FAQ

Frequently Asked Questions

Ready to supercharge your Jira Software pipeline?

Stop waiting for overnight tests and start shipping Salesforce releases with confidence. Set up the Jira Software integration today.

Positioning

SimpleTest, defined.

SimpleTest sits in the pipeline you already run. Salesforce UI journeys become a required check — same as application tests.

What we address

What we address

  • Salesforce ships outside CICode is gated. Metadata and Lightning changes still wait for a UAT window.
  • Broken journeys after deployGearset, AutoRABIT, and GitHub ship the org. Nobody re-ran the quote or intake path.
  • Results live in another toolQA has a report. Engineering has a PR. Failures do not block the merge.
  • Scratch orgs and sandboxes driftEphemeral URLs and data never make it into the test run automatically.

What you get

What you get

  • Native pipeline gatesGitHub Actions, Jenkins, Azure DevOps, ModernOps, Gearset, and AutoRABIT.
  • Required status on the PRA failed Salesforce journey blocks merge the same way a failed unit test does.
  • Jira when it failsDefects open with steps, org, and screenshot — not a Slack screenshot.
  • Environment injectionScratch org and sandbox URLs flow into the suite. No manual re-pointing.