[Bug] Difference in label search/filtering in the frontend and the backend

[Jonatan]

Hi,

I wanted to report a bug, and this seemed to be the place to do it. Please point me in another direction if this is not the correct place to be or if it has already been posted somewhere.

The background:

When adding a label to a Jira task/issue, there are two forms of filtering as you start typing in the label. The first happens in the frontend and takes effect right away (based on the labels that are already loaded). A second after that, the response from the backend filter comes into effect and updates the list of labels that is available in the frontend.

The bug:

The frontend filter searches for labels that contain your text.

The backend filter searches for labels that start with your text.

Example:

Thus, with a label structure like "feat/feature-1", "feat/feature-2", "client/client-1", "client/client-2", the frontend filter would allow you to search for "feature-2" as "feat/feature-2" includes it, but as soon as the backend filter loads "feat/feature-2" is removed from the list as it doesn't start with "feature-2".

The ideal solution

- Most importantly, both the frontend and the backend filters should both work the same way

- Ideally, they should both filter by labels that contain your text, so it is possible to search and not have to type out the label precisely as it is.