How can I build a ticket dashboard in Confluence with multi-level grouping, per-group totals, and on

[David Romero]

Context

We’re a Support team that exports tickets to CSV from Jira/JSM every week and publishes them in Confluence for internal reviews. We want the report to be quick to scan, easy to filter, and downloadable for CS and Product.

Our sample CSV (simplified):

issueKey,summary,assignee,team,priority,status,created,dueDate,originalEstimate,loggedTime,breachedSLA
SUP-1024,"Checkout error",ana,Support L1,High,In Progress,2025-08-20,2025-08-25,8h,6.5h,false
SUP-1031,"Notifications missing",luis,Support L2,Medium,Waiting for Customer,2025-08-21,2025-08-28,6h,1.5h,false
SUP-1040,"Mobile bug",maria,Support L1,High,Done,2025-08-22,2025-08-24,10h,11h,true

What we want to achieve

1. Group by team, and within each team by priority, showing column-level aggregations in each group header (e.g., sum of loggedTime, % of breachedSLA). What’s the best way to configure nested grouping and per-column aggregation?
   
   
2. Add a footer row with overall totals (ticket count, sum of loggedTime, average originalEstimate, max delay, etc.) that updates with filters. Is this done via Footer aggregation?
   
   
3. Create calculated columns without touching the CSV, e.g.:
   
   
   • DelayDays = today() - dueDate
   • OverUnder = loggedTime - originalEstimate
   • SLA Status = IF(breachedSLA, "Breached", "OK")
     
     What syntax should we use, and how do we reference columns by name?
     
     
4. Improve readability: use a Compact layout for dense data and control table height to avoid long page scrolls. Any presets you recommend for ~800–1,200 rows in a weekly report?
   
   
5. Enable a search bar for instant filtering and show row numbers so we can reference tickets during standups.
   
   
6. Export the result to CSV and Excel with one click. Anything to consider when grouping is turned on?
   
   
7. Hide less relevant columns (created, assignee), rename headers (e.g., “loggedTime” → “Time Logged (h)”), and reorder columns via drag-and-drop so the focus is on team, priority, status, DelayDays, OverUnder.
   
   
8. Define a weekly refresh flow:
   
   
   • Option A: Attach the new CSV to the page and import from “attachments.”
     
     
   • Option B: Upload the file each time.
     
     What do you recommend for keeping history and performance in check? I see Simple Tables supports import from attachments/upload/paste and can save the table as a page attachment (auto for large tables). Best practices?
     
     
9. Bonus: sometimes our dataset comes from an API returning JSON with nested fields (e.g., issue.fields.assignee.displayName). How do we extract nested fields as columns?

What we’ve tried

We imported the CSV with Simple Tables and enabled search/export (works great). We still need help fine-tuning grouping + per-column aggregations, and defining the formulas for DelayDays and OverUnder. We’d also love advice on layout (Compact + height) and on the attachments-based refresh flow.

Could you share a recommended step-by-step configuration and a few example formulas/settings?

Thanks in advance @Mia Tamm _Simpleasyty_!