Support OAuth for Jira integration instead of API token authentication

(Created using Elle!)
Summary

Enable OAuth-based authentication for the Jira integration so teams can connect Aha! to Jira without relying on long-lived API tokens or personal access tokens.

Problem

Token-based authentication creates administrative overhead, makes credential rotation harder, and can raise security concerns for enterprises that prefer centralized authorization and revocable delegated access.

Value

• Improves security posture through delegated authorization

• Reduces manual token management and rotation burden

• Aligns better with enterprise IT and compliance expectations

• Makes integration setup easier for organizations that standardize on OAuth

Proposal

Add support for OAuth 2.0 authentication for the Jira integration as an alternative to API token-based setup.

Requirements

• Allow admins to authenticate the Jira integration using OAuth 2.0

• Support secure token refresh and revocation handling

• Provide clear setup guidance for Jira admins

• Preserve existing token-based authentication as an option where OAuth is unavailable

• Surface meaningful error messages for authorization and permission issues

Success criteria

• Admins can connect Jira via OAuth without generating manual API tokens

• Connected integrations remain stable through token refresh flows

• Support requests related to Jira token setup decrease

Notes

This idea is specifically focused on Jira integration authentication and should be evaluated against security, admin experience, and compatibility constraints across supported Jira deployment types.