Jira Cloud app · built on Atlassian Forge
Estimate the whole sprint. Publish once.
Scope Planner puts every issue of a sprint, a backlog or any JQL in one editable table — story points, original and remaining time — keeps the numbers in a draft until the team agrees, and shows exactly what will change before anything reaches Jira.
- No external servers
- No data egress
- No tracking
How it works
From scope to Jira in four steps
Nothing touches your Jira issues until the last one — and you see exactly what it will write before you take it.
Prefer to watch? The 37-second demo shows the whole flow, from backlog to Jira.
-
1
Choose a scope
A board’s sprint or backlog, a project, or any JQL you write.
-
2
Estimate in one table
Story points on a numeric or T-shirt scale, original and remaining time. Inline edits, bulk fill and running totals as you go.
-
3
Draft, then share
Your work auto-saves to a private draft. Share it and it becomes the team draft; teammates merge their numbers in through a row-by-row review.
-
4
Review, then publish
Sprint Preview puts your value next to Jira’s, issue by issue. Publishing Pro writes them in one pass, with your own Jira permissions.
Estimate
The whole sprint on one screen
Stop opening issues one at a time in sprint planning or backlog refinement. Load a sprint, a backlog or any JQL into a spreadsheet-style table and estimate every issue right where you see it.
- Story points, original and remaining estimate — inline, or one value applied to a whole selection at once.
- Five scales: Fibonacci, Modified Fibonacci, Powers of 2, Linear and T-shirt sizes. Values snap to the scale, so nobody types 7.
- Totals update as you type and break down by epic, assignee, label or type.
Review
Every change, before Jira sees it
Estimates stay in a draft until you decide. Sprint Preview lists exactly what will change, issue by issue: your value next to what Jira holds now.
- Every edit lands in a private draft only you can see.
- Share it and it becomes the team draft. Teammates merge their numbers in through a row-by-row review, so nobody overwrites anyone by accident.
- Untick anything you want to leave alone, then publish Pro — with your own Jira permissions.
- If an issue fails, the rest still land, the reason is shown, and Retry repeats only the failures.
Plan Pro
Spot overload before the sprint starts
See who carries too much — and whether the sprint fits the velocity of your last five sprints — while there is still time to rebalance.
- Per-assignee workload flags anyone above 1.5× the team average.
- Target velocity is calculated from the board’s last five completed sprints. No number to maintain by hand.
- Estimation history for any issue, read from the Jira changelog: what it was, what it became, who changed it and when.
- Export the table to CSV with the columns you choose.
Screenshots
See it in Jira
Real screens from the app, on a demo sprint. Select one to see it full size.
-
Use the scale your team knows
Pick the scale your team already uses: Fibonacci, Modified Fibonacci, Powers of 2, Linear or T-shirt sizes. Values snap to the scale, so nobody types 7.
-
Apply one value to many issues
Select several issues and apply one value to all of them, or clear a batch, without leaving the table.
-
Totals by assignee, epic or label
Totals update as you type and break down by epic, assignee, label or type, so you see where the sprint is heavy before you commit to it.
-
Share once. One team draft
Share once and your draft becomes the team draft. Teammates merge their numbers into it through a row-by-row review, so nobody overwrites anyone by accident.
-
Publish in one pass Pro
Publish writes to your Jira estimate fields with your own Jira permissions. If an issue fails, the rest still land, the reason is shown, and Retry repeats only the failures.
-
Velocity from your last five sprints Pro
Target velocity is calculated from the average of the board's last five completed sprints. No number to maintain by hand.
-
See how every estimate changed Pro
Estimation history for any issue, read from the Jira changelog: what the estimate was, what it became, who changed it and when.
-
Export exactly the columns you need Pro
Export the table to CSV with the columns you choose, safe to open in Excel or Google Sheets.
Privacy by architecture
Your data never leaves Atlassian
Scope Planner runs entirely on Atlassian Forge. Its manifest declares no external network permissions, so the platform itself blocks any outbound call — enforced by Atlassian, not merely promised by us.
No servers of ours
Drafts and preferences live in Forge hosted storage, inside your own Atlassian site. We receive no copies of your data.
Your permissions, always
Every Jira read and write runs as you, so the app can’t see or change anything you couldn’t in Jira directly.
Account IDs only
People are identified by Atlassian account ID; names are fetched live, never stored. Private data is erased automatically when an account is deleted.
No tracking — here either
No analytics, cookies or advertising in the app. This website sets no cookies and loads nothing from anywhere else.
Free and Pro
Estimate for free. Publish with Pro.
Everyone on an installed site can estimate, keep drafts and preview the change. Pro writes the agreed numbers into Jira and adds the planning views.
Free
Included with the app
- The estimation table — inline and bulk editing, numeric and T-shirt scales, time estimates
- Private drafts and team-shared drafts
- Totals, breakdown, and column visibility
- Sprint Preview — see what a publish would change
Pro
Subscription through the Atlassian Marketplace
Everything in Free, plus:
- Publishing estimates to Jira (and retrying a failed publish)
- CSV export
- Per-assignee workload with capacity warnings
- Estimation history per issue
- Auto-calculated target velocity from closed sprints
Pro features are unlocked by a subscription or an active evaluation obtained through the Atlassian Marketplace, which handles all billing. Without one you can still estimate and keep drafts — you just cannot write the estimates into Jira. Your drafts are never deleted by a licence change.
Articles
Estimating sprints in Jira, with or without an app
Practical notes on what Jira does on its own, where it stops, and how to plan a sprint around it. All articles.
Questions
Asked before installing
Not here? The user guide covers every feature, or write to us.
Does anything reach Jira while we estimate?
No. Drafts live in the app’s own storage, not in your issues. Nothing is written to Jira until someone reviews the change in Sprint Preview and publishes it.
Can a teammate overwrite my numbers?
Not by accident. Only your private draft is edited directly; changes reach the team draft whole, through a review screen that shows row by row what will change.
What works without a Pro subscription?
The estimation table, private and team drafts, totals and Sprint Preview. You cannot publish estimates into Jira — your drafts are kept, and publishing becomes available as soon as a subscription or trial is active.
What does a Jira admin need to set up?
Once per site: which Jira fields hold your estimates. 🔍 Detect Fields scans your fields and suggests the mappings; the user guide walks through it.
Where is our data stored?
In Atlassian Forge hosted storage, inside your own Atlassian site. The developer operates no infrastructure of its own and receives no copies of your data. Details are in the privacy policy.
How do we get help?
Email support@dsplugins.dev. Every message is answered by the people who build the app; we aim to reply within one business day. Hours and what to include are on the support page.
Questions before you install?
Write to us — every message is answered by the people who build Scope Planner.