Jira
Baz’s Jira Integration
Last updated
Baz’s Jira Integration
Last updated
By pulling in ticket information like titles, descriptions, issue types, and stakeholder comments, Baz ensures that every change request is grounded in intent. Reviewers no longer need to tab between Jira and GitHub to understand why a change exists—they get the full story, right where the code is.
Baz uses this context to:
Enrich AI-generated summaries and topics with business objectives.
Tailor prompts to reflect the goals and constraints from the Jira ticket.
Help reviewers focus on what’s important by aligning code changes to the original intent.
To enable Jira support:
Go to the Jira integration section located in Settings.
Click Configure and follow the authentication flow.
Once connected to your Jira Workspace, Baz will automatically attach ticket context to linked change requests.
Tip: Baz detects linked tickets using conventional branch names (e.g.
ABC-123) or Jira issue keys mentioned in the PR description.
Once enabled, Baz pulls the following fields from linked Jira issues:
Title and description – used to inform review summaries and reasoning.
Issue type – helps guide expectations (e.g. bug fix vs. feature).
Stakeholder comments – injected into review prompts as context.
This context is injected into workflows that eventually:
Generate summaries that reflect Jira objectives.
Break down topics based on feature or flow relevance.
Guide reviewers to evaluate changes through the lens of what the ticket was designed to accomplish.
