Jira Integration
Create Jira tickets directly from your drift widgets to streamline your infrastructure remediation workflow.
Overview
The Jira integration allows you to:
- Create tickets from drift widgets - One-click ticket creation from your dashboard
- Auto-populate ticket details - Drift information, filters, and links are automatically included
- Link to Drift Explorer - Each ticket includes a direct link to view the drifts in detail
Prerequisites
Before setting up the Jira integration, ensure you have:
- A Jira Cloud account (Jira Server is not supported)
- Admin or project admin permissions in your Jira workspace
- At least one Jira project where you want to create tickets
Jira Cloud Only
This integration uses Atlassian's OAuth 2.0 (3LO) authentication, which is only available for Jira Cloud. Self-hosted Jira Server/Data Center instances are not currently supported.
Setting Up the Integration
Step 1: Navigate to Settings
- Log in to Controlinfra
- Go to Settings from the sidebar
- Click on the Integrations tab
- Select the Developer sub-tab
- Find the Jira Integration card and expand it
Step 2: Connect Your Jira Account
- Click the Connect to Jira button
- You'll be redirected to Atlassian's authorization page
- Select the Jira site you want to connect (if you have multiple)
- Review the permissions and click Accept
- You'll be redirected back to Controlinfra
Step 3: Verify the Connection
Once connected, you'll see:
- Your Jira account name
- The connected site URL
- Last verification timestamp
You can click Refresh Projects to load your available Jira projects.
Permissions Required
When you authorize Controlinfra, the following permissions are requested:
| Permission | Purpose |
|---|---|
read:jira-work | Read projects, issue types, and priorities |
write:jira-work | Create new issues in your projects |
read:jira-user | Display your account information |
offline_access | Maintain connection without re-authorizing |
Minimal Access
Controlinfra only requests the minimum permissions needed to create tickets. We cannot modify existing issues, access sensitive data, or perform administrative actions.
Creating Tickets from Drift Widgets
From the Dashboard
- Navigate to your Dashboard
- Find a drift widget showing detected drifts
- Click the Jira icon on the widget card
- Select a Project and Issue Type
- Customize the Summary and Description if needed
- Click Create Ticket
Ticket Contents
Each ticket automatically includes:
- Summary:
[Drift Alert] {Widget Name} - {Count} drifts - Description:
- Drift count and widget details
- Applied filters (severity, provider, action, etc.)
- Date range
- Direct link to Drift Explorer with pre-applied filters
- Labels:
drift,controlinfra(customizable)
Example Ticket Description
## Drift Alert: Production AWS Drifts
**15 drift(s) detected**
Critical infrastructure changes detected in production environment.
### Filters Applied
- **Severity:** critical, high
- **Provider:** aws
- **Action:** update, delete
**Date Range:** Last 30 days
### View Details
[Open in Drift Explorer](https://app.controlinfra.com/drift-explorer?severity=critical,high&provider=aws)
---
*Created by Controlinfra*Managing the Integration
Testing the Connection
Click Test Connection to verify your Jira connection is still valid. This is useful if you've changed your Jira permissions or if tickets are failing to create.
Refreshing Projects
Click Refresh Projects to reload the list of available Jira projects. Do this after:
- Creating a new Jira project
- Changing your Jira permissions
- Being added to new projects
Disconnecting Jira
- Click the Disconnect button
- Confirm the disconnection in the modal
- Your OAuth tokens will be removed from Controlinfra
After Disconnecting
You'll need to re-authorize to use the Jira integration again. Any saved preferences (default project, labels) will be cleared.
Troubleshooting
"Token refresh failed" Error
Your Jira access has expired and couldn't be renewed. This can happen if:
- You revoked access in your Atlassian account settings
- Your Jira account was deactivated
- There was a prolonged service interruption
Solution: Disconnect and reconnect the integration.
"No Jira sites found" Error
You authorized the connection but no Jira sites were found. This can happen if:
- You don't have access to any Jira Cloud sites
- Your Jira subscription has expired
Solution: Ensure you have an active Jira Cloud subscription and try again.
Projects Not Appearing
If your Jira projects aren't showing up:
- Click Refresh Projects
- Verify you have access to the project in Jira
- Check that the project isn't archived
Ticket Creation Fails
If tickets fail to create:
- Verify the selected project allows the chosen issue type
- Check that required fields in your Jira project are satisfied
- Ensure your Jira account still has create permissions
Security & Privacy
Data Storage
- OAuth tokens are encrypted at rest using AES-256
- Tokens are automatically refreshed before expiration
- No Jira data is stored beyond connection metadata
Token Refresh
Access tokens expire after 1 hour. Controlinfra automatically refreshes tokens using the secure refresh token flow, so you don't need to re-authorize.
Revoking Access
You can revoke Controlinfra's access at any time:
- Go to Atlassian Account Settings
- Find "Controlinfra" in the connected apps
- Click Revoke access
Best Practices
- Use dedicated labels - Add custom labels like your team name to organize drift tickets
- Set a default project - Configure your most-used project to speed up ticket creation
- Link to Drift Explorer - The auto-generated links help your team quickly investigate drifts
- Integrate with workflows - Set up Jira automation to assign tickets or trigger notifications
FAQ
Can I use Jira Server/Data Center?
Not currently. The integration requires Atlassian's OAuth 2.0 which is only available for Jira Cloud.
Can I connect multiple Jira sites?
Currently, only one Jira site can be connected per Controlinfra account. If you have multiple sites, you'll need to choose which one to connect.
Are there any limits on ticket creation?
Controlinfra doesn't impose limits, but your Jira plan may have API rate limits. Standard usage (creating a few tickets per day) won't hit these limits.
Can I customize the ticket template?
The ticket template is currently fixed, but includes all relevant drift information. Custom templates are planned for a future release.