JIRA Integration

Connect your Atlassian JIRA instance to deprec8 to create issues for deprecation milestones directly from the deprecation detail page.

Requirements

• PRO plan or higher
• A team organization in deprec8
• Admin role in the organization
• An Atlassian Cloud JIRA instance you have access to

Connecting JIRA

1. Switch to your organization using the organization switcher in the navigation bar
2. Go to Settings → Integrations
3. In the JIRA card, click Connect JIRA
4. You'll be redirected to Atlassian to authorize deprec8
5. Grant the requested permissions and click Accept
6. You'll be redirected back to deprec8 — the JIRA card now shows as connected

If your Atlassian account has access to multiple sites, deprec8 connects to the first available site. To switch sites, disconnect and reconnect.

Configuring Defaults

After connecting, configure default values for new issues:

1. Go to Settings → Integrations
2. In the JIRA card, click Configure
3. Set your defaults:
   • Default Project — the JIRA project where issues are created (required)
   • Default Issue Type — the issue type to use (loads based on selected project)
   • Default Priority — priority level for new issues, or Auto to map from milestone severity
   • Default Labels — freeform text labels to apply to all created issues
4. Click Save Configuration

Issue types are project-scoped in JIRA — changing the selected project will update the available issue types.

Testing the Connection

After configuring a default project and issue type, you can verify everything works:

1. Go to Settings → Integrations
2. In the JIRA card, click Send Test Issue
3. A test issue is created in your default project
4. Check your JIRA instance to confirm the issue appeared

A default project and issue type must be configured before sending a test issue.

Creating Issues from Deprecations

Once JIRA is connected, a Push to JIRA button appears on deprecation milestone detail pages:

1. Navigate to a deprecation milestone
2. Click Push to JIRA
3. An issue is created in JIRA with the deprecation details

The created issue includes:

• Deprecation title and description
• Affected component and category
• Milestone date and status
• A link back to the deprecation in deprec8

Issue descriptions use Atlassian Document Format (ADF) for rich formatting in JIRA.

Priority Mapping

When no default priority is configured, deprec8 maps the deprecation status to a JIRA priority:

If your JIRA instance uses custom priority names, set a specific default priority in the configuration instead of relying on auto-mapping.

Duplicate Prevention

deprec8 tracks which deprecation milestones have already been pushed to JIRA. If a milestone has already been pushed:

• The Push to JIRA button shows the existing JIRA issue key instead
• Clicking it opens the existing issue in JIRA
• This prevents duplicate issues from being created

Roles and Permissions

Disconnecting

To remove the JIRA integration:

1. Go to Settings → Integrations
2. In the JIRA card, click Disconnect
3. Confirm the disconnection

Disconnecting removes the OAuth connection and configuration from deprec8. Any issues already created in JIRA are unaffected.

Troubleshooting

"Push to JIRA" button not visible

• Confirm your organization has JIRA connected (check Settings → Integrations)
• Ensure you're viewing the deprecation in the correct organization context

Issue types dropdown empty

• Verify a default project is selected — issue types are loaded per-project
• Check that the connected Atlassian user has access to the selected project

Test issue fails

• Verify a default project and default issue type are configured
• Check that the connected Atlassian user still has permission to create issues
• Try disconnecting and reconnecting JIRA

Authorization expired

JIRA tokens may expire if permissions are revoked in Atlassian. Disconnect and reconnect the integration to obtain a fresh token.