Jira settings let Mini DBA create or update Jira issues for alert and operations workflows. Use this integration when database alerts should become tracked tickets.
Fields
- Jira Server URL: base URL for the Jira or Atlassian site.
- Project: target Jira project key, such as
OPS. - User Name: Jira user or service account.
- Access Key / Token: Jira API token or access key.
- Issue Type: issue type to create, such as Bug or Task.
- Auto Complete Issue: close or complete related issues automatically where supported.
Configure Jira
- Create or choose a Jira service account.
- Generate an API token with permission to create issues in the target project.
- Open Settings and select Jira.
- Enter the Jira server URL, project, user name, token, and issue type.
- Save.
- Trigger or test an alert workflow and confirm the issue appears in Jira.
Jira Workflow Guidance
Jira integration is useful when database alerts need a durable ticket, ownership, and follow-up history. Use a dedicated service account with permission only for the target project and issue types required by your operations process.
Choose the issue type carefully. Some teams use Bugs for application defects and Tasks for operational follow-up; others use Incidents or Service Requests. Align Mini DBA-created issues with the workflow your team already uses so tickets are triaged rather than ignored.
If Auto Complete Issue is enabled, confirm the behavior with a test alert before using it in production. Automatic closure is useful for transient alerts only when your process accepts that a cleared alert means the ticket can be resolved.
Jira Settings FAQ
Should every alert create a Jira issue?
No. Use Jira for alerts that need tracking, ownership, or remediation work. Noisy alerts should be tuned first.
What if issues are not created?
Check the Jira URL, project key, issue type, token, service account permissions, proxy settings, and Service Log.
Is a service account recommended?
Yes. A service account avoids tying operational automation to one employee's login.