A cycle time chart where every bar, dot and status opens into the arithmetic behind it.
Stintwise is a Jira dashboard gadget for cycle time and lead time. It shows you which work items it counted, which it left out, and exactly why — on the chart face, not in a settings page.
Try it on sample data, in your browser, without installing.
The problem it solves
You put a cycle-time chart on a dashboard. It says 6.2 days. Someone asks why, when that ticket obviously sat in review for three weeks. You cannot answer, because the chart will not tell you which work items it used or what it did with the ones it dropped.
What it does differently
It says what it left out
A line under the headline reads 374 work items charted · 25 excluded, or names the issue type or project shown, and every cause is itemised under the chart. Not a tooltip, not a setting — always on the chart face. Each cause opens the list of its work items, which links to the page explaining it; the one with no list, the item cap, links there itself.
Click any bar for the arithmetic
Every status segment with its entry, exit, counted and excluded time, then the total. The numbers add up on screen, because they are the same numbers.
An export that reconciles
One CSV row per status segment, one per work item, finished or in progress, and closing rows restating the 50th, 85th and 95th percentiles of cycle time and the 50th, 85th and 95th of lead time, and the Aging view's three lines. Check the chart in a spreadsheet without trusting the app at all — see the CSV format.
Weekends, working hours, and public holidays of 20 countries and of states and regions in 12 of them
A duration in days means 24 hours of counted time, or one working day where only working hours count, the average working day where they differ by weekday, and the chart says so under Time zone, build time and method and on every image of it. The settings ask which time is counted before a new tile is saved, so nothing is quietly removed from the first chart you see and nothing is quietly counted in it —how days are counted.
Six controls, and there will never be a seventh
Every additional setting is another way to get a number you cannot explain. What the six settings do. The team's days off are part of Public holidays, under its select, not a seventh control. What changes the view stays on the tile, where a wrong choice shows at once and is not a setting: one group or every group side by side, the 70% line, and a target of your own with how many work items met it. How a target is counted.
What it reads
Of each work item, finished or in progress, it keeps the id, key, creation date, issue type, parent, labels, components, team and status history, and of finished work the sprints it was in, by id and dates; and, for a chart's next build, for 97 hours, the status it is in now, its sprints and when it was last updated; and nothing more. It never asks Jira for descriptions, comments or assignees, and asks for summaries only of the parents you can open, as you, when you split a chart by parent; a test on every outgoing request enforces both; it keeps no sprint's name and no summary. Some things arrive anyway, because Jira sends them unasked: the identity of whoever made each status change, and anything the tool that made it attached; when Jira will not filter a work item's history, or its filter may leave out status changes that came from an import, the whole of it; with each sprint, its name, goal and planned end; with each parent, its summary, status and type; the site's field list, of which only the Sprint and Team fields' ids are used; the owner, sharing and description of the saved filter; the name, owner and sharing of the tile's dashboard; a board's location, which can name the person whose profile holds it, and the names of the boards that use a saved filter; and, while the settings of a gadget not yet configured are open, the configuring person's full profile, of which only the time zone is used. The app keeps what it needs and discards the rest as the response is read. The gadget's settings, among them the configuring person's time zone, are kept by Jira with the gadget. Apart from four product events that identify neither a person nor a work item, and log lines that Atlassian shares with the app's author unless an administrator turns off "Logs access", nothing is sent anywhere. The details are on the privacy page.
Support
Write to stintwise@adigium.com. Support is written documentation and written correspondence only — there is no live chat and no phone line, and that is a deliberate design choice rather than an oversight: the app is built and maintained by one person, and written answers scale where conversations do not. Every message the app can show links to a heading in the documentation, and every heading answers one question completely. The support page says what to send and when a first reply is sent.
Status
Stintwise is not yet listed on the Atlassian Marketplace. This site exists because the app links to it, and the documentation is complete and current — it is generated from the same files the app's own test suite checks its claims against.