Unpredictable results for filter queries referring to duplicated filter names

Description:

When two or more filters that have the same name are visible to a user, a query on 'filter="<filtername>"' returns mixed results from all filters.

According to JRASERVER-18035, this is the design intent. But it means that the results of the query are unpredictable, depending on actions by other users. If initially, my own filter is the only one by that name or the only one I can see, I get one result. If another user creates and/or shares a filter with the same name, suddenly my query returns different results.

JSWSERVER-20872 suggests one way of resolving this issue, by requiring all filter names to be unique across the instance.

Attached to this ticket, there is a screen recording video demonstrating the problem.

Proposed Solutions:

Make filters names unique such as the filter IDs are.

Another approach that would reduce the instances of undesired results but still allow the "feature" in cases where people want it would be to treat filters the same as Sprints, which is another case where there can be multiple objects with the same name. If you select a Sprint from the autocomplete list or click enter after typing the full sprint name, the Sprint id is populated into the query, instead of the Sprint name. You can still force the filter to reference the Sprint by name if you want, but in the majority of cases, the Sprint name is converted to the ID as the filter query is being written.

If this was done for filters, most filters would end up referencing other filters by id instead of the name, which would give predictable results regardless of the actions of other users.

This approach would require changing the autocomplete behavior for filters in queries to match Sprints. Looks like it's currently doing the same search as Search Filters (without quotes), which means it's hard to find a multi-word filter name in the list to select it.

Workaround:

Instead of using the filter name in the search, use the filter ID.