Add GHAS code scanning severity to Jira issue label

[maritiren]

This feature adds the severity label to the Jira issue.

The severity label is needed for project managers/whoever prioritizes tasks to prioritize the findings into sprints.

We discussed whether to write the labels with or without the severity- prefix. We figured we'd keep a clear language. See the example:

[Copilot]

🟡 Changes recommended

Label synchronization can delete unrelated user-managed labels beginning with severity-.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

Adds GitHub code-scanning severity labels to Jira issues and keeps them synchronized.

Changes:

• Derives severity from code-scanning rules.
• Adds or updates severity-* Jira labels.
• Documents label synchronization behavior.

File summaries

File	Description
sync.py	Passes alert severity during synchronization.
jiralib.py	Creates and updates severity labels.
ghlib.py	Extracts alert severity.
README.md	Documents severity labels.

Review details

• Files reviewed: 4/4 changed files
• Comments generated: 1
• Review effort level: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

🔵 Needs a closer look

Configured labels can collide with managed severity labels, causing issues to retain multiple contradictory severities.

Review details

Suppressed comments (2)

Previously missed (1) — in code that hasn't changed since the last review.

jiralib.py:197

• Configured Jira labels are concatenated with the managed severity without excluding the reserved severity values. For example, jira_labels: severity-high creates a low-severity alert with both severity-high and severity-low, so the issue no longer has the single current severity described in the README. Reject/reserve these values in jira_labels, or filter managed severity labels from self.labels before appending the alert's current severity.

This issue also appears on line 316 of the same file.

jiralib.py:316

• This loop re-adds any managed severity value present in jira_labels immediately after line 315 removes stale severity labels. Thus an existing low-severity issue remains labeled severity-high and severity-low when severity-high is configured, instead of replacing the stale value. Exclude or reject managed severity labels from configured labels before merging the current severity.

        for label in self.labels + severity_labels(severity):

• Files reviewed: 4/4 changed files
• Comments generated: 0 new
• Review effort level: Balanced