This profile connects actions, data, and evidence to the Readiness for Jira. concept. It shows what the showcase makes inspectable, what remains an intention, and what blocks any claim before launch.
A compatibility record that starts with what is not yet known.
Each app concept has a stable record for its intended host, proposed surface, distribution state, latest verification, degraded behavior, source, owner, and evidence status. Empty evidence stays explicit instead of becoming a compatibility claim.
Schema version
1
Registry reviewed
Current scope
1 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.
Readiness for Jira data path, with every unknown left visible.
This app-specific view separates the browser demonstration that can be inspected today from a production path that has not been distributed, tested, or approved. It is an evaluation aid, not a deployed architecture.
Production path · not validated
Absent before launch
Every production node is derived from the current permission, data, and compatibility registers. No hosting region, provider, scope identifier, storage service, recipient, or retention period is inferred.
Host contextNeeds confirmation
Jira access remains a functional intention.
Read issue context · Read readiness configuration · Save app state
Intended Forge surfaceAbsent before launch
The placement is named; its distributed implementation is absent.
Jira issue panel concept — no published module manifest
Processing, storage, and egressNeeds confirmation
Each data category keeps its unresolved boundaries attached.
Jira issue context · Readiness configuration
Intended return and deletionNeeds confirmation
The expected purpose is visible; production deletion still needs confirmation.
Jira issue context · Readiness configuration
Local demonstration · inspectable now
Available
The available path stays in the visitor’s browser.
This lane describes only the public showcase and its fictional dataset. It does not prove how a future Marketplace app will process customer data.
Input
Fictional dataset embedded in the public showcase
Purpose
Make the scenario interactive without customer data
Storage
Local demonstration-interface state
Egress
No remote product service connected in this showcase
Evidence source : Authorized issue and fields — product intent · Purpose : Calculate an explainable readiness state
Needs confirmation
Storage
Production architecture to be defined
Egress
To be confirmed with the published architecture and manifest
Retention
To be defined per field and app state
Deletion
To be defined for uninstall and issue deletion
Region
To be defined before any publication
Evidence source : public profile · Owner : Product owner to designate before launch · Review :
Readiness configuration
Evidence source : Criteria entered by an administrator — product intent · Purpose : Adapt the release review to the project
Needs confirmation
Storage
Planned app storage; architecture not finalized
Egress
No production recipient defined
Retention
To be defined according to the project lifecycle
Deletion
Administrator deletion and uninstall need specification
Region
To be defined before any publication
Evidence source : public profile · Owner : Product owner to designate before launch · Review :
Evidence exists only when its source opens.
Available describes an inspectable artifact now. Needs confirmation describes a model still to align. Absent before launch prevents any premature claim.
Interactive demonstration
Available
The surface and guided path can be inspected with explicitly fictional data.