Skip to content
← Readiness Map

Release notes

What's new in Readiness Map

Every release, newest first. We follow semantic versioning and keep changes grouped so you can scan what matters to you.

  1. v3.4.0

    October 31, 2026

    Routing fix for connections that step upward across stages.

    Fixed
    • Connections that route upward between stages now draw cleanly instead of overlapping the boxes they pass.
  2. v3.3.0

    October 31, 2026

    Map rendering, layout, and drag-and-drop improvements (consolidating the 3.1–3.2 refinements).

    Changed
    • Smoother, more predictable drag-and-drop when arranging components.
    • Cleaner layout and connection routing across stages.
    Fixed
    • Several edge cases in how rows and connections were placed on dense maps.
  3. v3.0.0

    October 1, 2026

    Richer Jira context and a generic, configurable core.

    Added
    • Jira user context, so a component can show who owns it.
    • Configurable vocabulary — rename components, maps, and columns to match your organization.
  4. v2.1.0

    October 12, 2026

    Zero data egress — the app stopped talking to the outside world.

    Security
    • Removed all external network access. Readiness Map is now fully Forge-native with zero data egress, and eligible for Atlassian's “Runs on Atlassian” program — your data never leaves Atlassian.
  5. v1.0.0

    September 20, 2026

    First release.

    Added
    • A registry-backed readiness map inside Jira: components as records (ID, stage, and provenance), a map view generated from the record, and read-only Jira access.