Affects: N/A

Some of Spring's issue tracking has recently moved from Spring's Jira instance to GitHub. I'm afraid this brought a grave display issue, which affects https://github.com/spring-projects/spring-data-jpa/issues/2085 , https://github.com/spring-projects/spring-data-commons/issues/2458 and more. One way to reproduce would be to go to the issue tracker of an affected project and add to the search query a word part of a closed ticket's title, then launch search (press Enter). For example, on Spring Data JPA's tracker, add "hints" to the text field. You will get a result like the following: Spring ITS search

This lacks ticket #2085, even if it has that term right in the title:

5.3.9. Applying Query Hints unclear about JPA query hints [DATAJPA-1790]

This false negative is in fact caused by a default search criteria which can be seen in the input field's default value:

is:issue is:open

"is:open" excludes closed tickets.

Unless this is the result of a misconfiguration which can be fixed simply, I would recommend at least halting migration.

Most of this was already reported in #27532, but the scope of the bug is not actually restricted to search. This is in fact a general display issue, as can be seen in the numbers displayed in the "Issues" tab. For example, as of now, Spring Data Commons displays a count of 186, when it should display 2070 (186 + 1884): Spring ITS

This ticket

Needless to specify, in order to workaround #27532, thank you for not setting this ticket to closed until this is fixed.

Considering the gravity of this issue, #28692 and the stage the migration has reached, please either solve this immediately or "pin" this ticket.

Comment From: Chealer

@rstoyanchev : As indicated, this bug is about default behavior (at least regarding search), so indeed, they are not completely ignored, they are "just" ignored by default. Yes, the effect on search can be worked around (and quite easily once one knows how). What makes this so critical is perhaps that this default behavior is far from obvious.

Comment From: snicoll

Please stop creating these. You're wasting both our time and yours.