Skip to main content
addly

Configure and verify Portfolio Insights.

Demonstration documentation for Jira · Project page. It describes the expected product contract, not an installation available on the Marketplace.

View the demo

Overview

A project view connects day-to-day progress with a portfolio reading without exporting Jira to a separate table.

Audience
Program leads, PMOs, and product leaders
State
Interactive concept, not published

Before installation

  • 01Confirm that Jira Cloud and the Project page placement match the need.
  • 02Identify the administrator responsible for configuration.
  • 03Review the intended permissions and data flow.
  • 04Choose a test project or space with no sensitive data.
  • 05Define the critical path and expected result.

Install

No installation is available. The future guide must start from the official Marketplace listing, verify the vendor identity, show the requested permissions, and confirm the target Atlassian site.
  1. 1Open the official listing linked from the product page.
  2. 2Review hosting, version, permissions, and the data policy.
  3. 3Install on an authorized test site.
  4. 4Verify that the surface appears in the expected context.

Configure

Configuration should start small and produce an observable result. The following settings are illustrative and must be replaced by the real schema.

{
  "surface": "Project page",
  "scope": "test-project",
  "mode": "preview",
  "data": "demonstration-only"
}

Preview mode should let the result be verified before broad activation.

Permissions and data

Intended permissions

  • 01Read selected projects
  • 02Read related issues and links
  • 03Write only view preferences

Data state

  • 01Fictional indicators
  • 02Calculations run locally in the prototype
  • 03No customer history is collected

Verification

Interact with the critical path without leaving the documentation. First observe the initial state, trigger the primary action, then verify that the feedback explains what changed.

WALKTHROUGH 01Instruction → interaction → expected state → limitation to record

addly Portfolio

Delivery health

ON TRACK12active items
NEEDS ATTENTION4active items
BLOCKED2active items

Demonstration data · Controls rendered with official Atlaskit components.

Checks to record

  • 01The surface appears in the simulated product and context.
  • 02Use only exposed controls and record every observable state change.
  • 03Verify that the primary action produces the visible feedback described in the demo.
  • 04Empty, insufficient-permission, and recoverable-error states cannot be manipulated here: record them as blocked evidence required before publication.
  • 05Deactivation and uninstallation cannot be manipulated here: treat them as documentary controls that still need confirmation.

Limitations

  • 01Host edition or release: No tested edition or release recorded
  • 02Distributed app version: No app version is distributed
  • 03Latest compatibility verification: Never — no versioned build exists to test
  • 04Technical support status: Unverified — no supported host or app version range

Any item marked ‘concept’, ‘intended’, ‘simulated’, or ‘pending validation’ must not be used as purchase evidence.

Compatibility registry

Documentation does not replace publication facts.

Before launch, every section will be aligned with the real manifest, listing, hosting, tests, and channels.

Back to the app