Jira and Probara stay in sync
Create Jira issues from the defects your testers find, keep their status in sync both ways, and show developers which test cases cover each story, right inside Jira.
Integrations are included in the Pro plan, and in the 14-day Pro trial every new organization starts with. Compare plans
From any defect, create a Jira issue prefilled with what the tester recorded: the run, the steps, the environment and configuration of the result, and its attachments.
An issue that already exists can be linked instead. Each Probara project files into the Jira projects mapped to it, with the issue type you choose.
When a Jira issue changes status, the linked defect follows its status category, and you can give any Jira status a Probara status of its own.
In the other direction, you choose which Jira status each Probara status moves the issue to. Priority, severity and comments sync in both directions.
| Jira status category | Probara defect status |
|---|---|
| To do | Open |
| In progress | In progress |
| Done | Resolved |
Link test cases to the Jira stories and epics they verify, one at a time or many at once. Then build a traceability report from the Jira projects you choose.
Each generated version is a frozen snapshot that lists the stories no test case covers yet. A linked case is flagged as stale when its story changed after the case was last edited, so drift shows up before a release does.
The Probara panel on each Jira issue shows its coverage, the test cases linked to it with their latest result, and the defects linked to it.
Jira users need no Probara account to see it, and Jira decides who can see and change what, with each viewer’s own Jira permissions.
Create your organization, connect your Jira Cloud site and file your first defect. Every new organization starts on a 14-day Pro trial, with no credit card.
