Jira integration in the free tier.

[dariofervenza]

Hello,

I have been inspecting the code and the documentation but I could not make the Jira integration work.

So far I have found a related function in pr_agent/tools/ticket_pr_compliance_check.py with signature def find_jira_tickets(text):

However, this is an unused function.

Besides, I have tried to locate the config key "jira_api_token" but it is only present here:
skip_keys = ['ai_disclaimer', 'ai_disclaimer_title', 'ANALYTICS_FOLDER', 'secret_provider', "skip_keys", "app_id", "redirect", 'trial_prefix_message', 'no_eligible_message', 'identity_provider', 'ALLOWED_REPOS', 'APP_NAME', 'PERSONAL_ACCESS_TOKEN', 'shared_secret', 'key', 'AWS_ACCESS_KEY_ID', 'AWS_SECRET_ACCESS_KEY', 'user_token', 'private_key', 'private_key_id', 'client_id', 'client_secret', 'token', 'bearer_token', 'jira_api_token','webhook_secret'] partial_skip_keys = ['key', 'secret', 'token', 'private']

I would like to confirm if Jira integration is only available in the pro version.

In my opinion, I believe that it is confusing because in the free version there is a .md document that explains Jira integration (docs/docs/core-abilities/fetching_ticket_context.md).

Thanks.

Best wishes.

[zulufoxtrot]

I just landed here after unsuccessfully trying to set up the Jira integration.
If it is not supported in the open source project, it should probably be removed from the docs.

[IsmaelMartinez]

Your reading of the code is right, and thank you for the precise trace. In this repository find_jira_tickets is dead code: extract_tickets fetches Asana tasks, GitHub issues and Azure DevOps work items, and never reaches a Jira branch. There is no [jira] configuration section either, so jira_api_token survives only in the settings redaction list. The documentation page is genuinely misleading on this point, and the follow-up comment is right that it should carry a caveat until the code catches up.

PR #2420 is open and actively being worked, adding Jira Cloud ticket-context support in a provider-agnostic way with a [jira] section and tests, so the gap is being closed rather than declared out of scope. Please follow that PR for progress, and do weigh in there if you have a view on the configuration key naming or on whether a broader issue-provider section is preferable. Closing this thread in favour of it.