I’m writing to share my first thoughts on this early version.
I noticed that the ‘change’ event on the ‘aui-toggle’ component isn’t working as expected.
It seems to always catch the opposite value, which is definitely not correct.
This issue is particularly problematic for toggles that are initially disabled.
Thanks for your message, indeed the default docker image was still using JDK17, and thus unable to start.
We have pulled the incorrect images, and pushed new ones based on JDK21, which correctly start.
Thanks for the feedback @chrschommer, however, I am not yet able to reproduce the issue, could you provide more details regarding how you are running Jira and when do you get the error ?
Could it be due to the jQuery changes? Since with this EAP, we remove jQuery 1 and jQuery 2 migrate, and there is a breaking change in jQuery 1.9
When you try to get the checked status of a checkbox with attribute, it is not working as expected. Some details are here in jQuery webpage: jQuery Core 1.9 Upgrade Guide | jQuery
Please let me know if you see the same problem when to check the toggle with prop, e.g.
AJS.$(document).ready(function () {
var toggle = AJS.$("aui-toggle[id='gzip-compression']");
toggle.change(function () {
if (toggle.prop('checked') === true) {
console.log("gzip-compression - CHECKED");
} else {
console.log("gzip-compression - NOT CHECKED");
}
});
});
Hello,
Thank you for reaching out. You are correct the links in readme.txt will only work when the final version is officially released.
In the mean time, you should rely on Preparing for Jira 11.0 | Administering Jira applications Data Center 10.6 | Atlassian Documentation.
You can also modify the links by replacing 110 with the latest feature release, so 106 currently, for example: http://docs.atlassian.com/jira/jadm-docs-106/Installing+Jira+applications
thata way you can access the docs from the latest release, also they might not be fully valid for 11.0.
Hey @JnisVanags
Speaking of the databases, I confirmed that with the team and PostreSQL 17 is supported. That error message was a health check error; we’re working on removing the error to avoid confusion
I’m struggling on missing artifact errors, which had become to appear too often after the repositories’ schema was changed (after the main Atlassian repo was deprecated as well as many third-party were introduced).
Since Jira 11 (EAP 2) has appeared, I’m trying to assemble my plugin which imports dependencies platform-public-api:8.0.0-m13 (which is a recommended way to manage dependencies, does it?), but it fails to resolve many transient/derivative dependencies due to they are missed in repositories.
For example, it cannot be resolved com.atlassian.crowd:crowd-api:7.0.0-p8-m23 (version is defined by platform-public-api pom-file). The most recent version I can see in the repo is 7.0.0-p8-m16. OK, I can substitute missed dependency by another one, but it involves another errors in runtime now, which I really don’t want to resolve on my side. And it is not a single dependency which cannot be resolved in the repo. It makes me really sad each time when I faced with such kind of errors.
Could you be so kind to publish all derivatives dependencies are mentioned in yours parent pom-files like platform-public-api, platform-bundled-plugins, platform-test-resources and others which are widely used developers as you recommended?
Im having an issue "com.atlassian.jira:jira-mail-plugin" it appears to still use javax in particular this class AbstractMessageHandler which is causing a java.lang.NoClassDefFoundError: javax.mail.Message when i’m trying to run Jira 11.0, is there a version of this that upgrades it to use Jakarta?
The latest jira-mail-plugin which I see in the repo is 111.0.8-6341e05. It has parent project jira-plugins-bundle:111.0.8-6341e05, which defines Jira version as 11.0.0-QR-20250228115330, and it does not contain Jakarta-related changes. It also exists more fresh jira-plugins-bundle:111.0.31 for Jira version 11.0.0-QR-20250519135447 which is probably what you need (no guarantee). Nevertheless, there is no related jira-mail-plugin in the repository… So, you’ve faced the missed artifacts issue, as I did.
Jira Software Application : com.atlassian.jira.jira-software-application
Version : 11.0.0-m0002
Status : enabled
Vendor : Atlassian
Description : Gathers pieces of Jira Software together.
but then
'com.pyxis.greenhopper.jira' - 'Jira Agile' failed to load.
Application context initialization for 'com.pyxis.greenhopper.jira' has timed out waiting for (objectClass=com.atlassian.jira.search.index.IndexAccessorRegistry)
Any ideas?
___ FAILED PLUGIN REPORT _____________________
7 plugins failed to load during Jira startup.
'com.atlassian.jira.plugins.jira-bitbucket-connector-plugin' - 'Jira DVCS Connector Plugin' failed to load.
Error creating bean with name 'repositoryDaoImpl': Injection of resource dependencies failed
Error creating bean with name 'defaultSynchronizer': Injection of resource dependencies failed
Error creating bean with name 'branchServiceImpl': Injection of resource dependencies failed
Error creating bean with name 'dvcsCommunicatorProviderImpl': Injection of resource dependencies failed
Error creating bean with name 'cachingBitbucketCommunicator' defined in URL [bundle://4a4fac89-bbaf-42a0-8677-c55aff0a3ca2_95.0:0/META-INF/spring/spring.xml]: Cannot resolve reference to bean 'bitbucketCommunicator' while setting bean property 'delegate'
Error creating bean with name 'bitbucketCommunicator': Injection of resource dependencies failed
Error creating bean with name 'messagingServiceImpl': Injection of resource dependencies failed
Error creating bean with name 'gitHubPullRequestPageMessageConsumer': Injection of resource dependencies failed
Error creating bean with name 'dvcsHttpStats' defined in com.atlassian.jira.plugins.dvcs.stats.DVCSStatsConfiguration: Failed to instantiate [com.atlassian.jira.plugins.dvcs.stats.DVCSHttpStats]: Factory method 'dvcsHttpStats' threw exception with message: failed to access class com.atlassian.jira.plugins.dvcs.stats.DVCSHttpStats from class com.atlassian.jira.plugins.dvcs.stats.DVCSStatsConfiguration$$SpringCGLIB$$0 (com.atlassian.jira.plugins.dvcs.stats.DVCSHttpStats is in unnamed module of loader org.apache.felix.framework.BundleWiringImpl$BundleClassLoader @4f039b3; com.atlassian.jira.plugins.dvcs.stats.DVCSStatsConfiguration$$SpringCGLIB$$0 is in unnamed module of loader org.eclipse.gemini.blueprint.util.BundleDelegatingClassLoader @2cd97cae)
Failed to instantiate [com.atlassian.jira.plugins.dvcs.stats.DVCSHttpStats]: Factory method 'dvcsHttpStats' threw exception with message: failed to access class com.atlassian.jira.plugins.dvcs.stats.DVCSHttpStats from class com.atlassian.jira.plugins.dvcs.stats.DVCSStatsConfiguration$$SpringCGLIB$$0 (com.atlassian.jira.plugins.dvcs.stats.DVCSHttpStats is in unnamed module of loader org.apache.felix.framework.BundleWiringImpl$BundleClassLoader @4f039b3; com.atlassian.jira.plugins.dvcs.stats.DVCSStatsConfiguration$$SpringCGLIB$$0 is in unnamed module of loader org.eclipse.gemini.blueprint.util.BundleDelegatingClassLoader @2cd97cae)
failed to access class com.atlassian.jira.plugins.dvcs.stats.DVCSHttpStats from class com.atlassian.jira.plugins.dvcs.stats.DVCSStatsConfiguration$$SpringCGLIB$$0 (com.atlassian.jira.plugins.dvcs.stats.DVCSHttpStats is in unnamed module of loader org.apache.felix.framework.BundleWiringImpl$BundleClassLoader @4f039b3; com.atlassian.jira.plugins.dvcs.stats.DVCSStatsConfiguration$$SpringCGLIB$$0 is in unnamed module of loader org.eclipse.gemini.blueprint.util.BundleDelegatingClassLoader @2cd97cae)
It was loaded from /home/jira/atlassian/test/jira-sw/jira11/11.0.0/home/plugins/installed-plugins/jira-dvcs-connector-plugin-11.0.0-m0002.jar
'com.atlassian.jira.plugins.jira-development-integration-plugin' - 'Atlassian Jira - Plugins - Development Integration Plugin' failed to load.
Application context initialization for 'com.atlassian.jira.plugins.jira-development-integration-plugin' has timed out waiting for (|(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsBranchService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsBranchService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsChangesetService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsChangesetService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsLinkService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsLinkService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsPullRequestService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsPullRequestService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsRepositoryService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsRepositoryService)))
It has the following missing service dependencies :
&dvcsLinkService of type (&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsLinkService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsLinkService))
&dvcsRepositoryService of type (&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsRepositoryService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsRepositoryService))
&dvcsPullRequestService of type (&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsPullRequestService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsPullRequestService))
&dvcsBranchService of type (&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsBranchService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsBranchService))
&dvcsChangesetService of type (&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsChangesetService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsChangesetService))
It was loaded from /home/jira/atlassian/test/jira-sw/jira11/11.0.0/home/plugins/installed-plugins/jira-development-integration-plugin-11.0.0-m0002.jar
'com.pyxis.greenhopper.jira' - 'Jira Agile' failed to load.
Application context initialization for 'com.pyxis.greenhopper.jira' has timed out waiting for (objectClass=com.atlassian.jira.search.index.IndexAccessorRegistry)
It has the following missing service dependencies :
&indexAccessorRegistry of type (objectClass=com.atlassian.jira.search.index.IndexAccessorRegistry)
It was loaded from /home/jira/atlassian/test/jira-sw/jira11/11.0.0/home/plugins/installed-plugins/jira-greenhopper-plugin-11.0.0-m0002.jar
'com.atlassian.troubleshooting.plugin-jira' - 'Atlassian Troubleshooting and Support Tools' failed to load.
Cannot start plugin: com.atlassian.troubleshooting.plugin-jira
Unable to resolve com.atlassian.troubleshooting.plugin-jira [173](R 173.0): missing requirement [com.atlassian.troubleshooting.plugin-jira [173](R 173.0)] osgi.wiring.package; (&(osgi.wiring.package=javax.ws.rs)(version>=2.0.0)(!(version>=3.0.0))) Unresolved requirements: [[com.atlassian.troubleshooting.plugin-jira [173](R 173.0)] osgi.wiring.package; (&(osgi.wiring.package=javax.ws.rs)(version>=2.0.0)(!(version>=3.0.0)))]
It was loaded from /home/jira/atlassian/test/jira-sw/jira11/11.0.0/jira/atlassian-jira/WEB-INF/atlassian-bundled-plugins/plugin-jira-2.8.0.jar
'com.atlassian.jira.migration.jira-migration-plugin' - 'Jira Cloud Migration Assistant' failed to load.
Cannot start plugin: com.atlassian.jira.migration.jira-migration-plugin
Unable to resolve com.atlassian.jira.migration.jira-migration-plugin [83](R 83.0): missing requirement [com.atlassian.jira.migration.jira-migration-plugin [83](R 83.0)] osgi.wiring.package; (osgi.wiring.package=javax.inject) Unresolved requirements: [[com.atlassian.jira.migration.jira-migration-plugin [83](R 83.0)] osgi.wiring.package; (osgi.wiring.package=javax.inject)]
It was loaded from /home/jira/atlassian/test/jira-sw/jira11/11.0.0/jira/atlassian-jira/WEB-INF/atlassian-bundled-plugins/jira-migration-plugin-1.12.36.jar
'com.atlassian.jira.mobile.jira-mobile-rest' - 'Mobile Plugin for Jira Data Center and Server' failed to load.
Application context initialization for 'com.atlassian.jira.mobile.jira-mobile-rest' has timed out waiting for (|(&(objectClass=com.atlassian.greenhopper.service.rapid.view.ColumnService)(objectClass=com.atlassian.greenhopper.service.rapid.view.ColumnService))(&(objectClass=com.atlassian.greenhopper.api.customfield.ManagedCustomFieldsService)(objectClass=com.atlassian.greenhopper.api.customfield.ManagedCustomFieldsService))(&(objectClass=com.atlassian.greenhopper.service.rapid.ProjectRapidViewService)(objectClass=com.atlassian.greenhopper.service.rapid.ProjectRapidViewService))(&(objectClass=com.atlassian.greenhopper.service.rapid.RapidViewHistoryService)(objectClass=com.atlassian.greenhopper.service.rapid.RapidViewHistoryService))(&(objectClass=com.atlassian.greenhopper.service.issue.RapidViewIssueService)(objectClass=com.atlassian.greenhopper.service.issue.RapidViewIssueService))(&(objectClass=com.atlassian.greenhopper.service.rapid.RapidViewQueryService)(objectClass=com.atlassian.greenhopper.service.rapid.RapidViewQueryService))(&(objectClass=com.atlassian.greenhopper.service.rapid.view.RapidViewService)(objectClass=com.atlassian.greenhopper.service.rapid.view.RapidViewService))(&(objectClass=com.atlassian.greenhopper.service.sprint.SprintService)(objectClass=com.atlassian.greenhopper.service.sprint.SprintService)))
It has the following missing service dependencies :
&rapidViewService of type (&(objectClass=com.atlassian.greenhopper.service.rapid.view.RapidViewService)(objectClass=com.atlassian.greenhopper.service.rapid.view.RapidViewService))
&columnService of type (&(objectClass=com.atlassian.greenhopper.service.rapid.view.ColumnService)(objectClass=com.atlassian.greenhopper.service.rapid.view.ColumnService))
&rapidViewIssueService of type (&(objectClass=com.atlassian.greenhopper.service.issue.RapidViewIssueService)(objectClass=com.atlassian.greenhopper.service.issue.RapidViewIssueService))
&sprintService of type (&(objectClass=com.atlassian.greenhopper.service.sprint.SprintService)(objectClass=com.atlassian.greenhopper.service.sprint.SprintService))
&managedCustomFieldsService of type (&(objectClass=com.atlassian.greenhopper.api.customfield.ManagedCustomFieldsService)(objectClass=com.atlassian.greenhopper.api.customfield.ManagedCustomFieldsService))
&rapidViewHistoryService of type (&(objectClass=com.atlassian.greenhopper.service.rapid.RapidViewHistoryService)(objectClass=com.atlassian.greenhopper.service.rapid.RapidViewHistoryService))
&projectRapidViewService of type (&(objectClass=com.atlassian.greenhopper.service.rapid.ProjectRapidViewService)(objectClass=com.atlassian.greenhopper.service.rapid.ProjectRapidViewService))
&rapidViewQueryService of type (&(objectClass=com.atlassian.greenhopper.service.rapid.RapidViewQueryService)(objectClass=com.atlassian.greenhopper.service.rapid.RapidViewQueryService))
It was loaded from /home/jira/atlassian/test/jira-sw/jira11/11.0.0/jira/atlassian-jira/WEB-INF/atlassian-bundled-plugins/jira-mobile-rest-6.0.1.jar
'com.atlassian.jira.jira-atst-healthcheck-plugin' - 'Atlassian Jira - Plugins - ATST Health Checks' failed to load.
Cannot start plugin: com.atlassian.jira.jira-atst-healthcheck-plugin
Unable to resolve com.atlassian.jira.atst-healthcheck-plugin [47](R 47.0): missing requirement [com.atlassian.jira.atst-healthcheck-plugin [47](R 47.0)] osgi.wiring.package; (osgi.wiring.package=com.atlassian.troubleshooting.api.healthcheck) [caused by: Unable to resolve com.atlassian.troubleshooting.plugin-jira [173](R 173.0): missing requirement [com.atlassian.troubleshooting.plugin-jira [173](R 173.0)] osgi.wiring.package; (&(osgi.wiring.package=javax.ws.rs)(version>=2.0.0)(!(version>=3.0.0)))] Unresolved requirements: [[com.atlassian.jira.atst-healthcheck-plugin [47](R 47.0)] osgi.wiring.package; (osgi.wiring.package=com.atlassian.troubleshooting.api.healthcheck)]
It was loaded from /home/jira/atlassian/test/jira-sw/jira11/11.0.0/jira/atlassian-jira/WEB-INF/atlassian-bundled-plugins/jira-atst-healthcheck-plugin-11.0.0-m0002.jar
The second EAP release of Jira Software 11.0 and Jira Service Management 11.0 is ready for testing.
