Capabilities / Reports

Hours reports

Sands builds hours tables from Jira worklogs, grouped the way agencies bill, ready to paste into an invoice email or a document.

Asking for a report

Name the project and the period, and anything to leave out.

Try asking

Hours report for Acme for September, excluding the internal tooling epic

Hours count by the date the time was logged. Sands fetches every worklog on every matching ticket, so nothing is silently cut off on large projects.

The table

You get a title, the table, and a short rounding note. Rows group by the structure your board uses: components first, then labels, otherwise one list ordered by ticket. Totals and a by-person breakdown sit at the bottom of the same table.

Anything only you need to know, like tickets that could not be read, appears under Notes for you below the table and is left out when you copy.

Leaving work out

  • Exclude a ticket and everything under it is excluded too.
  • Exclude an epic by naming it, or by naming any ticket inside it.
  • Say it in plain words: "without the internal tooling work" works.

Adding columns

Ask for more detail on the same report, like the activity for each row, and Sands adds it to the table it already built. The hours do not change. If a ticket has no value for the new column, the cell stays empty.

Try asking

Add the activity for each row

Copying

Click Copy under the reply. The table pastes as a real table into Gmail, Pages, Google Docs and Word, and as cells into a spreadsheet.

Same question, same numbers

The hours are computed and written into the table by Sands' reporting tools, not typed by the model. Ask the same question twice and you get the same table.