Jira Software 11.0 and Jira Service Management 11.0 EAP 06 is now available

BartoszRadaczyski · July 17, 2025, 12:15pm

can you please try this version of amps: 9.3.6-b0307e2b5? Also, the platform version can now be 8.0.0.
Meanwhile, we are working on a fix in amps that will be released before the Jira 11 GA.

Cheers,
Bartosz

adam.labus · July 17, 2025, 12:26pm

Hi @BartoszRadaczyski

this version fixes the issue visible in the logs, thank you

Cheers
Adam

RobertKlimkiewicz · July 31, 2025, 9:44am

Hi Dev Community!

Today, we’ve released the last EAP for Jira 11 with the following number:

11.0.0-EAP06
Maven 11.0.0-m0015

I’ve also updated the main post with the newest data. This EAP includes some internal changes, so there’s nothing new in the “Preparing for” document. However, if you want to find out more about the previous EAP releases, check out Preparing for Jira 11.0.
As this is the final EAP, the main release will happen very soon.

Happy testing!
The Jira Data Center team

adam.labus · July 31, 2025, 9:46am

Hi @RobertKlimkiewicz

Can you comment on my question Jira Software 11.0 and Jira Service Management 11.0 EAP 06 is now available - #40 by adam.labus?

After installing EAP 06, the question is still relevant.

Cheers
Adam

bcinarli · July 31, 2025, 10:40am

@adam.labus , from the usage perspective there are no changes. The button change on the dashboard is not related to AUI10 directly since the buttons are same in AUI10 and AUI9 but mostly due to updated code and removal of deprecated components from earlier versions.

edit: after discussing with AUI team, we are now planning to change those to a real button instead of link button. This will remove the text underline while interacting with these button.

AdamGodziuk · August 12, 2025, 10:06am

Hello, I have upgraded from javax as per documentation, however in case of JAXB I’m getting error:
Caused by: jakarta.xml.bind.JAXBException: Error while searching for service [jakarta.xml.bind.JAXBContextFactory] - with linked exception: [java.util.ServiceConfigurationError: jakarta.xml.bind.JAXBContextFactory: Provider org.glassfish.jaxb.runtime.v2.JAXBContextFactory not found] at jakarta.xml.bind.ContextFinder$1.createException(ContextFinder.java:83) at jakarta.xml.bind.ContextFinder$1.createException(ContextFinder.java:80) at jakarta.xml.bind.ServiceLoaderUtil.firstByServiceLoader(ServiceLoaderUtil.java:46) at jakarta.xml.bind.ContextFinder.find(ContextFinder.java:369) at jakarta.xml.bind.JAXBContext.newInstance(JAXBContext.java:605) at jakarta.xml.bind.JAXBContext.newInstance(JAXBContext.java:546) at com.common.utils.dataCenter.jiraProxyTools.CSLCacheManagerImpl$1.initJAXBContext(CSLCacheManagerImpl.java:73) at com.common.utils.persistance.dao.utils.XmlConverter.init(XmlConverter.java:42) ... 74 more Caused by: java.util.ServiceConfigurationError: jakarta.xml.bind.JAXBContextFactory: Provider org.glassfish.jaxb.runtime.v2.JAXBContextFactory not found at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:593) at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.nextProviderClass(ServiceLoader.java:1219) at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1228) at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1273) at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1309) at java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1393) at jakarta.xml.bind.ServiceLoaderUtil.firstByServiceLoader(ServiceLoaderUtil.java:39) ... 79 more

I can’t add it as dependency, since it has some transitional banned dependencies, and even if I exclude them, later on in Jira I get error:

Caused by: java.util.ServiceConfigurationError: jakarta.xml.bind.JAXBContextFactory: org.glassfish.jaxb.runtime.v2.JAXBContextFactory not a subtype
at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:593) [?:?]
at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1244) [?:?]
at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1273) [?:?]
at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1309) [?:?]
at java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1393) [?:?]
at jakarta.xml.bind.ServiceLoaderUtil.firstByServiceLoader(ServiceLoaderUtil.java:39) [jakarta.xml.bind-api-4.0.2.jar:4.0.2]
… 370 more

And I can;t add it as import-packages:
Package org.glassfish.jaxb.runtime.v2 is internal and is not available for export to plugin

Is there anything else I should do to upgrade this to work with Jira 11? Using 11.0.0-EAP06.

PabloPidal · August 12, 2025, 11:25am

Hello, in the release candidate version you released (m0017), when trying to install a plugin from a file, I get the following error:

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'fisheyeManager': Lookup method resolution failed
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.checkLookupMethods(AutowiredAnnotationBeanPostProcessor.java:498)
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.determineCandidateConstructors(AutowiredAnnotationBeanPostProcessor.java:368)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.determineConstructorsFromBeanPostProcessors(AbstractAutowireCapableBeanFactory.java:1334)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1229)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:569)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:529)
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:339)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:373)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:337)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.instantiateSingleton(DefaultListableBeanFactory.java:1222)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingleton(DefaultListableBeanFactory.java:1188)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:1123)
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:987)
	at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$1100(AbstractDelegatedExecutionApplicationContext.java:57)
	at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:322)
	at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
	at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:287)
	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:137)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.lang.IllegalStateException: Failed to introspect Class [com.atlassian.jirafisheyeplugin.domain.fisheye.FishEyeManagerImpl] from ClassLoader [com.atlassian.jira.plugins.jira-fisheye-plugin [116]]
	at org.springframework.util.ReflectionUtils.getDeclaredMethods(ReflectionUtils.java:483)
	at org.springframework.util.ReflectionUtils.doWithLocalMethods(ReflectionUtils.java:320)
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.checkLookupMethods(AutowiredAnnotationBeanPostProcessor.java:476)
	... 21 more
Caused by: java.lang.NoClassDefFoundError: com/atlassian/jira/plugin/devstatus/api/DevStatusSupportedApplicationLinkService
	at java.base/java.lang.Class.getDeclaredMethods0(Native Method)
	at java.base/java.lang.Class.privateGetDeclaredMethods(Class.java:3578)
	at java.base/java.lang.Class.getDeclaredMethods(Class.java:2676)
	at org.springframework.util.ReflectionUtils.getDeclaredMethods(ReflectionUtils.java:465)
	... 23 more
Caused by: java.lang.ClassNotFoundException: com.atlassian.jira.plugin.devstatus.api.DevStatusSupportedApplicationLinkService not found by com.atlassian.jira.plugins.jira-fisheye-plugin [116]
	at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591)
	at org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79)
	at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1976)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526)
	... 27 more

If I go to jira-development-integration-plugin-11.0.0-m0017.jar, the class com.atlassian.jira.plugin.devstatus.api.DevStatusSupportedApplicationLinkService does not exist. However, you reference it from com.atlassian.jirafisheyeplugin.domain.fisheye.FishEyeManagerImpl (you can see the reference directly in the .class by opening the file: “com/atlassian/jira/plugin/devstatus/api/DevStatusSupportedApplicationLinkService;”)

I am using this options for local tests (set JVM_SUPPORT_RECOMMENDED_ARGS=-Dupm.plugin.upload.enabled=true -Datlassian.upm.security.disable=true)

metin · August 14, 2025, 10:13am

Hey, Atlassians!

Jira 11.0 final release seems out now, but still missing the docker image. Can you check, please?

MarkusDarko · August 17, 2025, 1:11pm

Hitting the same problem. These dependencies are not available in any of the repos referenced by the Atlassian SDK maven settings.xml

SeriousDen · August 18, 2025, 5:16am

The issue disappear after Atlassian Team have published the first release version of Jira 11. You need just jump on platform-public-api:8.0.0, which has all its dependencies in public space. It works for me within amps 9.5.4

PabloPidal · August 18, 2025, 8:56am

Ok, failing on jira 11.0.0-RC but it’s working on jira 11.0.0, thanks

aragot · August 20, 2025, 3:15pm

Hi @RobertKlimkiewicz ,

On Search API deprecations and upgrade guide for Jira 11 | Administering Jira applications Data Center 11.0 | Atlassian Documentation, you mention to replace ClauseQueryFactory with ClauseQueryMapper.

But ClauseQueryMapper is marked as deprecated in Jira 10.4. Are you recommending to move to a deprecated class?

Also, is the recommended pom.xml still with a <dependency> to jira-api and <dependencyManagement> to platform-public-api:8.0.0 ? Isn’t jira-api supposed to be deprecated?

Thank you very much!

lexek-92 · August 21, 2025, 10:53am

Is there still no Docker images for Jira 11?

richard.white · August 21, 2025, 10:49pm

They finally appeared last night:
e.g. https://hub.docker.com/layers/atlassian/jira-software/11.0.0/images/sha256-4fa4a9ef4b96f3aeecb7ebb9c4cef635535b3970d5d3593b9220c98899cbb25b

https://hub.docker.com/layers/atlassian/jira-servicemanagement/11.0.0/images/sha256-29709bcda10fefe69ac0fd714b4a8115346f4054690c71b5e4475cc09c2ebf91

louiekessler · September 5, 2025, 6:26am

Jira 11 doesn’t seem to work with HTTPS Tomcat Connector with “keystoreFile“ and “keystorePass“ variables as described here .

In the logs I see this error:

Summary

SEVERE [main] org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to initialize component [Connector["https-jsse-nio-8443"]]
        org.apache.catalina.LifecycleException: Protocol handler initialization failed
                at org.apache.catalina.connector.Connector.initInternal(Connector.java:1075)
                at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:122)
                at org.apache.catalina.core.StandardService.initInternal(StandardService.java:522)
                at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:122)
                at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:957)
                at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:122)
                at org.apache.catalina.startup.Catalina.load(Catalina.java:712)
                at org.apache.catalina.startup.Catalina.load(Catalina.java:735)
                at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
                at java.base/java.lang.reflect.Method.invoke(Method.java:580)
                at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:302)
                at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:475)
        Caused by: java.lang.IllegalArgumentException: No SSLHostConfig element was found with the hostName [_default_] to match the defaultSSLHostConfigName for the connector [https-jsse-nio-8443]
                at org.apache.tomcat.util.net.AbstractJsseEndpoint.initialiseSsl(AbstractJsseEndpoint.java:76)
                at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:226)
                at org.apache.tomcat.util.net.AbstractEndpoint.bindWithCleanup(AbstractEndpoint.java:1399)
                at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:1412)
                at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:633)
                at org.apache.coyote.http11.AbstractHttp11Protocol.init(AbstractHttp11Protocol.java:82)
                at com.atlassian.secrets.tomcat.protocol.Http11NioProtocolWithPasswordEncryption.init(Http11NioProtocolWithPasswordEncryption.java:14)
                at org.apache.catalina.connector.Connector.initInternal(Connector.java:1073)
                ... 11 more

For reference, this is my HTTPS Connector in server.xml:

Summary

<Connector port="8443"
    SSLEnabled="true"
    acceptCount="100"
    clientAuth="false"
    connectionTimeout="20000"
    disableUploadTimeout="true"
    enableLookups="false"
    keyAlias="***"
    keystoreFile="***"
    keystorePass="***"
    productEncryptionKey="***"
    keystoreType="JKS"
    maxHttpHeaderSize="8192"
    maxSpareThreads="75"
    maxThreads="150"
    minSpareThreads="25"
    protocol="com.atlassian.secrets.tomcat.protocol.Http11NioProtocolWithPasswordEncryption"
    proxyName="***"
    proxyPort="443"
    relaxedPathChars="[]|"
    relaxedQueryChars="[]|{}^\`&quot;&lt;&gt;"
    scheme="https"
    secure="true"
    sslEnabledProtocols="TLSv1.2,TLSv1.3"
    sslProtocol="TLS"
    useBodyEncodingForURI="true"/>

It seems like these are deprecated and not working anymore since Tomcat 10, see Apache Tomcat 9 Configuration Reference (9.0.108) - The HTTP Connector

How to fix this? And could you also update the Doc’s?

Thanks!

louiekessler · September 8, 2025, 6:35am

HTTPS Connector works with the following config. However I can’t get it to work with an encrypted keystore password like in Jira <11 / Tomcat <10…

<Connector
    port="8443"
    SSLEnabled="true"
    acceptCount="100"
    connectionTimeout="20000"
    disableUploadTimeout="true"
    enableLookups="false"
    maxHttpHeaderSize="8192"
    maxSpareThreads="75"
    maxThreads="150"
    minSpareThreads="25"
    protocol="org.apache.coyote.http11.Http11NioProtocol"
    proxyName="***"
    proxyPort="443"
    relaxedPathChars="[]|"
    relaxedQueryChars="[]|{}^\`&quot;&lt;&gt;"
    scheme="https"
    secure="true"
    useBodyEncodingForURI="true">
    <SSLHostConfig>
        <Certificate
        protocols="TLSv1.2,TLSv1.3"
        certificateVerification="required"
        certificateKeystoreFile="***"
        certificateKeystorePassword="***"
        certificateKeyAlias="***"
        certificateKeystoreType="JKS"/>
    </SSLHostConfig>
</Connector>

SeriousDen · September 26, 2025, 9:55am

Does anybody encounter any issues with built-in Streams plugin (in recent Jira releases 11.0.1 & 11.1.0)? I’ve faced the issue of the Streams Plugin cannot resolve htttpClient 5. I clearly can see that it’s provided by the System plugin (osgi bundle), and also can confirm that the Streams plugin imports it successfully, but it doesn’t work at all, and I cannot understand why. For example, if you navigate to the summary project page (activity view), then you will get the error

2025-09-26 14:18:51,560+0700 http-nio-2990-exec-10 ERROR      [o.a.c.c.C.[.[localhost].[/jira].[servlet-module-container-servlet]] Servlet.service() for servlet [servlet-module-container-servlet] in context with path [/jira] threw exception [Servlet execution threw an exception] with root cause
java.lang.ClassNotFoundException: org.apache.hc.client5.http.classic.HttpClient not found by com.atlassian.streams.core-plugin [166]
2025-09-26 14:18:51,582+0700 http-nio-2990-exec-10 ERROR      [c.a.j.web.servlet.InternalServerErrorServlet] {errorId=2c66406d-d805-4b4d-9014-2893dbb383da, interpretedMsg=, cause=java.lang.NoClassDefFoundError: org/apache/hc/client5/http/classic/HttpClient, stacktrace=java.lang.NoClassDefFoundError: org/apache/hc/client5/http/classic/HttpClient
    	at org.owasp.validator.html.scan.AntiSamyDOMScanner.processAttributes(AntiSamyDOMScanner.java:582) [?:?]
    Caused by: java.lang.ClassNotFoundException: org.apache.hc.client5.http.classic.HttpClient not found by com.atlassian.streams.core-plugin [166]

Full stacktrace is very long for this error:

stacktrace.txt (60.1 KB)

Does anybody have any idea? I really need help to address this issue.

AndreasLfgren1 · November 13, 2025, 11:25am

Has TrustedRequestFactory been removed in Jira 11? Any recommendations on what to use instead?

rlander · November 13, 2025, 12:14pm

See https://jira.atlassian.com/browse/CONFSERVER-99078

And https://bitbucket.org/atlassian/dc-platform/src/50ef1c7f3e504ebb03f62cee4f1d568747694d05/demos/oauth1-impersonation-plugin-example

For the replacement API for Trusted Apps