Can it change ticket status or assign work?

It can, and this is the part worth thinking about before you connect it. Transitions, comments and assignments all notify watchers, so a mistake is visible to your team rather than private to you. Asking for a comment with a proposed change, instead of the change itself, is a good habit while you are learning what it does well.

Does it search Confluence properly, or just read pages I link?

It searches. That is the main reason this connector is more useful than it first looks — you can ask a question without knowing which page holds the answer, which is exactly the situation where Confluence is hardest to use by hand.

We use Jira Service Management as well. Does that work?

Service Management issues are Jira issues, so they come through. Bear in mind that a comment on a customer-facing request may be visible to the customer, depending on how your project is configured — check that before you let an agent comment on service tickets.

Team collaboration

Atlassian (Jira + Confluence) + Burrak AI

One connector for Jira and Confluence — the tickets and the pages that explain them.

Connects with OAuth — revoke any time

Most of what a team knows is split across two places: the ticket that records what was decided, and the page that explains why. Reading either one alone gives you half the story, which is why writing a decent status update or onboarding note is such a slog — somebody has to hold both open at once. An agent with this connector reads across them, so it can answer questions that neither product answers on its own, and file the result back where people will actually see it.

In the connector catalogue: Manage Jira issues, search Confluence pages.

Things you could ask for

Written the way you would actually say them. An agent plans the steps itself.

“Summarise what this epic actually delivered, using the tickets and the Confluence pages they link to.”
“Read this bug report, search Confluence for anything we already wrote about this component, and add what you find as a comment.”
“Draft the release notes for this fix version from the issues it contains.”
“Every Monday, write me a plain summary of what moved in this project last week and what is now blocked.”
“Take these meeting notes and open Jira issues for every action item, linked back to the page.”

This is one connector for two products, authorised at your Atlassian account level — the agent can reach whatever that account can reach. If your account is a site admin, that is a lot. Connecting from a normal team member’s account gives you a much narrower blast radius, and is usually enough.

Connecting it

1Create a Burrak account — the free plan is enough to try this.
2Open Connectors and choose Atlassian (Jira + Confluence).
3Authorise Burrak in Atlassian (Jira + Confluence)'s own window. Your password never reaches us; we receive a token you can revoke whenever you like.
4Give an agent a task. It will use the connector when the work calls for it.

Start free How connectors work

Atlassian (Jira + Confluence) and Burrak, in practice

Can it change ticket status or assign work?: It can, and this is the part worth thinking about before you connect it. Transitions, comments and assignments all notify watchers, so a mistake is visible to your team rather than private to you. Asking for a comment with a proposed change, instead of the change itself, is a good habit while you are learning what it does well.
Does it search Confluence properly, or just read pages I link?: It searches. That is the main reason this connector is more useful than it first looks — you can ask a question without knowing which page holds the answer, which is exactly the situation where Confluence is hardest to use by hand.
We use Jira Service Management as well. Does that work?: Service Management issues are Jira issues, so they come through. Bear in mind that a comment on a customer-facing request may be visible to the customer, depending on how your project is configured — check that before you let an agent comment on service tickets.