Spinzy Digital
Finance and procurement reporting, built for Confluence.
Computed columns, hierarchical subtotals, and clean CSV/Excel/JSON import — the structured reporting Confluence's native tables don't do.
Confluence tables are fine for a checklist. They fall apart the moment finance or procurement needs a real number: a computed total, a subtotal by department and vendor, a grand total that reconciles. Teams end up exporting to Excel, doing the math there, and pasting a screenshot back into Confluence — which means the "report" is stale the moment it's pasted.
Computed columns
Define a column as a formula referencing other columns (e.g. Unit Price × Quantity) and it recalculates automatically. Broken references are flagged clearly, never silently wrong.
Hierarchical grouping with subtotals
Group by department, then vendor, then whatever else — get subtotals at every level, plus a grand total, without building it by hand.
Import CSV, Excel, or JSON
Paste data, upload a .xlsx file, or bring in JSON — with a column-mapping step so a source file's headers don't have to match your report exactly.
It's a Confluence macro
No separate tool, no separate login — the report lives on the page your team already reads.
Built for finance, procurement, and ops teams who need Confluence pages with numbers people can actually trust — not a generic reporting tool trying to be everything to everyone.
Installation & setup
Prerequisites
- A Confluence Cloud site — this app runs on Atlassian Forge, so there's no self-hosted Confluence support.
- Site admin or Confluence space admin permission, to install apps from the Atlassian Marketplace.
- No external accounts, API keys, or database setup. The app runs entirely inside your Atlassian instance.
Installing the app
- From the Atlassian Marketplace listing, click Get app (or Try it free during the trial period).
- Confirm the requested permissions on the install screen: read/write access to the Confluence pages where you add the macro, and storage access via Forge's own storage APIs to save report definitions and imported data. No data leaves Atlassian's infrastructure.
- Once installed, the macro is available on any page in your site immediately — there's no per-space enablement step.
Adding the macro to a page
- Open (or create) a Confluence page, click + to insert content, and search for Structured Ops Reporting.
- Insert the macro. It opens in an empty Configure state.
- Configuration and data are scoped to that macro instance — adding the macro to multiple pages creates independent reports.
Permissions model
- Anyone who can edit the page can configure the report: define columns, import data, edit rows.
- Anyone who can view the page can view the rendered report table — no separate report-viewer permission is required.
- There is currently no per-report access control beyond standard Confluence page permissions.
User guide
Quick start
- Import or enter data. Paste a CSV, upload an Excel (.xlsx) file, or type rows in manually. On file import, map source columns to report columns — column names don't need to match exactly.
- Define a computed column. Add a column with a formula referencing other columns in the same row, e.g.
Total = Unit Price × Quantity. Supported operators:+,-,×,÷. - Group and get subtotals. Choose one or more columns to group by (e.g. Department → Vendor). The report renders subtotal rows at each level plus a grand total — no manual rollup needed.
Core features
Computed columns
Evaluated live from the underlying row data, not stored as a static value — editing a source cell automatically updates every column that depends on it. If a formula references a column that's missing or has been renamed, the cell shows a clear error instead of a silent zero or blank.
Hierarchical grouping
Supports at least two levels of grouping (e.g. Department, then Vendor). Each level gets its own subtotal row, computed from the same formulas as the detail rows.
Data import
CSV and Excel (.xlsx, first sheet only) are supported today. A column-mapping step lets you rename incoming columns on the way in rather than editing the source file. Malformed or missing columns produce a specific error rather than silently dropping rows.
Manual entry
For small datasets, skip import entirely: define your columns and type data directly into the table.
Known limitations (current release)
- No chart/graph rendering yet — table view only.
- No export back to CSV/Excel yet.
- No live Jira data source — file import and manual entry only.
- Excel import reads the first sheet only.
- Report size ceiling is roughly 200KB of underlying data (a few thousand rows, depending on column count); exceeding it shows a clear error rather than truncating silently.
FAQ
Why did my formula show an error instead of a number?
The referenced column is missing, renamed, or contains a non-numeric value in that row. This is intentional — the app surfaces broken calculations instead of returning a silently wrong or blank result.
What happens if my import file is too large?
You'll see an explicit size-limit error. Split the import into smaller batches (e.g. by department or date range) and import each separately into the same report.
Can I use this without importing a file?
Yes — define your columns and enter rows manually, no file needed.
Does this pull live data from Jira or an external database?
Not in the current release. Data comes from CSV/Excel import or manual entry only.
30-day free trial. No credit card to start.
| Team size | Price |
|---|---|
| Up to 10 users | $10/month |
| Up to 25 users | $25/month |
| Up to 50 users | $50/month |
| Up to 100 users | $90/month |
| Up to 250 users | $180/month |