Jira 9.11 EAP 01 has been released!

Jira Development Jira Data Center Announcements
, ,
1

Hi, Developer Community! :wave: The first EAP for Jira 9.11 Data Center and Server is ready for testing.

Highlights:

  • Jira automation 9.0 release
    The Automation for Jira app has been upgraded to version 9.0 but remains compatible with all releases from Jira 8.20.0 and Jira Service Management 4.20.0. The updates in Jira automation 9.0 include:

    • secret key masking
    • the new actions “Lookup issues“ and “Create variables“
    • the default enablement of the allowlist for sending outbound HTTP requests

  • Reorder project shortcuts
    You can rearrange shortcuts in the project sidebar by dragging and dropping or selecting the Move up and Move down buttons.

  • S3 object storage for attachments
    You can now store attachments more efficiently in Amazon S3 object storage.

  • Jira becomes more resilient to database connectivity dropouts
    Even if Jira loses a database connection while a scheduled job is starting, the job won’t be lost from your instance until the restart. When the connection resumes, the job will automatically restore, start, and properly schedule for the next occurrence.

  • Support for AWS Secrets Manager
    With Secrets Manager from Amazon Web Services, you’ll avoid storing plaintext passwords in configuration files and rest assured that your secrets won’t be exposed to any vulnerabilities.

  • User session invalidation across the cluster without the system reboot
    User sessions will be invalidated cluster-wide, without restarting Jira, after a user’s password is changed, a user gets anonymized or deleted, or an admin ends a user’s session through a REST API on any node.

  • New infrastructure metrics for in-product diagnostics
    We’ve added new metrics for monitoring the health and performance of your instance infrastructure:

    • outgoing and incoming mail servers
    • external user directories
    • shared and local home directories
    • node communication for Data Center instances.

  • Link multiple spaces to a portal in Jira Service Management
    Project admins can now link to more than one space from the same Confluence instance and let agents and customers access a wider range of articles.

  • New editor in Assets
    We’ve updated the editor in object comments and post-function email templates to create a modern and consistent experience across Assets and the rest of the Jira Service Management UI.

  • Improved search experience in Jira Service Management
    We’ve improved the search experience on the Customers page and made the messaging displayed during search request timeouts accurate.

  • Read-only access to Assets information
    We’ve improved the security of Assets data by strengthening the access pattern. Confluence users will have view-only access to Assets data through the Assets - Confluence Macro app without the need for a Jira Service Management license.

  • Breaking changes to Assets APIs in previous releases
    Breaking changes to Assets APIs in previous releases may have caused some issues for our app developers as we missed communicating these changes. We’ve now added the information to the following release notes.

  • Project permissions get extended configuration
    You can now define user visibility in mentions, Assignee, and Reporter pickers by using the extended project permissions: Assign issues for Assignee, Modify reporter for Reporter, and browse projects for User mentions. As we no longer validate Browse users permissions for these pickers and mentions, you might need to adjust your current settings.

  • Removing deprecated functions from the UrlState.js
    In Jira 9.9, we’ve deprecated several functions in the UrlState.js library. In this version, we’re removing them completely from the codebase.

  • Improvements to the support zip creation
    We’ve improved the process of creating a support zip in the Atlassian Troubleshooting and Support Tools (ATST) app by redesigning the Create support zip page and introducing additional configuration options.

  • More accessibility updates in Jira Service Management
    The highlights of this release include improved screen reader announcements for help center errors, the Activity section in issues, and column headers when you switch between them. We’ve also improved the experience of reaching the show-and-hide toolbar element. Check out the full list of fixed issues

Downloads & docs
For details, see Preparing for Jira 9.11. You can download the EAP from this page. If you’re using maven.atlassian.com, the version is 9.11.0-m0003.

If you have any comments, post them below.

Happy testing,
The Jira Server and Data Center team

4 Likes
2

Hi,
I tried atlassian-jira-software-9.11.0-EAP01-x64.bin on my local env, but the setup wizard failed with an error. I tested on three Virtualbox environments.

  • Ubuntu 20.04 and PostgreSQL 12
  • CentOS 8 and PostgreSQL 10
  • CentOS 8 and H2 (Built In)
2023-08-10 03:35:45,625+0000 http-nio-8080-exec-18 ERROR anonymous 215x208x1 zspsyj 192.168.33.1 /secure/SetupDatabase.jspa [c.a.jira.startup.ComponentContainerLauncher] An Error occurred during ComponentContainerLauncher servlet context initialisation - class com.atlassian.jira.issue.customfields.manager.xml.AllowlistedXStreamFactory (in unnamed module @0x4b9779ac) cannot access class sun.util.calendar.BaseCalendar$Date (in module java.base) because module java.base does not export sun.util.calendar to unnamed module @0x4b9779ac.
java.lang.IllegalAccessError: class com.atlassian.jira.issue.customfields.manager.xml.AllowlistedXStreamFactory (in unnamed module @0x4b9779ac) cannot access class sun.util.calendar.BaseCalendar$Date (in module java.base) because module java.base does not export sun.util.calendar to unnamed module @0x4b9779ac
        at com.atlassian.jira.issue.customfields.manager.xml.AllowlistedXStreamFactory.fillJiraDefaults(AllowlistedXStreamFactory.java:77)
        at com.atlassian.jira.issue.customfields.manager.xml.AllowlistedXStreamFactory.create(AllowlistedXStreamFactory.java:60)
        at com.atlassian.jira.issue.customfields.manager.xml.DefaultXmlConverter.<init>(DefaultXmlConverter.java:45)
        at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
        at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Unknown Source)
        at java.base/java.lang.reflect.Constructor.newInstance(Unknown Source)
        at org.picocontainer.injectors.AbstractInjector.newInstance(AbstractInjector.java:145)
        at org.picocontainer.injectors.ConstructorInjector$1.run(ConstructorInjector.java:342)
...
3

Same error on my end (Windows 10). This is the first time I got such an error during installation of Jira (incl. EAPs), so I suspect the cause is not on my end, but something with the 9.11.0 EAP.

1 Like
4

Same error on EAP02. Does anyone in Atlassian know this situation? I’m using JDK and H2 database bundled in Jira.

# /opt/atlassian/jira/jre/bin/java --version
openjdk 17.0.7 2023-04-18
OpenJDK Runtime Environment Temurin-17.0.7+7 (build 17.0.7+7)
OpenJDK 64-Bit Server VM Temurin-17.0.7+7 (build 17.0.7+7, mixed mode, sharing)

On the other hand, the Docker image (atlassian/jira-software:9.11.0-EAP02-ubuntu-jdk11) works correctly. The error did not happen.

5

Hello,
I tried to create a filter with a query like this one - “status = testStatus”, but it seems that in the new version (9.11.0-m0002), we can’t add status by name into a filter if it’s not associated with a workflow.
Does anyone in Atlassian know if that is a bug or a new improvement?

Thanks,
Stivan

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.