Atlassian Jira
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.
How does this capability work
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.
Jira issues that can be implemented with Tabnine
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.
Supported matrix
Jira Cloud | Jira Data Center | |
---|---|---|
Tabnine Pro | Yes | No |
Tabnine Enterprise (SaaS) | Yes | Coming soon |
Tabnine Enterprise (private installation) | Coming soon | Coming soon |
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.
FAQ
What context is utilized by Tabnine for the Jira connection?
For 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.
Who has access to this capability?
This capability is available to Tabnine users on the Pro and Enterprise tiers.
What control do Tabnine administrators have?
This feature is disabled by default and Tabnine administrators (at enterprise SaaS) 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.
Enabling the Jira Connection for Enterprise (SaaS)
Disabled by default; the team admin can enable it for the whole team.
To enable/switch it off, the Enterprise team admin should go to the Personalization screen on the Tabnine app and enable Enable connection to Jira.
Note: It can take up to one hour to populate the end users’ IDEs.
Last updated