Over the weekend, our YouTrack InCloud instance updated to 2018.2 Build 42133. We came in this morning and several of our filters were broken. From testing, it looks like the queries have gotten significantly stricter and I'd like to know if the following are by-design or if this is unexpected behavior:
- Filters containing "#Unassigned" stopped working. It turned out that we had fields in various projects that had "Unassigned" as a value (or empty value) and that YouTrack got confused when doing a search like "project: MYPROJ #Unassigned" in that it returned nothing. It looks like #Unassigned was finding values in a certain field and if the specified project did not contain that field, it just returned nothing. Renaming some of the Unassigned values fixed this problem.
- We had our system setup so that the Stage field and the State field had aliases for each other. When searching for "State: Fixed", it would also return nothing when paired with a project (e.g. "project: MYPROJ State:Fixed"). This was fixed by removing the alias from Stage corresponding with State.
- EDIT: Also, when doing a find like "project: MYPROJ #Fixed" where the project contains multiple fields that contain the value "Fixed", YouTrack now seems to choose one of those fields and only return results for that field instead of returning results for any field that contains that value.
Basically, YouTrack, when not limiting searches by selecting a scope in the drop-down seems to decide what field a certain value belongs to and even when specifying a certain project, the correct field/value combination for that project is not used.