[Feature][Jira] Support Atlassian OAuth 2.0 credentials for Jira service account

[squatboy]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Use case

As a platform/DevOps engineer, I want Apache DevLake's Jira plugin to support OAuth 2.0-based service account (non-human account) authentication, so that our organization can integrate Jira without relying on user API tokens or personal credentials.
In our environment, Jira integrations are expected to use a service account / non-human account with OAuth 2.0-based authentication.

Description

DevLake's Jira connector appears to support token-based or username/password-style authentication flows, but it does not appear to provide a native option for OAuth 2.0-based service account authentication.

We would like DevLake to support this authentication model for the Jira connector.

From a user perspective, the feature would ideally allow:

• configuring Jira connections with OAuth 2.0-based service account credentials
• using a non-human/service account for Jira data collection
• handling the necessary access token flow in the Jira connector itself instead of requiring an external authentication proxy or workaround

This would help organizations that:

• do not want integrations tied to individual user accounts
• require centrally managed service-account credentials
• use OAuth 2.0-based authentication for internal system-to-system integrations

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct