Reporting and Excel Export
Kanera reporting starts in the same place your team already works: board and Assigned Work views. You filter the cards you care about, shape them in List view, add numeric summaries, optionally break those summaries down by another dimension, then export the result to Excel or JSON.
This is powerful because Kanera workspaces share lists, labels, members, and custom fields across boards. A report can compare work from several boards without first cleaning up different board structures in a spreadsheet.
Build a report
Use this flow when you need a spreadsheet-ready report.
- Open a board or Assigned Work.
- Switch to List view.
- Use search and filters to narrow the report.
- Choose the columns you want to include.
- Group the rows by the main reporting dimension.
- Add Sum or Avg aggregates for number custom fields.
- Use Break down by when you want each group's numbers split by another dimension.
- Export to Excel or JSON.
For example, a client delivery team might open Assigned Work, filter to completed work from last month, group by Client, aggregate Hours, break down by Work Type, and export one workbook for billing review.
What filters control
Filters decide which cards are loaded into the report before grouping, summaries, and export happen.
Depending on the view, you can filter by:
- Search text.
- Board, when using Assigned Work across multiple boards.
- Labels.
- Members.
- Supported custom field values, including select and user fields.
- Overdue status in active work views.
- Completed date range.
- Archived cards when reviewing archived work.
Filters combine with each other. If you choose a board, a label, and a completed date range, the List view and export use cards that match that combination.
Completed cards are especially useful for reporting. Use Filter -> Completed to bring cards completed in a chosen date range back into the main List view. Once loaded, those cards can be grouped, sorted, aggregated, and exported with active cards in the same report.
Grouping and columns
Grouping answers the first reporting question: "What should this report be organized by?"
Common group choices include:
| Group by | Useful for |
|---|---|
| List | Work by workflow stage. |
| Assignee | Workload and ownership reports. |
| Label | Work by category, service, priority, or tag. |
| Due date | Deadline and ageing reviews. |
| Completion | Open-versus-completed summaries. |
| Custom field | Client, department, risk, work type, target release, owner, or other structured dimensions. |
Columns decide what appears on each card row in the Cards sheet. Use the Columns menu to show built-in fields and custom fields, then reorder or resize them before export.
Aggregates
Aggregates summarize number custom fields inside each group.
For each number field, you can show:
- Sum, for totals such as hours, budget, points, cost, quantity, or revenue.
- Avg, for averages such as score, risk, confidence, complexity, or cycle estimate.
Because custom fields are workspace-wide, the same numeric field can be summarized across several boards in Assigned Work. That means a field such as Hours, Budget, or Effort has the same meaning everywhere in the workspace report.
Break down by
Break down by adds a second reporting dimension to aggregates.
The top-level Group still controls the main sections of the report. Break down by splits each group's numeric totals into buckets.
Examples:
| Group | Break down by | What it answers |
|---|---|---|
| Client | Work Type | How many hours went to custom work, support, internal fixes, or onboarding for each client? |
| Assignee | Priority | How much effort is each person carrying by priority? |
| List | Risk | How much high-risk work is sitting in each workflow stage? |
| Due date | Board | Which boards are driving work due this week? |
| Label | Assignee | Who owns the work in each service category? |
The breakdown uses the same dimensions available for grouping, including built-in dimensions and supported custom fields. If a card matches multiple buckets, such as multiple labels or multiple select values, it can contribute to each matching bucket. That is intentional: the breakdown answers where the work applies, not only where it can be forced into a single bucket.
Excel workbook sheets
List view exports an .xlsx workbook. The workbook is designed for both human review and spreadsheet analysis.
| Sheet | What it contains |
|---|---|
| Cards | The visible report rows, grouped like List view, with the selected columns and card detail links. |
| Summary | Tidy numeric aggregate rows when aggregates are enabled. Each row is a group, optional breakdown bucket, field, metric, value, and total. |
| Report | A presentation sheet when aggregates are enabled. It combines card rows with summary and total rows that reference the Summary sheet with formulas. |
If no aggregates are enabled, the Excel export only needs the Cards sheet.
The Summary sheet keeps values numeric and filterable, which makes it useful for PivotTables, AutoFilter, SUMIFS, AVERAGEIFS, and downstream reporting templates. The Report sheet gives stakeholders a more readable layout while keeping the Summary sheet as the single source of aggregate truth.
JSON export
JSON export contains the same report payload in structured form:
- Metadata such as board name, export time, grouping, sorting, selected columns, aggregate configuration, and breakdown choice.
- Groups and card rows.
- Aggregate summary rows when aggregates are enabled.
Use JSON when another system, script, or integration needs to consume the report without opening Excel.
Completed-card history export
The separate completed-card history panel can also export matching completed cards to Excel or JSON. Use it when you want a focused completed-work archive without adding completed cards back into the main board or Assigned Work List view.
Use the main List view export when completed work needs to participate in filters, grouping, aggregates, breakdowns, and cross-board reporting.
Example reports
Useful reports include:
- Monthly client billing: filter completed cards by date, group by Client, aggregate Hours, break down by Work Type.
- Team workload: open Assigned Work, group by Assignee, aggregate Effort, break down by Priority.
- Delivery risk: group by List, aggregate Budget or Hours, break down by Risk.
- Due-date pressure: group by Due date, aggregate Effort, break down by Board.
- Review throughput: filter completed cards, group by Completion or List, aggregate Points, break down by Assignee.