Skip to main content

Reporting and Board Export

Kanera reporting stays connected to the work. Export a whole board to Excel or JSON for backup, migration, or offline review. Use Table export when you need a filtered report shaped by the current columns, grouping, sorting, aggregates, or breakdown.

Choose the right export

NeedExportResult
Back up, migrate, or review one complete boardExport board from the board toolbarThe entire board data visible to you, as Excel or a structured Kanera JSON archive.
Export a filtered or grouped reportExport this table from TableThe current Table result as Excel or JSON.

To export a whole board, open it in Board view, select the download button labelled Export board, and choose Excel or JSON. Editors and admins can export; assigned-items-only Editors receive only data they are allowed to see. See Boards for the contents of each format and how to import a Kanera JSON archive.

Choose the reporting surface

QuestionBest surface
What fields and values are on these cards?Table
How do numeric values total by client, owner, stage, or another dimension?Table aggregates and breakdowns
Which organisations, workspaces, or boards are late or overloaded?Portfolio
Which cards make up a Portfolio metric?Portfolio Table drill-down
What moved or finished on a day?Work Done
What is one person or the team carrying?My Cards or Team Cards
What needs my attention this week?Home

Build a Table report

  1. Open a board, My Cards, Team Cards, or a Portfolio metric drill-down.
  2. Switch to Table.
  3. Set the board scope when using Global Work.
  4. Use search and filters to narrow the cards.
  5. Choose the columns to include.
  6. Group by the main reporting dimension.
  7. Choose the sort order.
  8. Add Sum or Avg aggregates for numeric custom fields.
  9. Add a second Break down by dimension when needed.
  10. Export to Excel or JSON.

For a report you will revisit, save the Global Work view. Saved views preserve the lens, source scope, filters, display, grouping, sorting, and Table presentation.

The Platform Delivery board in Table view with Labels visible, grouped by Client, and Billing Hours set to Sum.

Filters

Available filters can include:

  • Search text.
  • Organisation, workspace, or board scope.
  • Labels.
  • Assignees.
  • Workflow lists.
  • Due-date conditions and overdue status.
  • Completion-date range.
  • Archived state.
  • Supported custom field conditions.
  • Unassigned cards in Portfolio.

Filters run before grouping, aggregates, Portfolio metrics, and export. A saved view lets a team return to the same reporting definition without rebuilding it.

Grouping and columns

Common grouping choices include:

Group byUseful for
Organisation, workspace, or boardSource and portfolio analysis.
ListWork by workflow stage.
AssigneeOwnership and workload reports.
LabelWork by category, priority, or service.
Due dateDeadline and ageing reviews.
CompletionOpen-versus-completed summaries.
Custom fieldClient, department, risk, work type, target release, or another structured dimension.

Columns define the detail on each card row. Use the Columns menu to show built-in and custom fields, then reorder or resize them.

Aggregates

Aggregates summarize numeric custom fields inside each group:

  • Sum for hours, budget, points, cost, quantity, or revenue.
  • Avg for score, risk, confidence, complexity, or estimates.

Shared workspace fields make cross-board aggregates consistent. A field such as Hours or Effort has the same definition on every board in that workspace.

The Platform Delivery report collapsed to Client groups with summed Billing Hours.

Break down by

Break down by splits each group's numeric result by a second dimension.

GroupBreak down byQuestion
ClientWork TypeHow many hours went to each kind of work for each client?
AssigneePriorityHow much effort is each person carrying by priority?
ListRiskHow much high-risk work is in each workflow stage?
Due dateBoardWhich boards are driving work due soon?
LabelAssigneeWho owns each service category?

Multi-value fields can place a card into more than one matching bucket. This is deliberate: the breakdown shows every category the card contributes to.

The Platform Delivery report grouped by Client with Billing Hours broken down by Billing Month.

The same Client report with Billing Hours broken down by Assignee.

Portfolio reporting

Portfolio summarizes the current Global Work scope with:

  • Active cards.
  • Overdue cards.
  • Cards due in the next seven days.
  • Unassigned cards.
  • Completed cards in the chosen reporting period.
  • Overdue assigned checklist items.

When board health is enabled, each board row also shows On track, Needs attention, At risk, or No active work. Workspace and organisation rows use the worst enabled child-board status; they do not merge all child cards into one percentage. Disabled boards are excluded from health rollups. See Board Health for the signal thresholds and configuration.

The hierarchy compares organisations, workspaces, standalone-board groups, and boards. Select any metric to open its cards in Table.

Portfolio also includes 60 days of movement and delivery activity. The activity and metric counts use the same filter set, so a client, label, assignee, or custom-field filter changes both.

Use Portfolio when you need the rollup first. Use Table when you need card detail or calculations.

Portfolio reporting with headline delivery metrics, activity strips, and expandable organisation, workspace, and board rows.

Table Excel workbook

Table exports an .xlsx workbook.

SheetWhat it contains
CardsThe filtered card rows, selected columns, grouping, and card links.
SummaryTidy numeric aggregate rows for filtering, formulas, and PivotTables.
ReportA readable grouped report when aggregates are enabled.

Without aggregates, the workbook can contain only the Cards sheet.

Each exported card row includes its human-readable Key and a clean card-detail link. These are more useful for reviews and cross-system references than Kanera's internal card id.

The Summary sheet keeps values numeric for PivotTables, AutoFilter, SUMIFS, AVERAGEIFS, and downstream templates. The Report sheet presents those values in a stakeholder-friendly layout.

Table JSON export

JSON export contains the same report definition and result in structured form:

  • Export metadata.
  • Source scope.
  • Filters.
  • Grouping and sorting.
  • Selected columns.
  • Groups and card rows.
  • Aggregate and breakdown configuration.
  • Summary rows when aggregates are enabled.

Use Table JSON for scripts, integrations, or another reporting pipeline. For a restorable archive of a complete board, use Export board -> JSON instead.

Completed work

Use Filter -> Completed to include cards from a chosen completion-date range in Table. They can be grouped, sorted, aggregated, and exported with active cards.

Use completed-card history when you need a focused archive of completed cards without mixing them into the main result.

Use Work Done when the question is about activity on a specific day rather than the current or completed card set.

Example reports

  • Monthly billing: filter completed cards by date, group by Client, sum Hours, and break down by Work Type.
  • Team load: open Team Cards, group by Assignee, sum Effort, and break down by Priority.
  • Portfolio risk: filter by a Risk field, compare overdue counts and cards due in the next seven days by board, then open a metric drill-down.
  • Deadline pressure: group by Due date, sum Effort, and break down by Board.
  • Delivery review: use Portfolio activity for the trend, then Work Done for the day-level event detail.