Decision Register for Jira FAQ

What is a Decision Register?

A Decision Register is a structured record of project decisions, rationale, owners, and timing so teams can audit delivery history without searching across multiple tools.

Who is it for?

Works with Jira Cloud projects where the app has the required access; validate compatibility in your site.

Where is data stored and what are tenancy boundaries?

The app is Forge-only and runs on Atlassian infrastructure. Data used for generation comes from Jira Cloud, and limited app state can be stored in Forge storage:app.

There is no external backend or external network egress for this app, so data remains within Atlassian tenancy boundaries.

How does permissions and access control work?

• Uses Forge scopes read:jira-work and storage:app.
• Who can view, generate, or export depends on Jira site/project access and admin installation choices.

What export options are available?

Current export support is CSV from the generated register view, with a copy-to-clipboard fallback when direct download is unavailable. If you need additional export formats, contact support with your use case.

What does it detect and how does it handle limits?

• Detects estimate, priority, scope/sprint, reopen, assignee, due date, and fix version changes.
• Retries Jira API calls on rate limits and server errors.
• Shows warnings when results are partial or limited.

Free vs paid

Pricing packaging is planned. Free and paid tiers may be offered, and final limits will be published on the Marketplace listing.

Security and compliance posture