Assign permanent, unique identifiers to any content item in Confluence. IDs never shift. References never break. Navigate directly to any item — inside the document.
Confluence has no native way to assign permanent, unique identifiers directly inside documents. As pages evolve, content becomes harder to track, reference, and verify — causing three specific problems.
Confluence heading and list numbers change automatically when content is added or deleted. Item 3.2 today becomes 4.2 tomorrow. Any reference to it — in a ticket, email, or another page — now points to the wrong thing.
Confluence supports anchors and heading links — so linking to a specific location is possible. To create reference in current page it requires switching to the target page, editing it, finding the location, adding and naming an anchor, copying the URL, save target page and returning to paste it. Across dozens of items this becomes slow, fragile, and hard to maintain.
Confluence Table of Contents provides a structured overview of page headings, but there is no native way to list, filter, or sort custom IDs or numbered items on a page. Jira can report issues through filters and queries, but cannot generate a report of items referenced within a specific Confluence page.
IDs survive page edits, content moves, and saves. REQ-12 always means REQ-12.
A built-in reference macro lets you navigates directly to the ID on referenced page, scrolls to it, and highlights it with a confirmation flag.
A built-in report macro lists all ID on any page — filterable, sortable, searchable — without leaving Confluence.
Any editor can define new prefixes and numbering schemes directly on a page — no Jira projects to create correct prefixes, no admin to contact, no waiting. REQ, TC, RISK, API, TASK — all on one page, set up in seconds.
The core macro. Placed inline on a Confluence page to mark any content / item with a permanent, unique identifier.
A reference macro that creates a live, navigable link to any Num ID — on the same page or a different one.
A reporting macro displaying a structured, interactive list of all Num IDs on any specified page.
| Feature | Confluence | Jira issues in Confluence | Numbering App for Confluence |
|---|---|---|---|
| Stable ID | May shift | Permanent | Permanent |
| Custom prefix (REQ, TC, SEC…) | Numbers only | Requires Jira project | Per page |
| Multiple prefixes on one page | Not native | Requires Jira projects | Native support |
| Link to exact ID/item across pages | Manual anchor setup | Opens Jira, not page | Easy link + exact landing |
| Broken reference notification | Not native | Not native | Flagged in macro |
| List all IDs on a page | Headings only | Not page-native | Instant — Num Report |
| Ready to use immediately | Any editor | Admin required | Any editor |
Any team that needs stable, referenceable identifiers inside Confluence documents — not just business analysis teams.
Stable REQ IDs that survive the entire project lifecycle — from inception through testing and sign-off.
Write detailed test cases directly in Confluence — each marked with a stable TC ID.
Label API endpoints, interface contracts, and technical design decisions with stable identifiers for unambiguous technical blueprints.
Clause and audit checkpoint numbering that stays stable during multi-party negotiations and regulatory reviews.
Assign permanent reference numbers to SOPs so teams can cite exactly which procedure version was followed.
Track risks with stable RISK IDs across project phases — reference them in decisions, mitigations, and reports.
Built on Atlassian Forge. Your data never leaves Atlassian Cloud.
Inherits Atlassian's security, compliance and data residency standards.
Designed by analysts and architects who have lived this problem on real enterprise projects.