Title here
Summary here
Jira Configuration
Configuration Fields
Enable Jira Integration: Toggle to enable or disable the entire integration. When disabled, no Jira issues will be created, but the configuration is preserved.
Project Key: The Jira project key where issues will be created, the short uppercase identifier shown at the start of every issue number (e.g., SEC in SEC-123). To find it: open your Jira project and look at any issue number, or go to Project Settings in Jira.
Issue Type: The type of Jira issue to create. After entering a valid Project Key and clicking Test Connection, this field becomes a searchable dropdown populated from the project’s available issue types (Task, Bug, Story, Security, etc.).
Severity → Jira Priority ID Mapping: Maps Aegis severity levels to Jira priority IDs.
| Aegis Severity | Default Jira Priority ID |
|---|---|
| Critical | 1 (Highest) |
| High | 2 (High) |
| Medium | 3 (Medium) |
| Low | 4 (Low) |
Enter the numeric ID, not the label. Jira priority IDs can be found via your Jira project’s configuration or the Jira REST API.
Auto-create on critical case / SLA breach: When enabled, Jira issues are automatically created when a new case with Critical severity is created, or when a case’s SLA deadline is breached. Manual Jira issue creation is always available regardless of this setting.
Testing the Connection
- Enter the Project Key.
- Click Test Connection.
- If successful: a green banner shows “Connected, project: [Project Name]”. The Issue Type dropdown is automatically populated.
- If failed: a red banner shows the error.
Common errors:
- “Project not found”: The project key is incorrect or Jira is not connected via Atlassian Administration.
- “Jira is not configured”: You have not connected Jira via Atlassian Administration (see the first-time setup steps on the Integrations tab overview page).
The test connection result auto-dismisses after 3.5 seconds.