Every Jira question, one chart away.
Group any set of issues by status, assignee, sprint, epic or time, pick one of twelve chart types, and click any bar to see the issues behind it. The charts live inside Jira, and so does the data.
The real module, running right here.
Working software on sample data — the same interface that renders inside Jira. It plays a short tour when it comes into view; click anywhere in it to take over.
620 generated issues so you can explore without connecting anything. Installed in Jira it reads your real projects, and issue data is limited to the projects the person looking at it can browse.
Built for the job, not the brochure.
Group, split and measure
Group by status, assignee, type, priority, project, epic or sprint, split by a second field, and measure issue count, story points, hours logged, estimates or age — by day, week, month or quarter.
Twelve ways to draw it
Bar, stacked, horizontal, line, area, bar-and-line, pie, donut, gauge, funnel, pivot table and a single value. Change the type and the same data redraws.
Pivot tables that read like reports
Rows and columns from any two fields, with totals and heatmap cells so the outliers stand out before you read a number.
Flow metrics built in
Time in status, lead time, cycle time and cumulative flow, worked out from each issue’s status history rather than from a field someone has to fill in.
Calculations on top
Cumulative sums, percent of total, a three-period moving average and a linear trend line, plus a target line when you have one to hit.
Click through to the issues
Every bar, slice, cell and point opens the list of issues behind it, so a chart is where a conversation starts rather than ends.
Three steps from install to answer.
Start from a preset
Open by priority, throughput trend, cycle time by type, workload by person — or a blank chart.
Shape the question
Pick what to group by, what to split by, what to measure, and any calculation or filter.
Save, share, pin
Save it, clone it, share it with everyone on your site, export CSV or PNG, or add it to a Jira dashboard as a gadget.
Inside Atlassian, with Jira’s rules.
Charts read from a copy of your issues kept in Forge storage and refreshed every hour, because Jira’s API is too slow to draw from directly. The copy lives inside Atlassian’s boundary, not on a vendor’s server. What “never leaves your instance” means →
- Issue data is limited to the projects the person looking can browse
- Projects with issue security levels are answered by a live query run as that person, so Jira decides
- Hours logged can be a measure in any chart, following the same rules as timesheets
- Saved reports are stored in the app’s own Forge storage
Straight answers.
How is it fast on a large Jira site?
The app keeps a copy of your issues in Forge storage, refreshed every hour, and of your worklogs, refreshed every five minutes. Charts read up to the 10,000 most recently created issues from that copy rather than asking Jira each time. Every serious app in this space keeps a copy — the difference is where the copy lives.
Can a chart show issues someone isn’t allowed to see?
No. Issue data is limited to the projects the viewer can browse, and projects where issues carry a security level are answered by a live query run as that viewer.
Can I put a chart on a Jira dashboard?
Yes. Any saved chart can be added to a Jira dashboard as a gadget.
Guides and articles.
Cycle time, lead time and throughput in Jira: what they measure
Three numbers describe how work flows through a Jira project. They are easy to confuse and easy to get subtly wrong — here is what each one measures and how to chart it.
Read the guide →Turn a support address into Jira issues with Cloudflare Email Routing
Forward a support address on your own domain into Jira, so each new message becomes an issue and each reply lands as a comment — without giving any app a mailbox.
Read the guide →See Claude Code spend per person, team and Jira issue
Point Claude Code’s own telemetry and a GitHub webhook at Workforce Intelligence, and see what AI coding costs — per person, per team, and per Jira issue it helped build.
Read the guide →Be first in when it opens.
One email when early access opens. Nothing else — no newsletter, no drip sequence, and the list isn't shared with anyone.
Early access members get the first year at launch pricing, locked.
Your address is stored with Resend, the email service that will send that one email.