JIRA's Search is far worse than the regular JIRA hotkeys. The Enter key will incorrectly tab-complete JQL just before executing the search. Meanwhile, the Tab key doesn't tab-complete and instead focuses the Search button (which lets you execute the uncorrupted JQL). You have to actively train yourself out of how everything else works just to avoid going insane. Well, that or use the mouse just to click Search (eww).
Every ticket tracking system sucks. Trello was the closest thing to joy.
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?
Its curse, is its developed by Atlassian. A company that was capable of buying Stash, and, somehow, somewhat, turned that codebase into what we now know as bitbucket.
When BitBucket was acquired they were cloud only, and when Stash launched it was on-prem only. We used Stash and BitBucket Cloud around that time at the place I was working and I can definitely tell you that on-prem Stash was definitely not a reskinned on-prem BitBucket Cloud; for one I’m pretty sure BitBucket Cloud was written in Python (Django) and Stash was a typical Atlassian Java product.
The best part of Jira is because it is so flexible, no matter how your process slightly deviates from a basic trello-like board, you should be able to make one or two adjustments in JIRA and have it reflect that.
That's not true of literally any other workflow piece of software I've used, and I've used a ton.
That said, because all the other types of workflow management software I've used are significantly more opinionated and limited, they also limit how bad of a process a bad project administrator can create in them as well.
Absolutely this. I grew up working on an FRC team that used Trello, and I think we got more done as high-schoolers than most modern Agile teams could.
Aside from auto-complete searchbars, I think UI functionality peeked in the mid to late 1990s.
Ever since then designers have decided that looking cool is better than being easy to use and it’s been shit.
Naturally tumblr isn't one of them.
They have rather more docs than you'd expect, the big problem seems to be that nobody expects them to have useful documentation so it often doesn't occur to us to look - hence why I figured it was worth posting it for people who didn't know about it yet.
Like I say, the big problem here is 'realising that googling "$site keyboard shortcuts" actually has a point in the first place' - hence why I tell people about '?' any time I think it might be useful :D
Most commands anyway. I'm looking at you, netcat
Not really though. Some command in the distant past once told me that I need to type /? to use the correct parameters. And then another one told me that /? is invalid, I need to type --help for help. And thus, I was aware. Contrast this with youtube, which I use for 10+ years now, where I have 500+ videos sorted into playlists, and I even know some shortcuts - discovered mostly by accident - and never once saw the "?" help page, until I read this hacker news thread.
Anecdote, I know.
Either way, even an extremely imperfectly honoured convention is better than no convention at all.
Also a lot of web-based code editors override the standard Ctrl/Cmd-L shortcut ("go to URL bar") to mean "go to line". It's nice having IDE-like affordances, I guess, but not when it interferes with the basic functionality of the browser.
I get why the hotkey scourge came about, because folks are trying to build apps on a platform that isn't actually a platform. Browsers provide some but not all of the facilities of a real operating system (I'm using "operating system" here in the larger sense of "an integrated software platform that includes a complete toolbox a la Windows, macOS, etc."), so everyone's forced to reinvent square wheels. But understanding it doesn't make the experience as a user any less painful. And although I very much prefer to be able to work from the keyboard whenever possible, hotkeys as they exist on the web today ain't it. They're inconsistent, undiscoverable, and aren't integrated with fundamental UX principles like "don't destroy the user's work" and "let the user recover from mistakes."
PLEASE STOP making the web terrible.
This would make a lot of careers obsolete though (and even entire companies - I'm sure there are "newsletter popup as a service" startups). It's hard to make someone understand something when their paycheck depends on not understanding it.