Runs on Atlassian

Specify what to build.
Document what you have.

All naturally in one simple flow — inside Confluence.

Install CapMap See how it works

Most analysis teams write change specs purely for development — and lose track of what the product actually does. One-off change documents quickly become a pile of outdated, unusable artifacts.

CapMap solves this naturally: you maintain a complete specification of product features and their technical design — all versioned per release, always current. Tools including diff between versions automatically show what changed; Jira integration creates tickets for developers. Zero extra effort — one flow, one data source, two views: living product documentation and change specs for development.

How It Works

CapMap connects business needs to implementation through a release-driven flow with full traceability.

Scoped per release R1

Requirements

Business needs targeting a specific release. Each requirement creates impacts that drive new versions.

impacts
impacts
Versioned per release R1 R2 R3

Features

Product capabilities by product & area. New version per release captures what changed.

depends on
depends on

Components

Technical blocks with APIs, data models & sequences. Versioned per release.

Reusable catalog
Artifacts Reusable rules and standards — account number formats, address display rules, validation patterns, and other cross-cutting specifications.

Requirements target releases and create impacts that drive new versions of Features and Components — full traceability from business needs to implementation.

Built for Product Teams

Everything you need to specify, document, and trace your product — right inside Confluence.

Version History & Diff

Track feature evolution across releases. Compare any two versions side by side with a rich diff view to see exactly what changed.

Release Planning

Plan work in release-scoped swimlane boards. Publish releases and promote items to production in one click.

Impact Traceability

From a single requirement, trace every affected feature, component and API version. Nothing gets lost.

API Schema Editor

Define request/response structures visually with data types and cardinality, or import existing OpenAPI specs.

OpenAPI & Excel Export

Export API schemas as OpenAPI 3.0 YAML or structured Excel workbooks. Attachments auto-sync to Confluence pages.

Embeddable Macros

Embed issue cards, filtered lists, and link maps into any Confluence page. Content stays in sync automatically.

Status Workflows

Configurable lifecycle per issue type — draft, analysis, review, approved, production. Visual workflow map included.

Jira Integration

Create Jira tasks from status transitions, link CapMap items to Jira issues, and sync progress across both tools.

Secure by design. Built for enterprise.

CapMap is a Forge-native app — runs entirely within Atlassian's sandbox with no external servers and no data egress.

Get it on Marketplace
Runs on Atlassian
No data egress
Data residency
GDPR compliant