Skip to content
Esc
navigateopen⌘Jpreview
Sign up
On this page

Fibery

Baz integration guide for Fibery

By pulling in Fibery entity data such as names, descriptions, types, and discussion comments, Baz ensures that every code change is grounded in product context. Reviewers no longer need to switch between Fibery and GitHub to understand why a change exists - they get the full context, right where the code is.

Baz uses Fibery context to:

  • Enrich AI-generated summaries and topics with your business objectives.
  • Tailor prompts to reflect the goals and constraints from the Fibery ticket.
  • Help reviewers focus on what’s important by aligning code changes to the original intent.
Configure Fibery integration

Configuring Baz & Fibery

To enable Fibery support:

  1. Go to the Fibery integration section in Settings.
  2. Click Configure and complete the authentication flow.
  3. Once connected to your Fibery workspace, Baz will automatically attach Fibery context to linked pull requests.

Tip: Baz detects linked Fibery entities using entity IDs in branch names or references included in the PR title or description.

How Baz Uses Fibery Data

Once enabled, Baz pulls the following data from linked Fibery entities:

  • Ticket name and description - used to shape review summaries and reasoning.
  • Status, priority, and group - helps set reviewer expectations.
  • Owners and contributors - injected into review prompts to guide validation.
  • Updates and discussion threads - used to enrich reviewer understanding.

This context is injected into Baz workflows to:

  • Generate summaries that reflect product intent and scope.
  • Structure review topics around features, flows, or decisions defined in Fibery.
  • Guide reviewers to evaluate changes through the lens of what the ticket was designed to accomplish.

FAQ

How does Baz know which Fibery item a change relates to?

From entity IDs in branch names, or references in the pull request title or description.

What does Baz read from Fibery?

Entity name and description, status, priority and group, owners and contributors, and updates and discussion threads.

Does connecting it change what reviewers see in the code host?

Yes, in the sense that the review itself gets richer: summaries, topics, and agent prompts carry the intent from Fibery, so reviewers do not have to open the tracker to understand why a change exists.

Nothing is attached to my pull request, what should I check?

Check that the integration is connected under Settings, Integrations, that the branch name or pull request description carries a recognizable identifier, and that the connected account can see the item in Fibery.

Was this page helpful?