Jira is now a first-class citizen in Focus Engine
Jira is now a first-class citizen in Focus Engine
v0.1.9 — Jira Integration (OAuth + Issues)
If your team runs on Jira, your sprint board has always been the source of truth for what you're supposed to be working on. Until now, that source of truth lived in a separate tab — one more system to check before you could figure out what to actually do today.
With v0.1.9, Jira connects directly to Focus Engine. Your sprint issues and assigned tasks flow into the daily briefing automatically, alongside your calendar, GitHub issues, Notion tasks, and email. The plan for your day is complete without opening Jira.
What's new
OAuth 2.0 connection to Jira Cloud
Connect via the standard Atlassian OAuth flow — no API tokens, no manual credential management. Authorise once and Focus Engine handles the rest.
Active sprint issue sync
Focus Engine knows which sprint is active and pulls every issue in that sprint assigned to you. Sprint-committed work shows up in the briefing without any manual input.
Assigned issue sync
Anything assigned to you in Jira — whether it's in a sprint, the backlog, or a separate project — is included. Nothing slips through because it wasn't in the current sprint view.
Rich metadata: priority, status, due date, epic link
A task title on its own isn't very useful. Every Jira issue brings its full context into Focus Engine:
- Priority tells the scheduling engine whether something is a Blocker or can wait.
- Status determines whether an issue belongs in "In Progress" or "Due Today."
- Due date feeds directly into deadline-aware prioritisation — if it's due today, it surfaces today.
- Epic link groups related work so the briefing gives you the bigger picture, not just isolated tickets.
Why Jira, and why now
Jira is the dominant issue tracker for mid-size engineering teams. It's where sprint planning happens, where work gets assigned, and where progress is tracked. The gap between Jira and a developer's actual calendar has always been a planning problem — sprints get committed in Jira, but focus time to do the sprint work rarely gets blocked on the calendar.
Focus Engine's core job is to bridge exactly that gap: take what you're supposed to work on (Jira) and connect it to when you can actually do it (your calendar). Jira issues are now fully eligible for the day planner — Blocker and Critical items are treated as urgent and scheduled first, with duration estimates and buffer time applied automatically.
Connecting takes about 30 seconds
- Go to Settings → Integrations.
- Click Connect Jira.
- Authorise access via Atlassian.
- Done — your next briefing will include your sprint and assigned issues.
Focus Engine only requests read access. It will never create, update, or transition issues in Jira.
Jira Cloud is supported in this release. Full documentation is available in the Jira Integration guide.