2 ms·
Gitlab is another culprit for this and their UI/UX is growing to be as awful as every other complex enterprise tool on the market. The search/filter box on the
by ljm 5y ago
Gitlab is another culprit for this and their UI/UX is growing to be as awful as every other complex enterprise tool on the market.
The search/filter box on the MR and Issues list has the appearance of accepting free input, but what you need to do is use some ridiculous no-code query UI to click your way to a valid query.
I can't type 'author: xxx' into the field, because that will tell me that searching that way is unsupported (so why let me do it?). Instead, I have to start typing, select the word 'author', then another box will appear and I have to select '=' in it, and then a third box will materialise where I can search for a username. At this stage, it's basically a coin toss as to whether you get the desired input or the whole form breaks and you have to start again. Someone, somewhere, thought this was more intuitive than parsing a string or offering some predefined filters.
My only question is: why?
- nyanpasu64 5y agoIt's out-of-band signaling which eliminates the ambiguity between searching for "author=" and searching for an author. It's still probably bad user experience. I'm not sure if it's justifiable, given how GitHub code search mostly ignores punctuation (whuch I hate too), whereas GitLab seems more literal.
- ljm 5y agoIt's specifically related to finding authors of merge requests, or issues, rather than a generic code search.