What the work in Jira cost, from Jira's own worklogs. No timesheet app required, and the total says what it covers.
It goes into an invoice, a budget review, a decision about whether a project continues. Which is why the ways it can be quietly wrong matter more than the ways it can be obviously wrong.
| Somebody has no rate set | Their hours count as zero |
| You cannot see every issue | Your total is smaller than a colleague's |
| Work logged outside the period | Counted, or dropped, without a word |
| The read did not finish | A partial answer, presented as the answer |
| $650.00 |
| $650.00 from 6.5 hours across 2 issues. 5 hours were logged outside the period and are not included. This covers what your Jira account is allowed to see. Jira can hide whole issues, and it can hide individual worklogs on an issue you can otherwise read, so another account may get a different figure from the same report. |
Anybody with no rate has their hours reported and named, never valued at zero. A rate that cannot be read, including a negative one, is refused rather than rounded into a number nobody typed.
Price "Senior Engineers", not Priya. Somebody joining that group is priced the day they join, by the same Jira membership that already governs their access.
A per-person rate card is a list that rots. Every new hire is unrated until somebody notices, and their hours drop quietly out of every invoice, which is the exact failure this app exists to prevent. Groups remove the maintenance and the gap together.
It is also how the work is actually billed. A rate card reads "Senior Consultant $180", not a column of names. If you genuinely need one person on their own rate, a one-person Jira group does it.
The nearest competitor reads a separate timesheet product, which costs more than it does. One of its own reviewers puts it plainly: without that second product, it is "basically useless".
This reads Jira's native worklogs. If your team logs work in Jira, you already have everything it needs.
Worklogs carry a timezone. A report for the 8th that quietly means the 8th in UTC will exclude work logged at half past eleven that night and include work from the evening before. Your browser's timezone is detected, shown on the page, and used for the dates.
Export to Excel or CSV, and the coverage goes into the file: the total, the query, the period and its timezone. Work that was not billed is in there too, with the reason, because a billing report that quietly omits somebody's unrated hours looks complete and is not.
Where rounding the individual lines to the cent makes the column disagree with the exact total, the file says so. Nobody should be hunting a missing penny in a document going to a client.
Cost Trail is read only. It cannot change an issue or a worklog. It reads the work already in Jira when you run a report, saves only your rate-card settings in Forge, and sends nothing outside Atlassian.
That is why it qualifies for Atlassian's Runs on Atlassian programme. Your cost report stays where the work already lives.
Send this and it reaches a monitored inbox. Replies come from a person, in English, on business days. Anything that has actually stopped working gets looked at the same day.