Also affects the main project pages, such as
https://bugs.openjdk.org/browse/JDK
Since there has been no response so far on web-discuss, and also
apparently no response to another feedback mail I had sent to
[email protected] 3 weeks ago regarding the new bug
reporting form (where feedback was explicitly requested), I am going to
include [email protected] now on CC (hopefully that is ok).
Also, another issue with the new bug reporting form
(https://bugs.java/bugreport/):
It seems you do not get the "Update Notification: Bug Report - JDK-..."
mail anymore which informs you about the creation of the bug report
(unless I made a typo in my mail address when submitting the report)? I
can see on https://bugs.openjdk.org that the report was created a few
weeks ago already.
Sorry in case this missing communication is just due to the holiday
season. Though web-discuss seems to be rarely looked at in general (but
it seems to be the most appropriate mailing list for this topic).
Am 27.11.2025 um 11:30 schrieb
[email protected]:
Hello,
it seems since a few weeks or months the JDK Bug System
(https://bugs.openjdk.org/secure/Dashboard.jspa) requires login when
searching for issues.
To reproduce:
1. Open https://bugs.openjdk.org/secure/Dashboard.jspa
(make sure you are not logged in)
2. In the top right, enter any text in the search text field, e.g. "test"
3. Press Enter to search
(note that the search text field already provides suggestions,
ignore those)
Problem: Instead of opening the results list, it shows the login page:
https://bugs.openjdk.org/login.jsp?permissionViolation=true
This is quite inconvenient for external users who don't have an
account, and likely also leads to increased amounts of duplicate bug
reports.
If possible, could you please fix this?
Tested browsers:
* Firefox 145.0.2 (64-bit)
* Chrome 142.0.7444.176
Workarounds:
* Instead of pressing Enter in the text field, click the "View all
matching issues" button at the end of the suggestions list
* Open https://bugs.openjdk.org/issues/ and perform the search there
instead
But these workarounds might be a bit difficult to find if a user is
not that familiar with Jira, or was not aware that searching did not
require a login in the past, giving the impression that you cannot
search without account.
Kind regards
