Jira integration
(Updated: )What the Jira integration enables
Search Jira issues in your projects using natural language or JQL (live API calls)
Create Jira tickets from chat with a preview > confirm flow
List accessible projects
Show required/optional fields (schema) for creating tickets
Audience
Admins: Connect Jira at the organization level (Cloud ID) to make Jira skills available in Leebry.
End users: Authorize their personal Jira account to run Jira actions in chat.
Prerequisites
Admins
- Leebry Web admin access to Integrations settings
- Jira Cloud ID
End users
Organization has Jira integration connected by an admin.
You must authorize your own Jira account (per-user OAuth) before using Jira actions.
Admin guide
Connect Jira (Cloud ID)
What you need: Jira Cloud ID.
Open Leebry Web > Integration.
Find Jira and select Connect.
Enter the Cloud ID and select Continue.
On success, Jira appears in the connected list with Reconnect and Delete actions.
End-user guide
Authorize Jira (per-user)
In Leebry chat, attempt a Jira action (search, create ticket, view projects/schema).
When prompted, select Authorize Jira.
Complete Atlassian sign-in/consent in the popup/new tab, then return to chat.
You must authorize even if your admin connected Jira. Live actions use your own Jira permissions (Digital User Passport).
Use Jira in chat
List accessible projects
Example prompts:
- Show accessible Jira projects
- In what projects can I create tickets?
View ticket schema (required/optional fields)
Example prompts:
Show required and optional fields in ticket in
<project>Show ticket schema in
<project>for Bug
Search Jira issues (natural language or JQL)
Example prompts:
Find issues in PANDO about onboarding
List tickets in PANDO that are In Progress
Search Jira using JQL:
project = PANDO AND status != Done ORDER BY updated DESC
Create a Jira ticket (preview > confirm)
Ask Leebry to create a ticket (for example, "Create a Jira ticket…", "Log a bug…").
Leebry returns a ticket preview card.
Review fields, then confirm creation.
Leebry replies with a confirmation and link to the created issue.
Troubleshooting
Admin
| Issue | Likely cause | Fix |
|---|---|---|
| Can't connect Jira; form won't submit | Cloud ID missing or invalid | Enter a valid Cloud ID; verify no whitespace-only values |
End users
| Issue | Likely cause | Fix |
|---|---|---|
| Authorization loop or repeated prompts to Authorize Jira | Per-user OAuth not stored or revoked/expired | Click Authorize Jira again and complete Atlassian sign-in |
| Callback error: invalid/expired state | OAuth state validation failed (stale tab or blocked popup) | Close popup, restart authorization from Leebry; try a fresh browser session |
| Search returns 0 results though the issue exists | Query match limitations or too-narrow phrasing | Search by issue key; add project key; broaden keywords; try JQL |
| Ticket creation fails | Some fields require Atlassian Document Format; unsupported custom fields | Retry with minimal Summary/Description; remove problematic custom fields; confirm required schema first |
Security and permissions
Your Jira permissions control what you can search and create. If you can't access a project or issue in Jira, Leebry can't access it either.
Leebry uses your per-user authorization token to make live API calls; it doesn't rely on a Jira content index.
FAQ
Do I need admin setup before I can use Jira?
Yes. An admin must first connect Jira for the organization. After that, you can authorize your personal Jira account and use Jira actions.
Is there Jira indexing for RAG?
No. At present, Leebry uses live, per-user API calls for Jira search and ticket creation. There's no Jira content indexing powering general answers.
Why don't I see Jira prompts?
Either Jira isn't connected at the org level, or you need to refresh the page after the admin connected it. If connected and refreshed, you'll see an Authorize Jira prompt when you first use a Jira action.
