Portfolio review
Compare initiative health using consistent indicators.
A product datasheet buyers can share without rewriting the story.
Portfolio Insights brings together its scenario, Atlassian surface, compatibility, permissions, data, limitations, and verification links. Its concept status stays visible in print and exports.
Concept datasheet
Printable and exportable
No price, customer, review, installation, or badge is added to make this datasheet look artificially commercial.
Jira · Project page
Portfolio Insights
Read risks, decisions, and dependencies at project level.
- Host product
- Jira
- App surface
- Project page
- Audience
- Program leads, PMOs, and product leaders
- Status
- Concept · unpublished
Problem, use cases, and observable capability.
A project view connects day-to-day progress with a portfolio perspective without exporting Jira into a separate dashboard.
Capacity trade-off
Spot dependencies that shift a target date.
Steering review
Share a summary linked directly to Jira issues.
Expected outcome
Read risks, decisions, and dependencies at project level.
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
Portfolio Insights
Read risks, decisions, and dependencies across the project.
Evidence status: Absent before launch
- Product state
- Concept only — not published or distributed
- Concept revision
- 0.4
- 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 project page 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.
- Record owner
- Product owner to assign before launch
- Record reviewed
- Stable record ID
- compatibility:portfolio-insights:concept-0.4
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.
Portfolio Insights 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 launchEvery 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 selected projects · Read links and dependencies · Save view preferences
- Intended Forge surfaceAbsent before launch
The placement is named; its distributed implementation is absent.
Jira project page concept — no published module manifest
- Processing, storage, and egressNeeds confirmation
Each data category keeps its unresolved boundaries attached.
Selected Jira project data · Portfolio preferences
- Intended return and deletionNeeds confirmation
The expected purpose is visible; production deletion still needs confirmation.
Selected Jira project data · Portfolio preferences
Local demonstration · inspectable now
AvailableThe 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
- Deletion
- Demo reset or session close
- Execution location
- Viewer’s browser
Owner: addly showcase owner · Reviewed: · Inspect
Host context
Needs confirmation
Read selected projects
- Intended scope
- Projects, issues, and fields the person can already view
Read links and dependencies
- Intended scope
- Visible relationships among issues in selected projects
Save view preferences
- Intended scope
- App-owned filters and presentation
- Source
- Read selected projects
- Owner
- Product owner to designate before launch
- Reviewed
Intended Forge surface
Absent before launch
Jira project page concept — no published module manifest
- Product truth
- Concept only — not published or distributed
- Distribution
- No package, Marketplace listing, or installation channel
- Verification environment
- No compatibility test environment recorded
- Source
- Product source
- Trust source
- Owner
- Product owner to assign before launch
- Reviewed
Processing, storage, and egress
Needs confirmation
Selected Jira project data
- Purpose
- Connect health, risks, decisions, and dependencies
- Storage
- Production architecture to be defined
- Egress
- To be confirmed with the published architecture and manifest
Portfolio preferences
- Purpose
- Keep the view configured by the person
- Storage
- Planned app storage; architecture not finalized
- Egress
- No production recipient defined
- Source
- Selected Jira project data
- Owner
- Product owner to designate before launch
- Reviewed
Intended return and deletion
Needs confirmation
Selected Jira project data
- Intended result or purpose
- Connect health, risks, decisions, and dependencies
- Deletion
- To be defined when removing a project and uninstalling
Portfolio preferences
- Intended result or purpose
- Keep the view configured by the person
- Deletion
- Reset and uninstall need specification
- Source
- Selected Jira project data
- Owner
- Product owner to designate before launch
- Reviewed
Permission intents
- 01Read selected projects
- 02Read associated issues and links
- 03Write only to view preferences
Data and limitations
- 01Illustrative indicators
- 02Calculations run locally in the prototype
- 03No customer history collected
Every statement keeps a path to verification.
The demo shows the nominal behavior. Documentation, trust evidence, and known limitations cover what this datasheet alone cannot prove.
A shareable datasheet never replaces the source.
Use it to guide internal review, then open the demo, documentation, and evidence links before making a decision.