It describes a host version, placement, required data, limitations, and test evidence. This versioned register distinguishes what is demonstrated from what still needs validation.
Host + version + surface + permissions + degraded behavior + date of the latest test.
A registry the administrator can audit.
Four stable records expose the intended Cloud context and proposed module while keeping host release, distributed app version, test date, environment, result, and degraded mode explicitly unverified.
Schema version
1
Registry reviewed
Current scope
4 app concepts · no distributed versions
Compatibility record
Readiness for Jira
Decide whether a release is ready without leaving the issue.
Evidence status: Absent before launch
Product state
Concept only — not published or distributed
Concept revision
0.3
Intended host channel
Jira · Cloud target only — not a tested compatibility statement
Host edition or release
No tested edition or release recorded
Proposed surface or module
Jira issue panel concept — no published module manifest
Distributed app version
No app version is distributed
Distribution channel
No package, Marketplace listing, or installation channel
Latest compatibility verification
Never — no versioned build exists to test
Verification result
Not tested
Technical support status
Unverified — no supported host or app version range
Test environment
No compatibility test environment recorded
Degraded behavior
Not defined. It must be implemented and tested for each distributed version before launch.
This register inventories product intent and missing verification evidence. It does not prove Marketplace availability, Atlassian approval, a Forge manifest, supported scopes, or compatibility with any host release.
An integration must explain its failure.
Good catalogs show what connects. A stronger page also shows what happens when that connection stops responding.
Connection
Authentication, scope, and owner of the app configuration.
Permission state
Minimum read or write access required for each action.
Synchronization
Direction, frequency, conflict, and source of truth.
Degraded mode
Visible state, recovery, and data retained after failure.
Verify compatibility at action level.
Choose an app, open its documentation, and check permissions, required data, and expected behavior before installation.