I have a small CLI script that runs JQL `text ~ "$1"` (with per-repo filters on project/component).

I don't have to switch to the browser most of the time!

I've always thought I was the only one experiencing this and felt like I was crazy.

I guess it's "good" to know that I'm not alone.

The amount of times I've searched for a ticket that I know it's there (because I either have it opened in a different tab, or because I just created it), but can't find, it's just way to many.

The results usually seem completely random to me. It's like the feature never made it out of proof of concept territory. The only advantage of all the email noise Jira sends out is that I can usually search my email for what I'm looking for.

I've used JIRA back in 2009 and that is exactly what we did to work around shitty search function in JIRA.

I always got sad when I create a ticket and I see the "ticket created" toast, and then I'm like "oh shoot I forgot to add a screenshot" and go to click the toast to go to my ticket but the toast disappeared. Because then I know that I'm gonna waste the next five minutes of my life looking for it.

FWIW Github has similar shitty search interface. Not sure why.

YouTrack's search is one of the main reasons I use it. Nice query language to filter down on any fields, including custom fields, never had an issue finding things. It's great. With the number of useless search functions in so many products, I'm happy that at least my issue tracking does it right.

Half the time I just grep the ticket key in Slack because it's faster than using Jira's own search.

ironically it's the one place where an agent might be of some use and they created one and it's terrible.

at least they didn't break their pattern of disappointing users. consistency is key.