Installing and finding the app
Install from the Atlassian Marketplace. There is no account to create, no key to paste and nothing to configure: the app runs on Atlassian's own Forge platform and is ready the moment it is installed.
After installing, open it from the left sidebar of Confluence: Apps → Field Report.
The first scan
The first time you open the app it reads the pages you can see and records what it finds. The screen tells you how far it got and what it found — for example 20 of 39 pages (51%) have named fields — before you have configured anything.
After that the index keeps itself true on its own. Every page you create, edit, delete or restore is picked up as it happens, and once an hour the app compares versions and re-reads only the pages that moved. Scan now, top right, forces a full pass if you want one.
What Field Report reads
- Page properties — the details macro, the way most teams already record structure.
- Tables with a header row — each column becomes a field.
- Status lozenges, dates, mentions and task items.
- Labels, authors, spaces and page trees.
- Links, and the text behind them — including the host each link points at.
- Typed values written in plain text — versions, amounts, codes.
Nothing has to be written in a particular way for this to work, and nothing on your pages is changed by reading them.
Filtering, grouping and sorting
Every value the app found becomes a filter with a count beside it. Tick one and the list narrows; tick it again and it comes back. The number at the head of the list always says how many pages you are looking at.
Group by puts the list under headings — by label, by link host, or by how many outgoing links a page has — with a count on each heading, and a total of a second field inside each group where that makes sense. A heading is a way back into the plain list, filtered to that group, not a table you get stuck in.
You can sort on several columns at once, and filter by author, by space and by when a page was last updated.
Saved views and links
A view is the screen you were on, under a name: the same filters, the same grouping, the same sort. Save it, send the link, and your colleague opens exactly what you were looking at.
Writing a field, and undoing it
Field Report can also fill a field in — the same field, on many pages at once. It never does so without showing you the list first.
On the Write tab you pick a field and a value. Before anything is written you get the list of pages that would change, with a tick on each one, and the button counts what you have ticked: Write 12 pages. Untick a page and it is left alone.
Every page written gets a new version in Confluence, labelled Field Report <run> in the page history. A whole run can be undone from the Changes tab: each page goes back to the version it had, and the history records Undo of Field Report <run>. Nothing is overwritten in place and nothing is deleted.
The table macro and the page card
Type /Field Report in a page to put a filtered table inside it. You choose the scope — a space, a page tree or a label — and which fields become columns. The table is rebuilt from the index every time the page is viewed, so it does not go stale, and it carries a search box and a CSV download of its own.
Under the title of every page there is also a small Field Report card: what the index knows about this page, and a way into the board filtered to it.
Export
Export CSV gives you exactly what is on screen — the same columns, the same rows, in the same order. The file is UTF-8 with a byte-order mark, so accented characters open correctly in Excel.
Permissions and data
The app runs entirely on Atlassian's Forge platform. No page content, no name and no identifier ever leaves Atlassian. There is no server of ours to send it to: the app makes no request to any address outside your Atlassian site, which is what the “Runs on Atlassian” badge on the Marketplace listing certifies.
It asks Confluence for exactly these permissions, and Confluence shows you the list before you install:
| Permission | What it is for |
|---|---|
| read:page | Reading the pages the index is built from |
| read:content-details | Page versions, and the names behind mentions |
| search | Finding which pages moved since the last pass |
| read:space | The list of spaces you pick a scope from |
| write:page | Writing a field you approved on the preview |
| write:content | Restoring a version when you undo a run |
| read:confluence-content.summary · write:confluence-content | Required by Confluence to subscribe to page events; they add no power beyond the rows above |
There is no permission to delete anything — not a page, not an attachment, not a space. That is not a promise, it is a list you can check yourself at install time.
Everything the app does, it does as you: it can never show you a value from a page you could not open yourself in Confluence.
Privacy policy
Nothing you have in Confluence leaves Atlassian. The app runs on Atlassian Forge. It makes no request to any host outside your Atlassian site, so there is no third party, no analytics service and no server of ours that could receive your data. This is enforced by the platform, not by our good intentions: a Forge app that egresses data must declare it, and this one declares none.
No AI model is used. The app declares no language model and sends nothing to one.
What is stored, and where. The app keeps an index of your pages — page identifiers, titles, spaces, versions, and the field names and values it found — inside Forge SQL storage, which lives in Atlassian's own infrastructure under your installation. That index is what makes the board, the macro and the export possible. Page bodies are read into memory while a page is being indexed and are not kept.
What is not stored. No attachments, no credentials, no e-mail addresses beyond those you wrote into your own pages and asked the app to report on. The app never builds a profile of anyone.
Who can see it. The app acts as the person using it: before anything is shown, it checks that person can open the page it came from. We, as the developer, have no way to read your data — there is no admin console on our side and no copy anywhere else.
Deletion. Uninstalling the app empties its index immediately, on the way out. Forge would otherwise keep an uninstalled app's storage in soft deletion for a while; the app does not rely on that, it clears the tables itself.
Questions about any of this: contact@maste.ro.
Limits
- No pivot. Grouping by one field and totalling another is supported; two axes at once is not. Two axes stop being a list you can click back out of, and clicking back into the pages is the point of the app.
- The index is a snapshot between passes. Page events keep it close to live, and the hourly pass catches what events miss; a page changed seconds ago may take a moment to appear.
- Not covered in this version: attachments, page restrictions and drafts.
- Writing is one field at a time, always through the preview, always undoable as a whole run.
Support
Write to contact@maste.ro — a problem, a question, or a feature you need. The same address is on every failure message in the app, next to a short code. Tell us what you were doing, what you saw, and the code if there was one.