Jira

The Jira integration turns AppArch findings into Jira issues and reads the mapped Jira projects for issue flow analytics.

Connecting

Integrations → Jira.
Enter the Atlassian site URL (e.g. https://your-team.atlassian.net), the account e-mail and an API token.
AppArch verifies the token against Jira (/rest/api/3/myself) before storing it encrypted.

Each workspace has one Jira connection. Managing it requires the workspace’s Integrations permission.

Mapping projects

A mapping links an AppArch project to a Jira project. For each mapping you choose:

the default issue type (Bug unless you pick another),
optionally a board, whether to add to the board’s running sprint, and the initial status,
the auto-create rules: open an issue when an ArchPilot review fails, and/or for critical ArchScan findings.

Creating issues

By hand: tick findings on an ArchScan run or an ArchPilot merge request in the panel and create issues for them.
Automatically: the auto-create rules run in the background. A first sweep looks back 24 hours from when the rule was switched on, and at most 50 issues are opened per mapping per sweep; the rest follow on later sweeps.

An issue’s summary is [AppArch] <rule code>: <message> (up to 200 characters); its description has the module, repository, rule and severity, file and line, branch, where it was seen, the message and the suggested fix when there is one.

The finding then shows a badge with the issue key, linking to the issue. Links are matched by the finding’s fingerprint, so a finding that a later run reports again keeps its issue instead of getting a new one.

AppArch does not show the issue’s status on the finding, and it does not add Jira keys to the comments ArchPilot posts on pull requests.

Issue flow

Once a workspace maps at least one Jira project, AppArch also reads the issues of its mapped projects (the first run looks back 180 days) for the issue flow report - see Engineering analytics.