Jira integration
Bring Jira issue requirements into every pull request and get validation results back automatically.
Bito integrates with Jira to automatically validate pull request code changes against linked Jira ticket requirements, helping ensure your implementations align with the specified requirements in those tickets.
How it works
When you create a pull request, Bito automatically:
Detects Jira ticket references in your pull request description, title, or branch name
Crawls the linked Jira tickets to extract requirements from issue descriptions and related Stories/Epics
Analyzes your code changes against these requirements
Provides structured validation results directly in your pull request comments
Setting up Jira integration
Connect Bito to Jira
Navigate to the Manage integrations page in your Bito dashboard
In the Available integrations section, you will see Jira. Click Connect to proceed.
Click Authorize with your Jira account. You will be redirected to the official Jira website, where you need to grant Bito access to your Atlassian account.
Click Accept to continue. If the integration is successful, you will be redirected back to Bito.
Agent-specific settings
After completing the initial setup, you can control Jira integration on a per-agent basis:
Go to the Repositories page in your Bito dashboard.
Find the Agent instance you want to connect with Jira and open its settings.
Within the Agent settings screen, click on the Integrations tab.
Locate the Functional validation option and enable this setting to activate automatic pull request validation against Jira tickets.
Linking Jira tickets to pull requests
Bito offers multiple ways to link your Jira tickets with pull requests. You can use any of these methods:
Method 1: Branch name
Name your source branch using the Jira issue key:
feature/QP-123-implement-user-authentication
bugfix/QP-456-fix-login-errorMethod 2: Pull request description
Include the Jira ticket reference in your PR description:
This PR implements user authentication as specified in QP-123.
Related tickets: QP-123, QP-124OR
This PR implements shopping cart functionality as specified in:
https://your-company.atlassian.net/browse/QP-3
https://your-company.atlassian.net/browse/QP-7Method 3: Pull request title
Include the Jira issue key in your PR title:
QP-123: Implement user authentication feature
[QP-456] Fix login validation errorUnderstanding the validation results
When Bito completes its analysis, it adds a "Functional Validation by Bito" table to your pull request comments. This table contains four columns:
Source
Displays the Jira issue key (e.g., "QP-11", "QP-123") that references the specific Jira ticket being validated.
Requirement / Code Area
Shows a brief description of the requirement or task that needs to be completed, summarizing what needs to be done according to the Jira ticket.
Status
Indicates the completion status of each requirement:
Met: The requirement has been fully implemented in the pull request
Missed: The requirement has not been addressed in the pull request
Partial: The requirement has been partially implemented but still needs additional work
Notes
Provides detailed information about the validation status:
For "Met" items: Explains what has been successfully implemented
For "Missed" items: Describes what is missing and needs to be addressed
For "Partial" items: Details what has been completed and what still remains to be done
Example validation output
Here's what a typical validation table looks like:
Benefits
Automated quality assurance: Ensure code changes meet specified requirements
Improved collaboration: Bridge the gap between project management and development
Reduced manual reviews: Bito AI automatically catches missing implementations during code review
Better traceability: Maintain clear links between requirements and code changes
By leveraging Bito's Jira integration, your development team can maintain higher code quality while ensuring that all requirements are properly addressed in every pull request.
Best practices
For developers
Always reference Jira tickets in your pull requests using one of the supported methods
Review the validation table and address any "Missed" or "Partial" items before merging
For teams
Ensure Jira tickets contain clear, detailed requirements
Use consistent naming conventions for branches and pull request titles
Enable functional validation for all relevant agents
Troubleshooting
Validation table not appearing:
Check that your Jira integration is properly configured in the Manage integrations page
Verify that Functional validation is enabled in your agent settings
Ensure your pull request contains valid Jira issue key references
Incorrect validation results:
Review your Jira ticket descriptions for clarity and completeness
Verify that linked Stories/Epics contain relevant requirements
Check that your code changes are in the expected areas
Last updated