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

[#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.

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?

No Time for a Long Reply? A Quick Click Helps Us Immensely!

We know your time is precious, but even a single number tells us a lot about our current adoption rate and helps us focus our support efforts.

Please reply with the number that best describes your team's current status regarding OpenSearch:

1. Migrated! (We are actively using OpenSearch in production)

2. Planning! (We have decided to adopt it and are currently scheduling, reviewing documentation, or in a testing phase.)

3. Blocked! (We want to adopt it but are currently stopped due to a specific issue/bug, missing feature, or resource constraint.)

Ready to experience faster, more reliable search?

Get started and read more:

• OpenSearch for Confluence Data Center

• OpenSearch for Jira Data Center | Atlassian Support | Atlassian Documentation

• OpenSearch hardware recommendations for Jira | Administering Jira applications Data Center 11.2 | Atlassian Documentation

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

Thank you!

[Steve Letch]

I have 3 instances successfully connected to my Opensearch cluster comprising of 2 coordinators, 3 masters, 3 data nodes. when the Opensearch security plugin is disabled so using http without auth,

Confluence Dev - 10.1

Confluence nprod - 9.2

Jira Dev now it's on v11.2

The issue I'm currently having when the Opensearch security plugin is enabled, is getting the tls handshake, for some Opensearch thinks it's receiving http traffic instead of https, even though the url is configured properly.

Currently I'm unable to connect to the indices that were previously working when the security plugin is enabled in opensearch :(

[Sake]

We're waiting for it to be released for Jira (next LTS) :) Confluence is already switched over and the cluster is waiting to spin up containers for Jira!

[Will Yasvoin]

Hey @Steve Letch 

Thanks for the feedback and glad to see you're experimenting with OpenSearch. Can you possibly share more details e.g. some security config (redacted of course) and possibly some OpenSearch logs? The team would be happy to investigate further.

Thanks 

Will