Your first
rehearsal.

Start with synthetic records.

1. Install in a test Jira Cloud site.

   Open the evaluation installation link above as a site administrator. Check the app name LotZero-Judge, provider and privacy policy. Select your site and review the requested Jira issue-read, issue-write and app-storage access before installing.

2. Open LotZero from a Jira project.

   Use a test project with a standard Task type. Open its LotZero page, then select Load synthetic dataset as a project administrator. The fictional Northstar dataset has 37 records and 43 relationships. Keep drill tasks away from automations that could trigger operational actions.

3. Define the scenario.

   Choose New drill, source lot ING-A19, contamination and effective time 2026-10-28T09:00:00Z. Run the trace. These are the bundled fixture’s expected results:

   Product lots

   3

   Shipments

   4

   Evidence gaps

   9

   Unresolved records

   12

4. Inspect evidence, then rehearse a control.

   In Impact explorer, select SHIP-002. Inspect its missing destination and the path ING-A19 → BATCH-101 → FG-101 → SHIP-002. Review failed and unknown assertions. In Intervention simulator, try a hypothetical WH-NORTH quarantine at the scenario time with evidence EV-DRILL. Future SHIP-002 is potentially preventable; historical SHIP-001 remains in the impact.

5. Save the rehearsal. Review any follow-up.

   Save the drill to retain its dataset, scenario and evidence. Jira suggestions begin unselected. If you want a real follow-up Task, review its target project and description, select only the intended suggestion and explicitly approve creation. The returned Jira receipt records the outcome. A rehearsal never holds a real shipment or contacts a customer.

A documented association is not proof of contamination. PASS, FAIL and UNKNOWN describe the supplied records and configured tests. LotZero does not determine food safety, certify compliance or direct a real recall.

Keep the evidence.

Reopen a saved rehearsal after reloading Jira. Its report includes the scenario, full dataset snapshot, findings, assertions, simulated controls and approved Jira receipts. Export Markdown or JSON, or use CSV for tabular findings.

If a download does not appear, expand View or copy export, choose the format and use Copy export, then paste into a local editor and save. Exact native clipboard contents have been verified for all three formats. Automatic file downloads inside native Jira remain unverified.

Exports can contain the full imported dataset and account identifiers. Review the contents and your intended recipients before sharing them. Corrected records can be imported and rerun against the same source and hazard to compare saved rehearsals.

When a step needs attention.

Permission denied

Ask your Jira administrator for the specific permission shown. Reading and saving drills require project Browse access; importing or deleting data requires project administration. Creating a Task also requires the target project’s Create Issues permission.

Import rejected

Use validated JSON or the documented record_type,json CSV envelope shown under Import format & limits. Arbitrary spreadsheet columns are not mapped automatically. The import limit is 200 KB; rejected data does not replace current records.

Jira requires additional fields

Choose a non-subtask Task type with description and labels enabled, and defaults for any other required fields. Review the target project’s workflow and automation before approving a drill Task.

A Jira creation result is uncertain

Do not blindly repeat creation or delete its receipt. Preserve the displayed action marker. Check Jira for that marker, inspect any matching issue, then ask a source-project administrator to use Verify existing issue. Check saved receipt returns an existing receipt and refuses to recreate a missing one.

The dataset changed or snapshot history is full

Rerun after a dataset-change warning. The current version keeps up to 25 Forge snapshots per project. Export what you need before considering a confirmed project-data reset.

Know what stays.

LotZero uses Forge-hosted storage. Imports and free-text fields may contain personal or commercially sensitive data. Snapshots and audit records include Atlassian account identifiers. Start with synthetic data and review project access before importing your own records.

• Dataset and action receipts: retained until replaced or explicitly reset, as applicable. Receipts and action claims help prevent duplicate Jira writes.
• Snapshots and audit history: request a 90-day storage TTL. Provider deletion is asynchronous and may take up to 48 additional hours; deletion at exactly 90 days is not promised.
• Project-data deletion: a project administrator can open Activity & data controls → Delete LotZero workspace data, type DELETE and confirm. Export first. Uncertain Jira outcomes must be reconciled before reset.
• Independent copies: deleting app data does not delete Jira issues or downloaded reports. Jira and provider backup retention apply separately. There is no automated individual-account erasure workflow.

See the privacy policy for processing details and how to make access, correction or deletion requests.

Bring the question.
Keep the secrets.

For installation, technical support or privacy requests, contact Himanshu Jha / LotZero. Include the app screen, what you expected, the error message and whether you used synthetic records. Redact any screenshot before sharing it.

GUIDE UPDATED / 30 OCTOBER 2026