{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T07:59:18.009Z",
  "record_id": "VXI-EXT-PROCUREMENT-JIRA-EXPORT-01-v1",
  "record_kind": "external_reference",
  "title": "Jira Cloud export: App data and automation need separate handling",
  "system": "Jira Cloud",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a Jira Cloud backup include third-party app data and automation configuration?",
  "near_questions": [
    "Does Jira backup include third-party app data?",
    "Are automation flows exported automatically?",
    "Which restore destination is intended?",
    "Are Cloud and Data Center formats interchangeable?",
    "What attachments were selected?",
    "Can cross-application links still point to the old site?",
    "Which credentials need reconfiguration?",
    "Are team-managed objects compatible with the destination?",
    "Does backup age affect restore eligibility?",
    "What was verified after import?",
    "When should an agent avoid promising complete migration?",
    "Can I save the Jira exit-evidence review?"
  ],
  "supported_claims": [
    {
      "claim": "The export guide excludes third-party apps and app data, and automation flows require their own export/import. Cloud and Data Center destinations have different compatibility constraints. A backup file therefore needs an inventory and target-specific restore evidence before it supports a full migration claim.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "The export guide excludes third-party apps and app data, and automation flows require their own export/import. Cloud and Data Center destinations have different compatibility constraints. A backup file therefore needs an inventory and target-specific restore evidence before it supports a full migration claim.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Jira Cloud data export",
    "source_url": "https://support.atlassian.com/jira-cloud-administration/docs/export-issues/",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-JIRA-EXPORT-01-v1",
    "candidate_record_sha256": "c2661460b9269eaf38f5467fb8f80a65a33e36b290b333481ecc9b7ad34ec23d",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "The export guide excludes third-party apps and app data, and automation flows require their own export/import. Cloud and Data Center destinations have different compatibility constraints. A backup file therefore needs an inventory and target-specific restore evidence before it supports a full migration claim.",
    "required_buyer_context": "Backup type, destination, app data, automation and restore eligibility. Effective buyer configuration and dated operational evidence are required.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-16",
    "claim_to_check": "The native backup captures the entire operational Jira environment.",
    "documented_statement": {
      "status": "documented",
      "statement": "The export guide excludes third-party apps and app data, and automation flows require their own export/import. Cloud and Data Center destinations have different compatibility constraints. A backup file therefore needs an inventory and target-specific restore evidence before it supports a full migration claim.",
      "source_ids": [
        "jira-export"
      ]
    },
    "buyer_evidence_required": [
      "Backup type and intended destination.",
      "App-data and automation export inventory.",
      "Restore validation and missing configuration list."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Require excluded-component evidence before approving migration completeness."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "jira-export",
        "url": "https://support.atlassian.com/jira-cloud-administration/docs/export-issues/",
        "final_url": "https://support.atlassian.com/jira-cloud-administration/docs/export-issues/",
        "title": "Jira Cloud data export",
        "checked_on": "2026-10-16",
        "sha256": "84227d9be1558837b42b8a435782965791df01fc431f62e61ebace09ce2471ee",
        "bytes": 484110
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "Preserve the excluded integrations and destination constraints behind a migration decision.",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Backup type, destination, app data, automation and restore eligibility"
    }
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#jira-backup-excluded-app-automation-data",
  "machine_readable_record": "/varexis-index/records/jira-backup-excluded-app-automation-data.json"
}