Jira

With the Jira Cloud integration, Proton links automations to Jira requirements and opens bugs from failed runs, with the report, the log and the link. Traceability then shows the requirements and the open bugs of each dataset.

Set up

In Settings > Integrations, register an integration of type Jira with:

• Base URL: the Jira Cloud address, such as https://yourcompany.atlassian.net;
• Email and API Token of a Jira account (preferably a technical user) with access to the projects.

See Integrations. Without the integration, the Jira features don't show up in the portal.

Requirements

In Proton, a requirement is a Jira issue, such as a story or an epic. A requirement is linked to a whole automation or to a dataset, and the dataset inherits the automation's requirements.

To link one:

1. In the automation's dataset list (or when editing the dataset), use Requirements, which shows how many are linked.
2. In the Requirements drawer, search Jira by key (PROJ-123) or by text in the summary.
3. Pick the issue. It shows up with its Jira status, grouped under Of this dataset and From the automation.

Unlink requirement removes the link in Proton; nothing changes in Jira. Requirements that come from Xray or Zephyr Tests (the Test coverage) can't be unlinked here.

The summary and status of the issues are read again from Jira from time to time (every 15 minutes at most). When Jira is down, Proton shows the last reading.

Bug from a run

In the run details and in the group's failure drawer, Jira bug offers:

• Open bug, already filled in with the error, the log and the link to the run. It's available once the run finishes.
• Link existing bug, for an issue that is already open.

The Open bug in Jira window has the Project, the Type (the last one used comes selected, or the one with "bug" in its name), the Summary (up to 250 characters) and the Description, plus two options that are on by default:

• Attach the run report (PDF);
• Link to the dataset requirements, which creates in Jira a link between the bug and each requirement.

The linked bug shows up as a badge that opens the issue. The X unlinks the bug from the run in Proton; in Jira, the bug stays.

The AI failure diagnosis also offers to open the bug.

In traceability

With Jira, Traceability gets the Requirements indicator and the Requirements column (with the status of each issue) and the Open bugs column (bugs opened from the dataset's runs that haven't been resolved in Jira yet).

Permissions

Action	Profile permission
View requirements	Jira requirements: read
Link and unlink requirements	Jira requirements: update
View bugs	Jira bugs: read
Open and link bugs	Jira bugs: create