Skip to content

ITS: SEARCH IGNORES TICKETS TRACKING OUTSTANDING ISSUES BY DEFAULT #27532

@Chealer

Description

@Chealer

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 issue with search, which affects at least Spring Data JPA ticket #2085 and Spring Data Commons ticket #2458. 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:
image

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: declinedA suggestion or change that we don't feel we should currently applystatus: duplicateA duplicate of another issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions