Skip to main content
addly
Jira · Project pageConcept to evaluate

Portfolio InsightsRead risks, decisions, and dependencies at project level.

A project view connects day-to-day progress with a portfolio perspective without exporting Jira into a separate dashboard.

Guided demonstration

Test a realistic scenario, then preserve the record.

The guide remains separate from the hero so the demonstration, instructions, and report have room to work as a complete evaluation space.

Guided demonstration journey

The steps direct observation; they do not automatically detect your actions.

Step 1 of 333% of the guide displayed

Compare the three views

Move through the Overview, Risks, and Decisions tabs in the simulated Jira project page.

Observe: Each tab exposes only the summary defined by the demonstration; no additional project detail is being tested.

addly Portfolio

Delivery health

ON TRACK12active items
NEEDS ATTENTION4active items
BLOCKED2active items

Demonstration data · Controls rendered with official Atlaskit components.

Record the local result

These notes stay on this page and are not sent to any service.

0/1,200

Local verdict

Step 1 of 3: Compare the three views.

Demonstration interface and data. Host-product controls are rendered with Atlaskit; no app is installed.

Host product
Jira
App placement
Project page
Primary audience
Program leads, PMOs, and product leaders
Commercial state
Marketplace listing to connect

The moments when this app earns its place.

Every use case begins with an observable friction, then shows the expected change without promising an unmeasured result.

01

Portfolio review

Compare initiative health using consistent indicators.

02

Capacity trade-off

Spot dependencies that shift a target date.

03

Steering review

Share a summary linked directly to Jira issues.

What the team sees. What it can explain.

A feature is credible only when its state, source, and next action remain readable.

01

Explained health

Indicators point to the underlying risks and decisions.

02

Visible dependencies

Critical links appear before they turn into delays.

03

Project narrative

The summary connects figures, decisions, and the next step.

Compatibility

Distributed app version
No app version is distributed
Latest compatibility verification
Never — no versioned build exists to test
Technical support status
Unverified — no supported host or app version range
View the matrix

Permissions required

  • Read selected projects
  • Read associated issues and links
  • Write only to view preferences
Examine security

Data handling

  • Illustrative indicators
  • Calculations run locally in the prototype
  • No customer history collected
Trace the flow

Evidence follows the app, not the sales pitch.

The trust profile separates verifiable facts, expected controls, and material still to produce for this concept. It implies no certification or availability.

Open the trust profile

Official pricing will remain in the right place.

Until the app is published, we display neither a plan nor a commercial estimate. The Pricing page explains the licensing model and will link to the official Atlassian Marketplace calculator.

Understand licensing

Questions to resolve before installation.

These questions are specific to the concept. The published version must align with the real manifest, hosting model, and limitations.

Does this view replace Advanced Roadmaps?

No. The concept complements an operational view in Jira; the Comparisons page explains when the native feature is sufficient.

Can the scores be configured?

The intent is to make every rule visible and configurable, never to produce an opaque score.

Can visibility be restricted?

A real version must respect Jira permissions and explain exactly how access to aggregated projects works.

The final step must lead to the official listing.

This product is still a demonstration: no Marketplace link, price, review, or installation is invented. Until an official URL exists, the pilot-access brief remains locally copyable and can be submitted only when compliant data collection is enabled.