We want your feedback: OpenSearch is now available in Jira 11.2

Jira Development Jira Data Center
1

Hi all,

We’re thrilled to share that OpenSearch is now live and generally available in Jira 11.2! Already proven in Confluence since 9.2 LTS, this next-generation search engine brings faster, smarter, and more scalable search to Jira Data Center—delivering improved speed and reliability, and enabling the use of more cost-effective hardware.

:information_source: OpenSearch for Jira will be included in the upcoming Jira 11.3 LTS release.

Why OpenSearch?

OpenSearch in Jira isn’t just about searching—it supports everything you do, from loading boards and viewing backlogs to generating reports and working with issues. Because so many core actions rely on search, OpenSearch’s speed, consistency, and reliability have a direct impact on your team’s productivity and experience.

Key benefits:

  • Better search results: In Confluence, OpenSearch is approximately 4.5 times faster than a comparable Lucene-based search. In Jira, it delivers a 38% improvement in overall performance.
    • OpenSearch reduces memory consumption and garbage collection overhead, significantly lowers thread contention, and eliminates input/output (I/O) anomalies seen with Lucene.
    • This performance gap increases as your dataset grows, so you’ll notice even greater improvements over time.
  • Scalable architecture: Confidently support more users and larger datasets without sacrificing performance.
  • Advanced analytics and observability: Get deeper insights into search performance and usage.
  • Open-source flexibility: Benefit from active community support and continuous improvements.

Your feedback matters!

  • Are you already using OpenSearch? What benefits or issues have you noticed?
  • Will you adopt OpenSearch in the next 6–12 months?
  • What search or performance challenges are you currently experiencing in Jira or Confluence?
  • What would make you consider enabling OpenSearch in Jira or/and Confluence
  • Are there any concerns or blockers that may prevent you from adopting OpenSearch?

:timer_clock: No Time for a Long Reply? A Quick Click Helps Us Immensely!
We know your time is valuable, so we’ve added a quick poll to make it easy for you to share your team’s OpenSearch status with us.

  • Migrated! (We are actively using OpenSearch in production)
  • Planning! (We have decided to adopt it and are currently scheduling, reviewing documentation, or in a testing phase.)
  • Blocked! (We want to adopt it but are currently stopped due to a specific issue/bug, missing feature, or resource constraint.)
0 voters

Ready to experience faster, more reliable search?

Get started and read more:

Let us know how things are going, your input will directly influence our next steps.

Thank you!

2 Likes