QC Traceability Is Now on Forge — With More Features for Confluence Cloud

QC Traceability Is Now on Forge — With More Features for Confluence Cloud

Published on 18 August, 2026 by Evangelos MantadakisEvangelos Mantadakis

QC Traceability for Confluence Cloud now runs on Atlassian Forge. This is the next version of the same Marketplace app — not a separate product — and your existing projects, collections, items, page links, relationship types, and severity levels stay where they are.

The Forge release is also a feature release. Teams can now place live traceability reports on Confluence pages, export tables from the browser, share deep links into Site Overview, and work with a richer Page Overview, diagrams, and history.

Why we moved to Forge

Forge is Atlassian’s current Cloud platform for marketplace apps. Moving QC Traceability onto it keeps the product aligned with Atlassian’s security, performance, and long-term Cloud support — the same path we have already taken for other QC apps.

What does not change:

  • You still install QC Traceability for Confluence Cloud from the Atlassian Marketplace.
  • Existing site data is unchanged.
  • The familiar workflow remains: projects, collections, items (Confluence pages or external links), relationship types, and page links.

What does change is how much of that workflow you can show, share, and export without leaving Confluence.

What’s new in this version

QC Traceability Macro — insert reports on any page

Connect never had a macro. The Forge version does.

Insert QC Traceability Macro on a Confluence page and choose Page or Project:

  • Page: a table of links for a selected page, or the current page if you leave that field empty. Optionally show the page traceability diagram.
  • Project: Overview, Detailed, or Traceability Matrix. Overview and Detailed can also show the project diagram.
  • Readers see the same saved configuration after you publish. Search, pagination, and table export stay available at view time.

This is the fastest way to put a live trace matrix or page-link table next to the requirements, design, or test content your team already writes in Confluence.

Richer diagrams, including the project V-model

Traceability is easier to defend when people can see the links.

  • The content byline still opens a Page Traceability Diagram for the current page.
  • Page Overview groups first-degree linked items by collection, with a legend for this page, upstream, and downstream.
  • Each project can show a V-model diagram. Place collections on the left (design), right (verification), or bottom (implementation). Click a collection node to open that collection’s detailed report.

Export from the table toolbar

List tables, reports, the trace matrix, statistics, Page Overview, and macros now export from the table toolbar. Choose CSV, Excel, PDF, or Word. The file matches the rows you currently see (including search and filters). PDF and Word include a title and page numbers.

That makes it straightforward to attach a matrix or item list to an audit pack without rebuilding the table in a spreadsheet.

Page Overview that helps you build the next link

Page Overview is still the place to manage links for the current Confluence page. In the Forge version it also:

  • Lets you Add upstream or Add downstream with a live diagram preview of source → relationship → target.
  • Searches Confluence pages or Jira / web links in a nested picker (Jira search needs the app Connected to Jira in Atlassian Administration).
  • Shows this page item’s collections and severity, and warns when a Required project rule is still missing.
  • Adds a History tab for link and collection changes on that page.

Archived items stay read-only, so completed work is not edited by accident.

Site Overview: shareable URLs, history, and a change log

QC - Traceability Overview (from the Confluence Apps menu) still covers Projects, Collections, Items, and Settings. You can now:

  • Share a URL that opens a specific project, collection, settings, history, or change log view.
  • Use site-wide and project History tables as an audit trail of important Trace actions.
  • Filter items and reports by severity, and see the level under each item title.
  • Read product updates in the in-app Change Log.

What existing users should do

If QC Traceability is already installed, upgrade to the latest version from the Atlassian Marketplace or Apps → Manage apps in Confluence.

You do not re-create projects or re-import pages. After the upgrade, look for the new QC Traceability Macro when you insert a macro on a page, and use the table Export menu wherever you already open reports.

New teams can still start a free trial from the Marketplace.

How to get started

  1. Install or upgrade QC Traceability for Confluence Cloud.
  2. Open QC - Traceability from the Apps menu to review projects, collections, and items.
  3. On a requirements or design page, open QC - Traceability Page Overview to add upstream and downstream links.
  4. Insert QC Traceability Macro where stakeholders should see a live table or diagram.

For product context and use cases, see our QC Traceability product page and the original launch article, Introducing QC Traceability.

Need a walkthrough? Book a meeting or contact [email protected].