Reports and exports

Reports is a tab on the Saguaro Hours page, open to every user.

Run a report

1. Choose a range: this week, last week, this month, last month or custom.
2. Optional filters: team, users, projects.
3. Group by one field, then optionally by a second: user, team, project, epic or parent, issue type, label, billable, or any attribute.
4. The screen shows totals per group, a grand total and a detail table.

Regrouping after the report has loaded is instant.

A long run shows how far it has got, an estimate of the time left once a few seconds have been timed, and a Cancel button. Cancel shows nothing from that run. The estimate is rough: a Jira rate limit wait or one very long issue moves it.

What counts

• Hours are native Jira worklogs, read as you. You see worklogs on issues you can browse.
• Days are bucketed in your Jira time zone.
• A worklog with several labels, or a person in several teams, is placed under one combined label. Totals do not double count.
• The screen shows the first 500 detail rows. Exports include all rows, up to the 25,000 limit.
• A report holds up to 25,000 worklogs. Above that it stops and shows no totals, because partial totals would be wrong for billing. Narrow the date range, or filter by team, user or project, and run it again.
• If the billable and attribute data cannot be read, the screen warns you instead of showing everything as not billable.

Saved reports

• Save the current setup under a name. You can keep up to 50.
• Saved reports belong to you. Load, Update and Delete (with confirmation) are available.
• A preset range such as This week moves forward when you load it. A custom range stays fixed.

Exports

• Summary CSV.
• Detail CSV.
• Excel (.xlsx) with Summary and Detail sheets.

CSV files use UTF-8 with a byte order mark and CRLF line ends. Text that starts with =, +, - or @ gets a leading quote so a worklog description cannot run as a spreadsheet formula. The files are built in your browser and are not sent anywhere.

Limits

• Up to 25,000 worklogs per report.
• If Jira keeps refusing with a rate limit after 90 seconds of waiting on one call, the report stops with a message and no table. It never shows part of the hours.

Measured in our load test, on 300 issues with one person's worklogs and one viewer:

• A report of 4,644 worklogs took 15 to 18 seconds.

Estimates, not measured. No report near 25,000 worklogs has been run. These figures are extrapolated from that load test of 5,970 worklogs, as about 4 ms per issue to search, 31 ms per issue to read and 1.1 ms per worklog for billable flags:

Time depends mostly on the number of issues. Many people, several viewers at once and very large sites have not been measured.

At 5 worklogs per person per working day, 25,000 is about 238 people for a month, 79 for a quarter and 19 for a year. These are arithmetic, not measurements. Larger ranges need a filter or a shorter range.