Introduction
Connect Jira so the AI assistant and agents can search selected projects at the moment a user asks a question.
This is a live connector. Nothing from Jira is copied, indexed, or stored in Docebo. When a user asks a question, Docebo searches the projects you've made available at that moment, using the user's own Jira account.
How permissions work for Jira: each colleague connects their own Jira account the first time it's needed. Every search then runs as that user, so Jira applies its own access rules and they only see what they could open in Jira themselves. The account you use during setup is only used to set up the connection.
1. Prerequisites in the source system
Required setup
This connector only supports Jira Cloud.
Required role
You need an Atlassian organization admin to create the OAuth app and authorize the connector.
Required settings
If your organization uses an app allowlist, add the new OAuth app to it before authorizing.
2. Preparation in the source system
Jira uses the same kind of app as the Confluence connector: an OAuth 2.0 (3LO) app in the Atlassian Developer Console. If you already created an app for Confluence, you can reuse it. Open it, then continue with Add permissions. Any Confluence scopes you've already granted stay in place.
Create the app
Skip this step if you're reusing your Confluence app.
- Go to the Atlassian Developer Console and create a new OAuth 2.0 integration.
- Name it (for example, "Docebo Knowledge Connector") and keep Access type set to Account-level (the default).
Create a new OAuth 2.0 (3LO) integration, with the access type choice.
Add permissions
- In the app, open Permissions. Under Jira API, select Add if it isn't listed yet, then Configure.
- Stay on the Classic scopes tab, select Edit Scopes, and tick View Jira issue data and View user profiles.
- Open User identity API and make sure View active user profile is ticked. It already is if the app is used for Confluence.
| API | Scope name | Code |
|---|---|---|
| Jira API (classic scopes) | View Jira issue data | read:jira-work |
| Jira API (classic scopes) | View user profiles | read:jira-user |
| User identity API | View active user profile | read:me |
Add the callback URL
Under Authorization, make sure the callback URL below is listed in Callback URLs. If it isn't, add it and select Save changes. It always follows this pattern: https://[YOUR-DOCEBO-PLATFORM-URL]/knowledge/v1/integrations/connections/callback, for example https://demo.docebosaas.com/knowledge/v1/integrations/connections/callback.
It's the same URL the Confluence connector uses, so an app shared with Confluence already has it.
Authorization tab with the Callback URL field and the Authorization URL generator.
Define distribution
Skip this step if you're reusing an app that's already set up for Confluence.
- Open Distribution and set Distribution status to Sharing.
- Fill in the required fields with your own information: vendor name, privacy policy URL, terms of service URL, customer support contact, and the personal data declaration.
- Select Save changes.
Edit distribution controls, with Sharing selected and vendor details filled in.
Retrieve the Client ID and Client secret
Open Settings and copy the Client ID and Secret from Authentication details. You'll paste them into Docebo.
3. Required actions in Docebo
| Information to enter | Where to find it |
|---|---|
| Client ID | Atlassian Developer Console → app → Settings → Authentication details |
| Client secret | Atlassian Developer Console → app → Settings → Authentication details |
Authorizing the connector
- Go to Add-ons and integrations → Knowledge Connectors → Create → Jira. This menu is only visible to Superadmins.
On the Authorize tab, enter the Client ID and Client secret from your Atlassian app, then select Authenticate.
In the Atlassian pop-up, review the requested access and select Accept. The connector then shows as connected. No sync starts, because nothing is copied.
Choose which projects can be searched, then save your selection.