Every Jira issue on a connected site can show a Probara panel. It gives the people who live in Jira — developers, product owners — the Probara side of that issue without leaving Jira: which test cases cover it and how they last ran, and which defects are linked to it. Jira users need no Probara account to see it.
The panel comes with the Probara for Jira app; there is nothing extra to install. This assumes a Jira site is connected; see Jira Cloud integration.
What the panel shows
Open a Jira issue and select Probara among the issue’s apps. The panel shows:
- Coverage — the state of the issue’s linked, active test cases, with a count per result. Failing means a covering case failed the last time it ran; Passing means every covering case passed the last time it ran; In progress means none failed, but some are untested, blocked or skipped; Not covered means no active test case is linked;
- Test cases — each linked case with its ID, title, latest result, run and when it ran. Archived cases are listed with a badge and not counted. Selecting a title opens the case in Probara (Jira asks before leaving);
- Defects — each linked defect with its ID, title and status.
The panel lists up to 50 test cases and 50 defects; a note says when Probara has more. Coverage counts the first 1,000 linked test cases; past that, the panel says so and links you to Probara.
When the panel has nothing to show, it says why:
| Message | Meaning |
|---|---|
| ”This Jira site is not connected to Probara” | No Probara organization is connected, or its plan does not include integrations |
| ”This Jira project is not shared with Probara” | The site is connected, but this Jira project is not in its allowed projects |
Neither message reveals which organization, if any, the site is connected to.
Who can see and change what
Jira decides, not Probara. Each time the panel loads, Probara asks Jira — with the viewer’s own Jira account — what that person may do on this issue.
| In the panel | Needs, in Jira |
|---|---|
| See the panel’s data | Permission to browse the issue’s project |
| Search, link and unlink test cases | Permission to edit the issue |
Probara remembers a “yes” for about a minute per person and issue, so a permission you remove in Jira can take up to a minute to stop showing the data. Linking and unlinking always ask Jira again.
What Jira users can see
Privacy. For every Jira project the connection shares, everyone Jira lets browse an issue sees all the Probara data linked to that issue — including data from Probara projects they are not a member of.
That data is the organization name, test case IDs and titles, latest result statuses, run names and dates, and defect IDs, titles and statuses. It does not include step details, comments, attachments or anything not linked to the issue.
You control this exposure in Probara:
- Allowed Jira projects on the connected site decide which Jira projects show the panel’s data at all. An empty list shares every project. See Choose which Jira projects Probara may use.
- Mappings decide which Probara projects can link to a Jira project in the first place: a project’s own mappings, or, for a project with none, the organization’s default mapping.
Share only the Jira projects whose audience may see this data.
Link test cases from Jira
People who can edit the issue get Link test cases:
- Select Link test cases.
- Search by title or type a test case ID such as
WEB-12. - Pick up to 20 cases; cases that already cover the issue are marked Already linked.
- Select Link (for example Link 3 test cases). A summary says how many were linked, were already linked, or could not be found.
Only test cases of Probara projects mapped to the issue’s Jira project can be linked, and not those of archived projects. To remove one, select Unlink on its row and confirm; the case stays in Probara. Defect links cannot be changed from the panel.
Links made from Jira count exactly like links made in Probara: they appear on the test case’s Jira issues, in the next version of any traceability report, and in Workspace activity as done by the system, with the Jira account.
Troubleshooting
| You see | What to do |
|---|---|
| ”You don’t have permission to see Probara data for this issue.” | Jira does not let you browse this issue’s project. Ask a Jira admin. |
| No Link test cases button, or “You need permission to edit this Jira issue…” | You cannot edit this issue in Jira. Ask for the permission, or link the case from Probara. |
| ”This Jira project is not mapped to a Probara project…” | An owner or admin maps it in a Probara project’s Settings › Jira, or in the organization’s default mapping. |
| A test case you expect “could not be found” | Its Probara project is not mapped to this Jira project, or the project is archived. |
| ”The connection to Probara needs attention.” | A Jira admin opens Jira settings › Apps › Probara; see Troubleshooting the connection. |
| ”Too many requests. Try again in a moment.” | The panel is rate limited per person and per site. Wait, then select Try again. |