Atlassian Service Management Update Version 11.3.2

Jira Software 11.3.2 was released on 2026-02-05. It adds admin controls for JQL clause limits to reduce out-of-memory risk and includes security fixes for DoS issues in `okio` and `semver` dependencies. Reference IDs: JSWSERVER-26764, JSWSERVER-26716.

• Fixes DoS (Denial of Service) issues in com.squareup.okio:okio and semver dependencies in Jira Software Data Center and Server.

• Software project board creation could fail when too many statuses existed.
• OAuth 2.0 authentication flow could not be completed on the development panel.
• Advanced Roadmaps plans could disappear when date fields contained invalid data.
• Backlog sprint creation had missing accessibility semantics for unordered lists and grouped form controls.
• Plugin upgrades could take several hours because permission checking lacked caching.
• Index snapshot restore could unexpectedly allow traffic while an exclusive write lock was held in clustered environments.
• JQL searches with many text clauses could cause out-of-memory errors or jqlTooComplex responses.
• Editing the hostname for Custom Service Provider with MS_Graph protocol required switching providers first.
• Automation rules could overwrite variables inconsistently.

• Admins can set limits for the maximum number of clauses allowed in plain JQL queries.
• Jira can estimate JQL clause counts and reject queries that exceed the configured limit.

• Configure jira.clause.count.limit and jira.clause.count.estimation to match server memory capacity; both are enabled by default.
• Atlassian recommends a clause limit of 65,000 and monitoring logs for rejected queries to tune performance.
• See the Preventing crashes with JQL resilience guidance for configuration details and best practices.

Product Information

Vendor: Atlassian

Product: Service Management

Version: 11.3.2

Release date: Feb 5, 2026