ForgeboardGuide
/
Sign in

The report builder

Build a report by dragging fields: what to group by, measure and filter.

Report Builder

Compose a report by dragging fields onto three slots — what to group by, what to measure, and what to filter out. The preview runs as you build, so you see the answer before you decide whether to keep it.

The three slots

  • Group by — up to two. Each becomes a row in the table, or a bar on the chart. Drop a date here and it buckets by month; change that to day, week, quarter or year on the chip.
  • Measure — what gets counted or totalled. At least one is required; up to three can sit side by side.
  • Filters — narrow the rows before anything is grouped. The operators offered depend on the field, so a title can be searched but not compared as a range.

Every field can also be added with the + button next to it. Drag and drop cannot be driven from a keyboard, so the buttons are the equivalent path rather than a shortcut.

Choosing a chart

  • Table — every column, exact numbers. The right answer when a report is meant to be read rather than glanced at, and the only view that shows three measures honestly.
  • Bar — compares categories. Needs one grouping.
  • Line — shows a trend. Needs a date grouping; a line over statuses would imply an order that does not exist.
  • Donut — shows how a whole splits up. One grouping, one measure.

A chart that cannot draw the current fields is disabled with the reason on hover, rather than hidden — the reason is usually one field away from being fixed.

Sources

  • Issues — every issue: epics, stories, tasks and bugs.
  • Worklogs — time logged against issues, which is where hours and utilisation come from.

Switching source clears the canvas. A dimension of one source is not a dimension of the other, so carrying the selection across would build a report the server rejects.

Saving and sharing

A saved report is private until you share it. Sharing publishes it to everyone in the workspace who can read reports; only the owner can edit or delete it, so a report a team relies on cannot change underneath them.

Export any saved report as CSV from the toolbar. Every cell is quoted, so a name containing a comma cannot shift the columns.

A report scans at most 20,000 source rows. Past that the result is a slice rather than the whole dataset, and the preview says so — add a filter to narrow it rather than reading a truncated answer as complete.
Reports aggregate across every project's data at once, so they need the same cross-project access as the rest of Reports. That is why building and reading them needs the report permissions, not just access to a project.