I don't get Jira hate. It may be clunky, slow and overcomplicated but really it's just system to document stuff. If you don't document stuff on a sufficiently big project (I'd day >10 engineers, and especially at >100) then it's a recipe for a disaster.
As for solutions to document stuff, specifically issues, then Jira seems to be ok and not lacking in any area, maybe not a leader but not a worst thing to use too.
> I don't get Jira hate. It may be clunky, slow and overcomplicated
Ding ding ding!
Seriously though, I think a lot of issues with Jira stem from poor implementations that cause it to perform terribly, which impedes an engineer's ability to quickly get in and out of Jira. For example, the on-prem Jira instance for one of my clients would take upwards of five minutes to render the board, and another 30+ seconds to render the ticket page. Adding comments was another frustrating experience. I'm sure the OOTB experience with modern Jira is probably fine, but it seems that hardly anyone uses Jira without some resource-intensive customization.
What is needed is registrars keeping track of documents and writing summaries etc. I blame the 'savings' on secretaries for many of the modern corporate worlds problems. A tell tail of that the top brass them-self don't believe secretaries are not needed, is that they them-self have them. It is just engineering that can't have them - pushing any bigger engineering org. into chaos.
As for solutions to document stuff, specifically issues, then Jira seems to be ok and not lacking in any area, maybe not a leader but not a worst thing to use too.