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

Jira Development Jira Data Center
1

Hi, Developer Community! :wave: The first EAP release of Jira Software 11.0 and Jira Service Management 11.0 is ready for testing.

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

To find out more about this EAP release, check out Preparing for Jira 11.0.

If you have any comments, post them below.

Happy testing,
The Jira Data Center team

4 Likes
2

Hi @RobertKlimkiewicz

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.

Cheers
Adam

3

Hi @RobertKlimkiewicz ,

the EAP does not start for us, we are using you docker images, error message is:

ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND

Best,
Christopher

4

Hello @chrschommer ,

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.

Best regards,
Raphael

1 Like
5

Thanks for the feedback @adam.labus . Do you see this issue in custom apps that you have or does it occur in every toggle components we have?

6

Hi, thanks, it looks better but still does not work

Warning  Unhealthy  15m (x10 over 15m)  kubelet            Readiness probe failed: Get "http://10.2.32.96:8080/status": dial tcp 10.2.32.96:8080: connect: connection refused
7

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 ?

8

Hi @bcinarli

from what I have observed, this applies to all - I uploaded two videos, toggle doesn’t work in both cases when it is turned off - Index of /jira11

Example .VM

$webResourceManager.requireResource("com.atlassian.auiplugin:ajs")
$webResourceManager.requireResource("com.atlassian.auiplugin:aui-toggle")

<html>
<head>
    <title>test</title>
    <meta name="decorator" content="atl.admin"/>
</head>
<body id="jira" class="nl">
<script nonce="<nonce>" language="JavaScript" type="text/javascript">

    AJS.$(document).ready(function () {
        var toggle = AJS.$("aui-toggle[id='gzip-compression']");
        toggle.change(function () {
            if (toggle.checked || toggle.attr("checked") === "checked") {
                console.log("gzip-compression - CHECKED");
            } else {
                console.log("gzip-compression - NOT CHECKED");
            }
        });
    });

</script>

<div id="main-content">

    <form action="" id="formConfiguration" method="post" class="aui">

        <aui-label for="gzip-compression">Use gzip compression</aui-label>
        <aui-toggle id="gzip-compression" label="use gzip compression"></aui-toggle>

    </form>
</div>

</body>
</html>
9

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");
            }
        });
    });
1 Like
10

Thank you, this solves my problem :slight_smile:

1 Like
11

Do the links in README.TXT start working only when it is out of EAP and in production?

12

I am confused about database versions. The health check says

“PostgreSQL 17 is not supported. You should migrate to a supported database version.”

but the Preparing for Jira 11.0 | Administering Jira applications Data Center 10.6 | Atlassian Documentation says that PostgreSQL 17 support is implemented in EAP1. So which one is it?

Details:

select version();
PostgreSQL 17.5 (Debian 17.5-1.pgdg120+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit