Atlassian Jira
Tabnine AI code assistant: Atlassian Jira integration
Last updated
Tabnine AI code assistant: Atlassian Jira integration
Last updated
AI agents to implement and validate Jira issues
You can now connect Tabnine to Atlassian Jira and take advantage of two new AI agents:
Jira Implementation Agent: A user can ask Tabnine to implement a Jira issue that’s been assigned to them. Tabnine generates code for the requirements outlined in the Jira issue.
Jira Validation Agent: A user can ask Tabnine to review their implementation. When a user has written code for a Jira issue, Tabnine can check if their code accurately captures the requirements outlined in the Jira issue, offering suggestions if it doesn’t.
As the first AI code assistant to offer an integration with Atlassian Jira, Tabnine enables you to accomplish macro-level tasks with a single click. You can directly ask Tabnine to implement a story, bug, task, or subtask — there’s no need to decipher requirements in a Jira issue, break it down into tasks, and feed specific prompts into an AI chat window.
To use the new agents, you must first connect Tabnine to Jira. After the connection is established, all the Jira issues assigned to you as an individual user are available in Tabnine.
You can then select a specific issue and ask Tabnine to implement it. Once you hit Enter, Tabnine generates code to meet the requirements of the Jira issue. From there, you can review and revise the code as needed before inserting it.
In addition to code generation, you can validate code with this functionality. Simply select the code you’ve written and ask AI chat if it aligns with the requirements outlined in the Jira issue.
There’s no technical limitation on the type of Jira issues that Tabnine can implement. To ensure the most relevant and accurate output, we recommend using Tabnine for issues like stories, bugs, tasks, and subtasks (i.e., issues that represent defined and specific units of work). This keeps the communication with AI concise and makes it easier to check the responses. During implementation, you can then ask Tabnine to refine the output (as needed), review the reference files used to generate the output, and work through the follow-up questions suggested by Tabnine.
To establish a connection between Tabnine and Jira, you need access to an internet connection and a browser. It’s not supported in VDI environments.
We currently support parent issues in Jira. Issues that are children of a parent issue need to be implemented individually.
Inline actions currently don’t support this capability. *Jira Data Center version 8.20 and higher. **Jira Data Center: Tabnine version 5.11.0 or higher; Jira Cloud: Tabnine version 5.12.0
Enterprise SaaS This feature is not enabled by default and requires explicit activation. For assistance, please contact your Tabnine Account Manager or email support@tabnine.com.
Enterprise Self-Hosted
Starting from version 5.12.0, the Jira connection feature for Enterprise customers in private installations is license-dependent. If this feature is not enabled for your account, contact your Tabnine Account Manager or email support@tabnine.com.abnine Account Manager or email support@tabnine.com.
Notes
Regardless of the admin setup, the end user flow and experience are the same for both integration options.
The integration may take up to one hour to fully populate and become visible in users' IDEs.
Enabling the Jira Cloud connection for Tabnine Enterprise SaaS is straightforward. Team administrators can toggle the feature directly in the Tabnine Admin Console.
Steps:
Log in to the Tabnine Admin Console.
Toggle the Enable connection to Jira switch.
This setup is available for Tabnine Enterprise customers with private installations (version 5.12.0 or higher).
Integrating Tabnine private installation with Jira Cloud requires additional configuration, as it involves creating a dedicated OAuth 2.0 App in Atlassian.
Go to the Atlassian Developer Console.
From the Resources menu, select Developer Console.
Click Create App, then select OAuth 2.0 (3LO Integration).
Enter a name for your application and accept Atlassian’s developer terms.
You'll be redirected to the My Apps overview page.
Navigate to Authorization and provide a callback URL.
Add the following required permissions to your app:
read:me
read:account
read:jira-work
read:jira-user
Go to Distribution and complete the form to share your app.
Copy your OAuth 2.0 application credentials from Atlassian:
Navigate to Overview > App Details.
Copy the Client ID and Client Secret.
Log in to the Tabnine Admin Console:
Navigate to Settings > Workspace.
Locate the Enable Jira connection section.
Enable the Jira Cloud option.
Enter the following details:
Client ID
Client Secret
Jira Data Center URL (if applicable)
Click Save.
Note
The Tabnine integration with Jira Data Center is available to Tabnine Enterprise customers with private installation (version 5.11.0 or higher).
Supports Jira Data Center version 8.20 and higher.
Integrating Tabnine with Jira Data Center requires additional configuration beyond simply enabling the toggle. Follow these steps:
Navigate to Resources > Developer Console.
Click on Create App and then click on OAuth 2.0 (3LO Integration).
Enter a name for your application and accept Atlassian’s developer terms.
Navigate to Administration > Applications > Application links.
Select Create link.
Choose External application, and set the direction to Incoming.
In the following screen, complete the fields as follows:
Name: Enter a unique name for the application link.
Redirect URL: Enter the callback URL from the Tabnine admin application. This URL will redirect users after authorization and should be your Tabnine server URL followed by /app/auth/jira. For example: https://private-tabnine.company.com/app/auth/jira.
Permission: Set the permission to Read (defines which permissions the application has on your instance).
After creating the application link in your Data Center instance, input the application credentials in the Tabnine Admin Console:
Ensure you have the Client ID and Client Secret from your Jira Data Center application:
Go to Administration > Application links in your Jira Data Center.
Locate the relevant application link and select More actions > View credentials.
Copy the Client ID and Client Secret.
In the Tabnine Admin Console:
Navigate to Settings > Workspace.
Find the Enable Jira connection section and toggle it on.
Click Edit.
Enter the Client ID, Client Secret, and your Jira Data Center URL.
Click Save.
For the Jira connection, Tabnine leverages the text in the Jira issue’s title and description as context for implementing the issue and for reviewing the implementation. We currently don't use the following as context:
Images that are included in the Jira issue
Comments added to the issue
History
Links in the issue
Related issues
Design specs like Figma
In addition to using the information in Jira issues as context, Tabnine continues to use locally available code and information in your IDE and (for Enterprise users) your organization’s global codebases to generate responses tailored to you and your organization.
This capability is available to Tabnine users on the Pro and Enterprise tiers.
This feature is disabled by default for Enterprise customers, but enabled by default for all other Tabnine chat users.
Tabnine administrators (at enterprise SaaS or private installation) can enable it. The administrators can enable the feature themselves without contacting our Support team. Once enabled, this feature is available to all Tabnine users at the company. The end users of Tabnine can then connect Tabnine to Jira themselves. Please note, this is a client-side integration.
Tabnine leverages Jira user permissions during connection ensuring that only issues assigned to a developer are accessible to them.
This feature supports the same and as the AI chat.
The Jira connection is disabled by default for Tabnine Enterprise customers. Team administrators can enable or disable this feature for the entire team through the Tabnine Admin UI. Tabnine supports integration with either or .
Navigate to the screen.
Go to .
Tabnine Pro
Yes
No
Tabnine Enterprise (SaaS)
Yes
Yes
Tabnine Enterprise (private installation)
Yes**
Yes**
