Skip to main content
addly
Jira · Issue panelConcept to evaluate

Readiness for JiraDecide whether a release is ready without leaving the issue.

The panel brings criteria, blockers, and the next action together in the exact context where the team prepares its delivery.

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

Read the initial state

Find the IN REVIEW verdict, the percentage, and the remaining incomplete criterion in the simulated Jira panel.

Observe: The percentage and criterion count follow the boxes that are actually selected in this demonstration.

addly Readiness

Pre-release check

IN REVIEW
67%

2 of 3 criteria are ready

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: Read the initial state.

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

Host product
Jira
App placement
Issue panel
Primary audience
Release managers, product teams, and Jira administrators
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

Release review

Check critical criteria before moving the issue forward.

02

Handover

Make missing information visible to the next team.

03

Lightweight governance

Keep the decision readable without adding another meeting.

What the team sees. What it can explain.

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

01

Explainable verdict

Every state points back to the criteria that produced it.

02

Action in the flow

The next step remains available where the work happens.

03

Compact view

The main indicator stays visible without turning the issue into a dashboard.

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 issue context
  • Read configured fields
  • Write only to app-owned state
Examine security

Data handling

  • Demonstration data only
  • No remote service connected in this showcase
  • Retention to define before publication
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 the app change the Jira workflow?

The concept shown here does not require any change. A published version would document every optional automation or transition separately.

Can readiness criteria be configured?

That is the product intent: criteria would be configured per project, with a preview before activation.

Where can I find the exact permissions?

The product documentation and Data record must reflect the manifest that is actually published. The current material is a transparent prototype.

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.