Skip to main content
addly

Build an explainable release review

Move three fictional criteria to a READY verdict, then retain the observation and limitation that shape your decision. This quick start covers an interface and demonstration data: it is not an installation, a compatibility test, or Marketplace evidence.

Prepare the testOpen the lab
Jira · Issue panel8 to 12 minutes

Expected output

An exportable observation, not an automatic score.

Reset restores the fictional preset. Your observation and verdict stay local until you explicitly copy them.

What you will build

Release review

Move three fictional criteria to a READY verdict, then retain the observation and limitation that shape your decision.

Read product limitations

Prerequisites before you click

  • A real release scenario to compare, without copying sensitive data into the demo.
  • The person who can confirm the criteria and stop condition.
  • Your own definition of ‘ready’; the demo does not replace your governance.
  • No account, Jira site, or installation: this lab uses fictional data only.

The initial preset is documented and restorable.

You know exactly what is already displayed before the action. ‘Reset all’ restores those values without retaining your trials.

  1. STATE 01

    Two of three criteria are selected and progress shows 67%.

  2. STATE 02

    The rollback plan is incomplete; the verdict shows IN REVIEW.

  3. STATE 03

    Verdict details are closed and no data is sent.

One action, one expected result, no decorative step.

Instructions use only controls present in the demo. If a behavior is not interactive, it appears below as blocked evidence.

  1. 01

    Read the source of the verdict

    Find the unchecked criterion, the 2 of 3 count, and the IN REVIEW lozenge in the simulated Jira panel.

    Expected result

    The initial verdict can be explained without inferring a hidden rule.

  2. 02

    Change one criterion

    Clear and then select ‘Success measure defined’ and watch the percentage.

    Expected result

    The count and bar immediately follow the criteria that are actually selected.

  3. 03

    Reach the ready state

    Select the rollback plan or activate ‘Complete review’.

    Expected result

    The panel shows 100%, three of three criteria, and a READY verdict.

  4. 04

    Verify and record

    Open ‘View details’, note what matches your process, and choose a local verdict below the demo.

    Expected result

    The message explains the state and the Markdown result separates observation, verdict, and prototype scope.

lab Jira

Use the preset, then keep the trace.

The guide does not monitor your clicks; it tells you what to observe. Reset, observation, verdict, and Markdown export remain under your control.

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.

Verification recipe

‘Blocked’ means this demo cannot produce the evidence. It means neither failure nor compliance of the future product.

Interactive

Progress and count

Interactive by selecting or clearing each of the three criteria.

Interactive

IN REVIEW to READY transition

Interactive when the third criterion becomes true.

Interactive

Verdict explanation

Interactive through the View details action.

Blocked evidence

Empty, insufficient-permission, and recoverable-error states

Absent from this prototype; record them as blocked evidence, never as passed tests.

Troubleshooting and limitations

The first diagnostic separates a misunderstood local action from a capability that simply does not exist in the showcase.

The verdict does not change to READY. What should I check?

All three boxes must be selected. Use Reset all to restore the exact initial 2 of 3 state.

Can I test my Jira workflow or fields?

No. The demo validates only the visible interaction. The real workflow, configuration, manifest, and permissions remain blocked evidence before publication.

How do I keep the result?

Enter the observation and local verdict, then copy the Markdown. Add that trace to the evaluation room with the other evidence.

This quick start tests a concept in the browser. Before a pilot, require a real listing, manifest, compatibility, permissions, data processing, contract, and support channel.

Open the shareable datasheet

The quick start ends with a traceable decision.

Add the exported observation to the packet, assign the blocked evidence, and decide whether to continue, ask, pause, or reject.

Open the evaluation packetReturn to all four quick starts