Jira reports with your own data in them.
Upload your budgets, rosters and cost centres. Report on them beside your Jira fields. No formula language.
Your data never leaves your Atlassian environment.
Easy Reporting runs on Forge, in a database that belongs to your site alone. It is built without permission to call any outside address. There is no analytics service, no external logging, and no subprocessor of any kind.
- One database per site
- Nothing is pooled. There is no shared store where one site's data sits next to another's.
- Your permissions, not ours
- You see the issues you can already see in Jira. A project you cannot open is a project you cannot report on.
- Encrypted at rest, where Atlassian keeps it
- Whatever data residency applies to your site applies here. There is no second location to assess.
- Uninstalling takes it with it
- The database is dropped with the app. There is no copy anywhere else, because there is nowhere else.
Bring your own numbers into the same table.
Upload a roster, a cost centre map or a budget as a CSV. Say which column matches a Jira assignee, project or issue key. Those columns then sit in your field list beside status and story points.
The match rate is the first thing you see. If 46 rows out of 1,284 found no Jira user, you get those 46 with a likely reason against each one. Rows that do not match are never joined.
Cost per story point by cost centre. Delivered work against budget. Throughput per head.
Build the report by clicking.
Three shelves: Split by, Measure and Filters. Click a field on the left to add it, click the cross to take it out.
"Count of issues and sum of story points, split by project and by month resolved, only including issues where status is Done." The sentence above the shelves rewrites itself as you build, so you can check what you asked for by reading it back.
Ask about the past, not only about today.
Every status change is recorded as it happens, one row per transition, from Jira's own changelog. Pick a date and see the board as it stood, with today beside it.
Twelve months of history, the same on every site. Inside that window the record is complete, so a report about a past date is a real query rather than an estimate.
It says so when a number needs a caveat.
Split by labels and one issue lands on several rows, so the rows add up to more than the total. Every reporting tool does this. Easy Reporting tells you, above the table, with the size of the error.
The Story points column adds up to 1,042. The real total is 742.
The warning travels with the report. It shows in your saved reports list, and it is written into the exported file.
One plan, priced per user.
The rate steps down as the site gets bigger, and each rate applies only to the users inside its band. So the 101st user is $0.60, and does not change what the 100th costs.
| Users | Rate |
|---|---|
| Up to 10 | $10 for the site |
| 11 to 100 | $3.00 |
| 101 to 250 | $0.60 |
| 251 to 1,000 | $0.25 |
| 1,001 and above | $0.20 |
Billed through the Atlassian Marketplace on the same cycle as your Jira subscription. The user count is your Jira user count, which is how the Marketplace licenses every app. Everything on this page is in the plan, and there is no edition above it to move up to. Evaluate it on the Marketplace's free trial, which runs the whole app on your real Jira data.
Questions people ask first.
What happens when I uninstall?
The database is dropped with the app. Every synced issue, every recorded status change, every uploaded file and every saved report goes with it. There is no copy anywhere else, because there is nowhere else. Export any saved reports you want to keep before you uninstall.
How much history do I get?
Twelve months, on every site, with no setting to change it. On the first sync Easy Reporting reads back 12 months of Jira's changelog. After that the window moves forward with today.
The window exists because of where the data lives. Your database sits on your own Atlassian site, where Atlassian caps it at 1 GiB. A fixed window is what keeps a complete record inside that cap. If you need figures going further back, put those reports on a schedule: Easy Reporting keeps the results of every run, dated, and nothing deletes them.
Can it email me a report?
No. Sending mail would mean handing your report to a service outside your Atlassian environment, and not doing that is the point of the app.
Two things happen instead. A report on a schedule runs as often as you like and keeps every run in the app, ready to open or download. And any report can go on a Jira dashboard, where it stays current on a page people already read.
Is there a size limit?
Each installation gets a fixed 1 GiB on Atlassian, shared between issue data, 12 months of status history, worklogs and anything you upload. That is comfortable for most sites up to roughly 40,000 issues.
If yours does not fit, we tell you which fields are too big before we store anything, and you turn those off. We will never store half a field, because half a field gives you wrong numbers with nothing on screen saying so.
What files can I upload?
CSV, up to a few thousand rows per file comfortably. Rosters, cost centre maps, budget lines, headcount plans and rate cards are what this is for. You see the space a file will take before the upload starts.
Each file carries its own permissions, so a salary band can be limited to three named people. Fields you cannot see do not appear in your field list at all.
What if someone renames a field in Jira?
Nothing happens to your reports. They are saved against the field's permanent Jira ID, never its name, so a rename cannot break one. The new name appears in your field list, and for one refresh cycle it shows as "Squad (was: Team)" so you can still tell what it is.
Do I need to be an administrator?
An administrator installs it, and the first sync starts on its own. There is nothing to switch on. After that anyone with access can build and save reports, and everyone sees only the issues they can already see in Jira.
Ask us something.
Tell us what you are trying to report on and we will tell you whether Easy Reporting does it today. If it does not, we will say so.
We read every message ourselves. There is no ticket queue and no chatbot.
Put your own numbers next to your Jira numbers.
Install it and the first sync starts straight away. Every field we can read is stored, so there is no step two.