OpenProject 17.9.1 was released on October 1, 2026 and is the current bugfix level of the OpenProject 17.9 series. The main 17.9 release arrived on September 30, 2026 and adds several changes that matter for productive project and knowledge platforms.

For organizations, the feature list alone is not the most important point. What matters is whether documentation, tasks, migration and authentication become easier to operate and control in daily work. This is exactly where OpenProject 17.9 is relevant.

Documents become more connected to project work

One central change is the closer connection between Documents and work packages. According to OpenProject, work packages can now be created directly from a document. This brings documented knowledge closer to concrete tasks, responsibilities and follow-up.

That is especially relevant for teams that do not want specifications, meeting notes, concepts or decision documents to live separately from project execution. Documentation can become actionable work more quickly.

Date alerts in the Community Edition

OpenProject 17.9 makes date alerts available in the Community Edition. Teams can use time-based reminders around dates, deadlines and work packages without necessarily depending on a commercial edition.

For organizations evaluating or self-hosting OpenProject as an open source project management platform, this is a visible step toward more practical planning and deadline transparency.

Backlogs, Jira migration and XWiki integration

Backlogs also receive an initial filtering capability in OpenProject 17.9. That may sound small, but it matters operationally: the larger product and project lists become, the more filtering determines whether teams can work with backlogs efficiently.

OpenProject also highlights improvements around Jira migration. Parallel jobs, progress information and better transparency help especially where existing Jira environments need to be assessed or migrated step by step. XWiki integration is also improved through more targeted page selection.

More control for work packages and exports

OpenProject 17.9 also improves several details around work packages. When deleting work packages with descendants, users can more explicitly decide whether to remove only the selected work package or the entire descendant structure. That reduces the risk of accidentally deleting larger hierarchies.

For bug and product management, the new “Observed in versions” field helps document in which versions an issue has been seen. This is useful when bugs affect multiple product releases or when support cases need to be tracked against concrete versions.

PDF exports are improved as well. According to the release notes, administrators can define defaults per work package type, such as orientation, footer text, table of contents or hyphenation. This helps teams produce more consistent project reports, contract exports and PMflex artefacts.

MCP, meetings and administration

OpenProject 17.9 further extends the MCP server. According to OpenProject, AI assistants can now find, create, update and delete time entries, work with visible work package IDs and receive more compact search results. This is especially relevant for future assistant and automation scenarios.

Meetings also receive smaller but useful improvements: new meetings use more practical default times, and the API can filter meetings by title. The administration interface continues its modernization with Primer UI components, including quick filters in roles and permissions.

More control over SSO and password login

For identity and security teams, more precise control over password login in SSO scenarios is especially interesting. When OpenProject is connected to central authentication systems, it must be clear which local login paths remain allowed and which are intentionally disabled.

OpenProject 17.9.1 also fixes an SSO-relevant issue: according to the release notes, Chrome direct login could fail because of the CSP configuration of the provider host. That makes 17.9.1 more important for Single Sign-On deployments than a simple convenience update.

What 17.9.1 fixes compared with 17.9

OpenProject 17.9.1 is a bugfix release. According to the official release notes, it fixes two concrete issues: the work package sidebar could disappear or be partially hidden, and Chrome direct login via SSO could fail because of the CSP provider host configuration.

Anyone running OpenProject 17.9 in production or planning an update should therefore target 17.9.1 directly instead of staying on 17.9.0.

ForgeOne context

For ForgeOne, OpenProject 17.9.1 fits well into the broader context of sovereign collaboration platforms. The combination of project management, documentation, XWiki integration, SSO control and transparent migration from existing tools is especially relevant.

We updated our own OpenProject environment and are also reviewing the changes technically. A detailed ForgeOne tech article with screenshots, upgrade notes and acceptance checks will follow separately once the technical post is ready.

The official details are available in the OpenProject 17.9 release blog and in the 17.9.0 and 17.9.1 release notes.