Install from the Marketplace
Install from the Atlassian Marketplace. Ekko deploys to the Forge runtime inside your Jira Cloud tenant. No servers to provision, no keys to rotate.
Edit assignee, estimate, status, linked work, description, and comments from a single planning view. Stop juggling a dozen Jira tabs to get through a sprint.
Straight from the app
No mockups here — every screen is the shipping product, running on a real Jira Cloud site.
Live capacity
Every assignee change, estimate edit, and story point update recalculates capacity instantly — for that person and for the whole team. You see who has room and who is overloaded while you plan, not after the sprint starts.
How capacity is calculatedGive EKK-431 to Mira and her committed hours update immediately. You know how much room she has left before you hand her anything else.
Raise the estimate from 8h to 18h and the math follows. That pushes Mira past her 40 hours, so her bar turns amber on the spot — not halfway through the sprint.
The Capacity button sits in the top right of the planning view. One click shows committed versus available hours for every person on the team, always current.
Assigning the task and raising the estimate updated this bar instantly — Mira is now over her 40-hour limit, and you can see it before committing the sprint.
The Capacity button in the top bar opens this team summary at any time. The numbers are always current — there is no report to run.
0 of 5 voted
Run a full planning-poker session without leaving the sprint. Your team votes on each task in story points or hours, votes stay blind until everyone is in, and the chosen estimate writes straight back to the issue. No side-channel app, no screen-sharing, no pasting numbers later.
The estimate that gets picked is the estimate that ships.
How sprint poker worksEkko reads every task assigned to each person — in hours or story points — subtracts PTO and meetings, and shows you exactly how much time each teammate has left before the sprint is full.
Inputs
In the app, this number is summed automatically from every issue assigned to each teammate — hours or story points.
Inside Jira, Ekko pulls the real number here automatically from each teammate’s assigned issues — hours or story points, partial PTO, and per-person overrides included.
The same calculation runs inside the app, per person, in real time.
How capacity is calculatedInstall from the Atlassian Marketplace. Ekko deploys to the Forge runtime inside your Jira Cloud tenant. No servers to provision, no keys to rotate.
A short configuration captures capacity mode (hours or points), working hours, working days, default meeting overhead, and the default sprint board.
Pick team members per project, bulk-add from the user list, and override capacity where it varies. Add holidays once; PTO goes in as it comes up.
Open the planning view with real capacity, linked-task context, and in-place editing for every detail — assignee, estimate, status, description, comments. Nothing opens in a new tab.
Ekko is an Atlassian Forge app. It runs inside your Jira Cloud tenant, uses Jira’s APIs, permissions, and user context, and keeps its own settings in Forge storage. There are no Ekko-operated servers, no third-party processors, and no copy of your issue data outside the Atlassian trust boundary.
Ten questions we hear most often on calls with engineering managers, platform teams, and Atlassian admins. The fastest way to answer the rest is to run Ekko against your own sprint — the 30-day trial is free, needs no credit card, and installs in minutes.
Start your free trialBrowse all docsScrolling this far was the hard part. The rest takes minutes: start the 30-day trial from the Atlassian Marketplace, complete a short setup, and plan your next sprint against real capacity, linked work, and every task detail — editable in place, in the tool your team already uses every day.