Paperless-ngx vs Jira
Side-by-side trajectory, velocity, and editorial themes.
Paperless-ngx is rebuilding for v3 with AI, a plugin framework, and a Tantivy search rewrite.
Two release lines run in parallel. The v2.20.x stable branch is in aggressive security-patch mode — five GHSA-tagged security releases in roughly two months (v2.20.7, 2.20.8, 2.20.9, 2.20.12, 2.20.15) plus a stream of permission-scope and workflow bug fixes. Meanwhile, v3.0.0-beta.rc1 just dropped with the largest feature surface in the project's history: Paperless AI, Remote OCR via Azure AI, sharelink bundles, document file versions, a document parser plugin framework, and a swap of the Whoosh search backend for Tantivy. The v3 cut also lands eleven explicit breaking changes — old API versions removed, encryption support dropped, Python 3.10 support cut, OCR control decoupled from archive-file control.
The arc is a generational rewrite landing on top of a hardened v2 foundation. The team is using v2.20.x to absorb security disclosures (often credited to community researchers) while v3 takes on the architectural debt — fresh migrations from scratch, removed legacy paths, a search engine swap, and a plugin framework that opens the parser surface to extensions. The simultaneous Paperless AI and Azure AI Remote OCR features signal a deliberate move into AI-augmented document processing rather than a passive integration.
Expect more v2.20.x security and bugfix releases through the v3 beta period, then a coordinated migration push when v3 stabilizes — Tantivy reindexing and the API-version removals will both gate that upgrade. Watch the next v3 beta for what Paperless AI actually exposes (suggestion-only vs auto-classification) and whether the plugin framework gets a public extension point doc.
Atlassian is quietly turning Jira into the connective tissue for an AI-driven enterprise work platform.
Jira keeps shipping along two tracks at once. One is enterprise lifecycle plumbing — sandbox-to-production config promotion, guest access on paid plans, multi-space service queues — that closes long-standing change-management and collaboration gaps. The other is platform expansion: HRIS data flowing into the Atlassian Teamwork Graph, Rovo skills landing inside Jira Align, and Bitbucket merge queues.
The center of gravity is moving from issue tracking to a unified work platform with AI on top of an enriching Teamwork Graph. Atlassian is treating the Graph as the substrate Rovo reasons over, and is now feeding it HRIS data — well beyond traditional Jira scope. Enterprise-grade controls (sandbox promotion, guest seats, multi-space views) are being assembled in parallel to make that platform pitch defensible at the CIO level.
Expect more first-party connectors that load non-Jira data (HRIS, CRM, finance) into the Teamwork Graph, paired with Rovo skills that act on it. Configuration Promotion should reach GA within a quarter.
See more alternatives to Paperless-ngx →
See more alternatives to Jira →