List view
JIM's step-change from identity synchronisation into identity governance. This milestone introduces direct management of metaverse objects within the UI, entitlement visibility and mapping, access request workflows, and basic attestation capabilities. Establishes the governance layer that enables compliance-driven organisations to manage access holistically, not just synchronise it.
No due date•0/5 issues closedExpanding the range of connected systems JIM can synchronise with. Each minor release adds support for additional connectors (Broader LDAP support, SQL databases, SCIM endpoints, HR systems, Entra ID, etc.) along with any connector framework improvements identified during v1.0 usage. Operational polish and community-driven enhancements also land here.
No due date•0/11 issues closedThe first production-ready release of JIM. All core identity lifecycle management capabilities are present: robust sync rules, identity fusing, lifecycle automation, scheduling, error handling, and operational monitoring. This is the release where JIM is ready for production environments.
No due date•1/49 issues closedMaturing the platform from MVP to production-ready. This milestone covers completing missing configuration controls, identity fusing logic, lifecycle state management (joiner/mover/leaver triggers), and hardening the core sync pipeline. The sync engine internals are refined to extract a clean domain engine with optimised data access patterns, establishing the architectural foundation needed for connector extensibility and the IGA capabilities planned in v2.0. The goal is a stable, fully configurable ILM engine ready for real-world deployment.
No due date•24/37 issues closedFeatures and improvements planned for after MVP release.
No due date•22/25 issues closed