Atlassian's documentation isn't that good however.
That's the fundamental problem. Jira is sold to PMs and managers, not to developers, and it shows. Jira isn't an issue tracking tool, it's a work-tracking and developer-tracking tool masquerading as an issue tracker. The people who spend the most time with it aren't the customer.
I think this actually might be a fundamental issue that is masquerading as design issues on Jira's side, because when you're doing roadmapping views you want to continually refactor them to reflect better metaphors and realities, whereas when you're doing issue tracking you want issues to stick around and be solid entities linked intimately into the history of the software application. So tools like Portfolio have to juggle both ends.
When you're working with Python, Jira will render __init__.py as an italicized version of _init_.py even when you put it in monospace with the {{braces}}. If you're talking more abstractly about algorithms, O(n) turns into the letter O followed by the thumbs down emoji.
It's a good thing no one uses Jira for software projects because that'd be really awkward!!!
A non sane place would have 20 obscure mandatory fields per ticket, require the ticket to go through 10 different states that makes no sense, and last but not least, every click would take a full minute to load the page.
Collaborating over JIRA on a video conference is PAINFUL AF. A lot of time is spent just waiting for the UI to respond. It is completely unacceptable.
I'm not a PM and I don't really want to get to know the ins and outs of an issue tracker.
Also, looking at my project is a pain since my tickets are outside the sprint and I either need to go into the backlog and scroll a bunch, or use a custom search.