Jira Software 11.2 and Jira Service Management 11.2 EAP is now available

Jira Development Jira Data Center
1

Hi, Developer Community! :wave: The EAP release of Jira 11.2 is ready for testing.

You can download the EAP from this page. If you’re using maven.atlassian.com, the version is:

  • For EAP01: 11.2.0-m0040

To find out more about this EAP release, check out Preparing for Jira 11.2. Quick summary of changes:

  • Jira Software and Jira Service Management common features:

    • Supported platforms changes
    • Welcome OpenSearch in Jira Data Center
    • Indexing and snapshots improved with OpenSearch
    • Implement custom query mappers for your app
    • Connect securely with OAuth 2.0 for app links
    • Protect your Jira nodes with JQL resilience
    • :red_exclamation_mark:Strengthen sysadmin and OS access separation breaking change
    • :red_exclamation_mark:Optimize your instance with safeguards breaking change
    • One place to clean them all

  • Jira Software features:

    • Deprecation of Browse Project properties in workflows
    • New limit of 10,000 items on a board
    • Jira Mobile plugin removal

  • Jira Service Management features:

    • New REST API scopes for service accounts
    • Link your Jira with Confluence through OAuth 2.0

If you have any comments, post them below.

Happy testing,
The Jira Data Center team

1 Like
2

@RobertKlimkiewicz Does this EAP contain all changes from Jira 11.0.1 & 11.1.1? I’m interested in a specific built-in plugin named Streams plugin, which supply for Activity streams functionality.

3

Hey @SeriousDen, yes, it does contain them, so this EAP should be fine to check things from 11.0.0 / 11.1.1.

1 Like
4

Hi, Dev Community!
We’ve identified one more breaking change that might impact your apps. I marked this change with the label breaking change in the list above and updated the Preparing for Jira 11.2 page. This affects the new safeguards features in the Instance optimizer.

Make sure your app detects creation errors triggered by safeguard enforcement and shows a clear message to users if a safeguard is breached. Most safeguard enforcement is implemented at the service layer (for example, productService instead of productManager, or issueService instead of issueManager). For best integration and error reporting, your app should use the service layer where possible.

Don’t adjust default safeguard limits in production instances without consulting Atlassian support. For product testing, you can adjust safeguard limits in Advanced settings.

If you have any comments, post them below.

Happy testing,
Robert

5

Hi, Dev Community!

The second EAP has just been released. The version is 11.2.0-m0041.

In this EAP, we’ve added a note about React 18 and Atlaskit upgrade.

Happy testing!
Vasylyna