History search for status can break when next-gen repeats classic status names

Issue Summary

The JQL search for historical entries (i.e: "status was in (done)") breaks when there are multiple statuses with the same name (possible due to Next-gen). From our tests, the search only consider the one status with the highest position from the Status configuration page (next-gen statuses also have a position in the backstage but these are hidden from the page)

Steps to Reproduce

1. Create a next-gen and classic project with a repeating status name i.e: "To-Do"
2. Create issues and transition them to and from the status done (so we can have a history entry)
3. In the Statuses configuration page move the done status to the bottom of the list (to ensure that NG statuses have an upper position behind the scenes)
4. Perform a historical search (i.e: status was in (done))

Expected Results

• The search would return both the NG and the Classic issues, considering only the status name

Actual Results

• The search will only return issues from the project from which the "Done" status has the highest position. In this example, since we moved the Classic status to the bottom, it wouldn't return its issues.

Workaround

• Change the order of the statuses on the page, but it can break this for other projects.
  Or,
• Use the status Id, instead of the status name in the search.