Jira integration
(Updated: )What you can do
The Jira integration gives you access to several Jira features directly from Leebry. Once the integration is set up, you can:
- Search Jira issues using natural language or Jira Query Language (JQL) — live API calls
- Create Jira tickets through a preview-and-confirm workflow
- List accessible Jira projects
- View Jira ticket fields (both required and optional)
Audience
The Jira integration involves both administrators and users. Administrators configure the integration for the organization, while users authorize their own Jira accounts to perform Jira actions.
Admins: Connect Jira at the organization level using a Jira Cloud ID to make Jira features available in Leebry.
Users: Authorize their personal Jira accounts to perform Jira actions in chat.
Prerequisites
Before setting up or using the Jira integration, make sure the following requirements are met.
Admins:
- Access to the integration settings in the Leebry admin dashboard
- Jira Cloud ID
Users:
- Jira has been connected by an administrator
- Your Jira account has been authorized through per-user OAuth before using Jira actions
Connect Jira (admins)
As an admin, once you have the Jira Cloud ID, follow these steps to connect Jira to Leebry.
In the Leebry admin dashboard, go to Integration.
In the Jira tile, click Connect.
Enter the Cloud ID, then click Continue.
After the connection is established, Jira appears in the list of connected integrations.
Use Jira in chat
List accessible projects
Example prompts:
- Show accessible Jira projects.
- In what projects can I create tickets?
View ticket fields
Example prompts:
- Show required and optional fields for tickets in [project].
- Show the ticket schema for Bug in [project].
Search Jira issues
Search using either natural language or JQL.
Example prompts:
- Find issues in the project about onboarding.
- List tickets in the project that have status In Progress.
- Search Jira using JQL:
project = PROJECT AND status != Done ORDER BY updated DESC.
Create a Jira ticket
Ask Leebry to create a ticket, for example:
- Create a Jira ticket
- Log an issue
Leebry displays a preview of the ticket.
Review the ticket details, then confirm creation.
Leebry confirms that the ticket has been created and provides a link to the new issue.
Troubleshooting
Admins
| Issue | Likely cause | Solution |
|---|---|---|
| Can't connect Jira; the form won't submit | Cloud ID is missing or invalid | Enter a valid Cloud ID and verify that it doesn't contain leading or trailing spaces |
Users
| Issue | Likely cause | Solution |
|---|---|---|
| Authorization loop or repeated prompts to authorize Jira | Per-user OAuth authorization is missing, expired, or revoked | Click Authorize Jira again and complete the Atlassian sign-in process |
| Callback error: invalid/expired state | OAuth state validation failed because of a stale browser tab or blocked pop-up | Close the pop-up, restart authorization from Leebry, and try again in a new browser session |
| Search returns no results even though the issue exists | Query is too narrow or doesn't match the issue | Search by issue key, include the project key, broaden the search terms, or use JQL |
| Ticket creation fails | Some fields require Atlassian Document Format or unsupported custom fields | Retry using only the required fields, such as Summary and Description, remove unsupported custom fields, and verify the required ticket fields first |
Permissions and security
Your Jira permissions determine which projects, issues, and actions are available through Leebry. If you can't access a resource in Jira, Leebry can't access it either.
Leebry uses your per-user authorization token to perform live API requests. It doesn't rely on a Jira content index.
FAQ
Do you need an administrator to set up Jira before using it?
Yes. An administrator must first connect Jira for the organization. After that, you can authorize your Jira account and use Jira actions.
Does Leebry index Jira content?
Leebry uses live, per-user API requests for Jira search and ticket creation. Jira content isn't indexed to power general AI responses.
Why don't you see Jira prompts?
Either Jira hasn't been connected at the organization level, or the page needs to be refreshed after an administrator connects it. Once Jira is connected and the page is refreshed, the Authorize Jira prompt appears the first time you use a Jira action.
