Levee for Jira

A unified Jira queue without the project-board sprawl. Levee pulls your assigned issues, mentions, approvals, risks, and follow-ups into one dashboard — and drafts the next comment so you can reply in seconds, not minutes.

Connect Atlassian

You'll be redirected to Atlassian to sign in and approve the app. By installing you agree to the Terms of Service and Privacy Policy.
Already a Levee user? Connect from your account.
Looking for Slack? See /install/slack.

Needs your reply Jira

3 issues mention you · updated in the last 24h

Drafted with the context Levee already read from the thread.

PROD-482 · In review · updated 2h ago

@you — can you sign off on the rate-limit change before we cut the release?

Suggested comment: Approved. Roll it out behind the feature flag we discussed; I'll watch the dashboards for the first hour.

CX-1207 · Blocked · updated 5h ago

@you flagged this is stuck waiting on the data team for the schema doc.

Suggested comment: Bumping the data team — Sara, mind dropping the schema draft here today so this can unblock?

OPS-93 · Open · overdue 4d

Vendor renewal approval — assignee left the team, ticket still open against you.

Suggested comment: Reassigning to procurement to pick up the renewal — original assignee no longer owns this.

What you get

Your queue, not the board

"Needs your reply", "follow-ups", overdue, stuck->14d, approval queue — already filtered to issues that actually involve you, across every project.

AI-drafted comments

Click Suggest reply on any issue. Levee reads the comment thread and drafts a context-aware response. Edit, then click Send to post it as you.

Project filter

Only care about three projects? Set a filter on /connections and every KPI, list, and search scopes to those. The rest stays out of sight.

What permissions Levee asks for

Read and reply, nothing more.

Levee uses Atlassian's OAuth 2.0 (3LO). You're redirected to Atlassian to sign in and approve, and we receive a short-lived access token plus a refresh token. Tokens are encrypted at rest with AES-256-GCM. You can revoke at id.atlassian.com → Security → Connected apps anytime.

Read scopes read

read:jira-user

Resolve Atlassian account IDs into display names + emails so dashboards read "Sara Mohamed" instead of an opaque ID, and so we can confirm the connection on your behalf.

read:jira-work

Read your issues, comments, projects, and the JQL search results that power every panel — "needs your reply", "approval queue", "stuck", etc.

Write scopes act

write:jira-work

Post the comments you write (or accept from the AI draft) back to the original issue, as your account. We never edit or delete existing content.

offline_access

Receive a refresh token so the dashboard stays connected without forcing you to re-auth every hour. Refresh tokens rotate on every use; revoke any time.

FAQ

Where's my data stored?

On a single server we control. All Atlassian tokens are encrypted at rest with AES-256-GCM. We don't sell, share, or run analytics on your data. Full privacy policy →

How do I disconnect?

Click Remove on /connections (deletes the encrypted token from our DB), or revoke at id.atlassian.com → Connected apps.

Does Levee touch every Jira ticket?

No. Every query is JQL-scoped to issues that involve you (assignee, mentions, watchers, approval queue). Set a project filter on /connections to scope tighter still.