Last updated Oct 16, 2026
Work trackers (Linear, Jira, Asana)
Connect the issue tracker your team lives in so project goals can pull live counts and Operator can summarize what's in flight.
integration
core
Connect a work tracker so project-shaped goals ("ship initiative X", "close N bugs") can pull live counts straight from the source. Brev also reads context from your tickets so AI insights know what's stuck and what's moving.
Supported trackers #
- Linear: issues, projects, cycles, statuses, labels.
- Jira: projects, issues, sprints, statuses, custom fields.
- Asana: projects, tasks, milestones.
ClickUp and monday.com are in the catalog but can't be connected yet. Their cards show Request access, so you can tell the Brev team you want them.
How to connect #
- Find your tracker in the Data section of IntegrationsEach has its own card. Click Connect.
- Authorize in the tracker's windowYou'll be redirected to sign in and grant access to your workspace. Brev asks for access to issues, projects, and metadata, and only reads them to track goals. Operator can also change Jira issues, but only with your say-so (below). If your account reaches several workspaces or sites, you choose which one when you connect a goal.
- Connect a goal to a project or queryOn any project-shaped goal, click 'Connect to integration' from the goal panel and pick what to track: a Linear project, an Asana project, or a Jira project or query. The goal's value updates automatically as tickets move.For Jira, pick your Atlassian site and then the project you want to track. Brev writes the query for you and shows a live count before you save. If you need something a project on its own can't express (a sprint, an assignee, a label), turn on Advanced and write the JQL yourself.An Advanced query has to be scoped to something, a project, an issue key, a sprint, a filter. Jira refuses to run a query that would search everything, so 'status = "In Progress"' on its own is rejected as you type; 'project = "ABC" AND status = "In Progress"' is fine. If Jira turns down a query for any other reason, the message you see is Jira's own.
Where the data appears #
- Goal values: counts and statuses from the connected project or query populate the goal automatically. Trajectory chart points are tagged with the tracker's icon.
- AI Goal Insights: when issues are blocked, reassigned, or stalled, the goal's Insights tab calls that out.
- Suggested check-ins: when tickets close in bulk (sprint end, milestone hit), Brev pre-drafts a check-in with the new value for the owner to confirm.
- Operator answers: ask Operator about a project and it'll pull live status from your tracker.
- Operator changes (Jira): with your say-so, Operator can file a Jira issue, move one to another status, or comment on one. Details below.
Operator can also file, move and comment on Jira issues
Ask it to open a ticket, move one to another status, or add a comment, and it will, but only after you say yes. It should tell you what it's about to change and wait; what actually holds the line is that the change is refused unless your own last message agreed to it. "Yes" on its own works, and so does saying the change back ("yes, create them"), but a reply that adds anything new, like a condition or an extra name, is treated as an instruction rather than a yes. One yes makes one change, so a second change needs asking again.Filing several issues at once is one change, not several: ask for a list, check what Operator shows you, and one yes files the lot, up to 20 issues, all into the same project. If Jira turns one of them down, Operator stops there and tells you which ones it filed, which one failed and why, and which it never got to.The change is made under your Jira account and your team sees it as yours, so Operator can only do what you could do in Jira yourself. Brev can't undo it afterwards.Changes need a permission that reads-only connections don't have. If your Jira connection was made before this existed, the first change will ask you to reconnect the Jira card and allow Brev to create and update issues, a one-time step. Reading Jira keeps working either way, and so does the scheduled sync.Operator won't make a change from a shared Slack or Teams channel, only from a DM or the web chat: in a busy channel it can't be sure whose "yes" it just read, and the change would go out under your name. Reading in a channel is unaffected.How often it refreshes #
- Tracker connections refresh every 30 minutes from 11:00 to 23:59 UTC and every 4 hours overnight.
- Linear and Jira also send webhook updates for high-signal events (status changes on tracked items). Those land in seconds.
- Linear can also collect Project Updates as check-ins: switch on 'Collect Project Updates' when you connect a Linear project, and a progress update written on that project in Linear shows up on the goal as a check-in via Linear, full text included.
- The Jira fast path is off unless you ask for it. Switch on 'Update in real time' when you set up or edit a Jira connection, then reconnect the Jira card once so Brev can register the update with your Atlassian site. The newer permission is only granted on a fresh connect. Until both are done, the connection keeps updating on the regular schedule.
- Real-time Jira updates only apply to connections whose JQL names a project (for example 'project = BRE'). A query with no project stays on the regular schedule.
- Click the refresh icon on the goal's connection to pull right now.
- Submitting a check-in on a connected goal triggers an on-demand refresh of that goal's connection.
Common issues #
- Counts seem off
- Open the goal's integration connection (kebab → Edit connection) and compare the connected project or query against what you see in the tracker. The most common cause is a scope mismatch (e.g. project moved to a new team).
- Jira doesn't show some projects
- Jira's permission model is granular. Brev only sees projects your user has Browse access to. Ask your Jira admin to grant your user access, or connect with a service account that has broader permissions.
- Linear shows duplicate counts
- If a goal's connected project is also tracked by a parent goal, the counts roll up correctly but can look surprising. Check the parent goal. Counts shown on the goal detail are scoped to its own connection, not the rollup.
- Linear says webhook setup needs an admin
- The Project Updates webhook is created once for your whole organization, and only an organization admin can create it. Ask an admin to open a Linear connection once with 'Collect Project Updates' switched on; after that, everyone's connections show it as configured. Goal progress keeps syncing on its regular schedule either way.
Give feedback
Was this page helpful?
Related
- Connecting an integration
How any integration in Brev works: the connect flow, what Brev sees, how often it refreshes, and how to disconnect.
- Goal detail
The side panel, full-page view and /goals page for one goal: progress and check-ins, insights, alignment, milestones, actions, and how progress rolls up from sub-goals.
- Data warehouses & BI (BigQuery, Snowflake, PowerBI, Sigma)
Anchor KPI goals on live SQL or BI tool data. The value on the goal is always whatever your warehouse says right now.
- Docs & spreadsheets (Google Sheets, Excel, Google Drive)
Pull goal values from a Google Sheet or Excel cell, or give Brev's AI context from files you add from Google Drive.