The Linear integration monitors SLA events across your entire Linear workspace and delivers them to LogBrew as push notifications. When an issue breaches its SLA or is approaching the deadline, you know about it on your phone before anyone has to ping you.Documentation Index
Fetch the complete documentation index at: https://docs.logbrew.co/llms.txt
Use this file to discover all available pages before exploring further.
What you’ll see
- SLA breached: an issue has exceeded its SLA deadline (Critical)
- SLA high-risk: an issue is approaching its SLA deadline and is at risk (Warning)
- SLA set: an SLA has been assigned to an issue (Info)
Connect Linear
Authorize with OAuth
LogBrew opens the Linear authorization screen. Approve the requested permissions for your Linear workspace.
One Linear connection creates exactly one LogBrew project, covering all issues in your Linear workspace. There is no per-team or per-project filtering at connection time.
Severity mapping
| Linear SLA event | LogBrew severity |
|---|---|
| SLA breached | Critical |
| SLA high-risk | Warning |
| SLA set | Info |
Two-way resolve sync
Resolve sync works in both directions:- Resolve in LogBrew. Swipe to resolve on any Linear SLA event in your feed, and LogBrew resolves the corresponding issue in Linear on your behalf.
- Resolve in Linear. When an issue is resolved in Linear (by you or a teammate), LogBrew receives the event and marks it resolved in your feed automatically.
Staying connected
LogBrew refreshes your Linear authorization automatically in the background. Your connection stays active without any manual re-authorization.