Skip to content
Jira-native · Everything in one view

Cut your sprint planningin half.

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.

  • 30-day free trial — no credit card
  • Runs inside Jira Cloud, no separate login
  • One tab for all planning needs
< 5 min
Install to first planning session
0
Jira tabs to open during planning
100%
Runs on Atlassian Forge
01

Straight from the app

Say hello to your new favorite tool.

No mockups here — every screen is the shipping product, running on a real Jira Cloud site.

Ekko's sprint planning view inside Jira: task list, selected task with description, comments and linked work, and the task details sidebar
Status, estimates, description, comments, and linked work on every task — editable without leaving the list. Read the planning guide
A live Ekko sprint poker session: issue queue, voting deck, and QR invite
Issue queue, live voting deck, and a QR invite that pulls the whole room into the session. How sprint poker works
Ekko's sprint capacity summary: team capacity bar and per-person committed versus available breakdown
Committed versus available, per person, with the calculation shown — not a number you have to trust blindly. Ekko ships both themes and follows your Jira appearance setting. Same view, either way. How capacity is calculated
02

Live capacity

Live capacity tracking on every change.

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 calculated
  1. 01

    Assign a task

    Give EKK-431 to Mira and her committed hours update immediately. You know how much room she has left before you hand her anything else.

  2. 02

    Change an estimate

    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.

  3. 03

    Open the summary any time

    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

03
Estimate together

Sprint poker, built into Jira.

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.

  • Story points or hours — choose the unit per session
  • Blind voting with one-click reveal and auto-consensus check
  • Voters join by QR code or link — no install, no login
  • Accepted estimate writes back to Jira so the number sticks
Votes blind until revealNo anchoring, no peer pressure. Numbers only appear once everyone has locked in.
Consensus in one clickHighest-voted card becomes the accepted estimate — or keep the discussion going until the room agrees.
Back to Jira instantlyThe chosen estimate lands on the issue before your next sip of coffee.

The estimate that gets picked is the estimate that ships.

How sprint poker works
Live sessionHost · CS Sprint 1
EKK-412To do0/5 voted

Retry queue for Jira webhooks

Votes blind until reveal
  • Y
    SP
    You
  • A
    SP
    Aarav
  • S
    SP
    Sofia
  • J
    SP
    Jun
  • M
    SP
    Mira
Your turn —tap a card below to lock in your vote.
Your deckFibonacci + escape cards
Voters join in secondsShare the session link or QR. Works on any device — no install required.
Start free trial

04
Know your real capacity

Model your team’s real capacity.

Ekko 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

Pulled from Jira assignments

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.

Free capacity left this sprint77% booked
88hacross 6 teammates
480hpossible32hPTO72hoverhead288hassigned=88hfree
Per-person workload
assigned / available
  • Alex Chen56h / 63h89%
  • Sam Park39h / 63h62%
  • Jordan Reyes63h / 63h100%
  • Morgan Diaz32h / 63h51%
  • Riley Novak52h / 63h83%
  • Casey Singh45h / 63h71%

The same calculation runs inside the app, per person, in real time.

How capacity is calculated
Start free trial
05
Up and running in four steps

Four steps from install to planning.

Read the getting-started guide
  1. 01

    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.

  2. 02

    Complete onboarding

    A short configuration captures capacity mode (hours or points), working hours, working days, default meeting overhead, and the default sprint board.

  3. 03

    Define the team and schedule

    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.

  4. 04

    Plan the next sprint

    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.

06
Safe by design

Your data never leaves Atlassian.

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.

  • 01
    Stays inside your tenant
    Hosted on Atlassian Forge. No Ekko-operated servers, no egress to third parties, nothing new to add to your vendor list.
  • 02
    No separate login
    Authenticates through Jira. Respects existing project permissions and user context. No new identity to manage.
  • 03
    Jira is the source of truth
    Edits in Ekko write straight to Jira through Forge. No sync job, no parallel database, no drift.
  • 04
    Least-privilege scopes
    Only the Jira scopes planning and capacity need. Reviewable in your Atlassian admin before install.
07
FAQ

What security and delivery leads usually ask.

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 docs
  • No. Assignee, estimate, status, linked work, description, and comments are all editable in one place, for all tasks. An update goes straight to Jira through Forge. Open the issue in Jira only when you want the full admin surface — custom-field editors, workflow configuration, or historical activity.
30-day free trial

You’ve made it to the end.

Scrolling 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.

  • 30-day free trial on a real Jira site
  • No credit card — billing through Atlassian only if you stay
  • Installs from the Marketplace in minutes