Really? Maybe you need a larger company to manage things like this; but at one place where we switched to Jira we wrote integration into our GUI apps for users

Really? Maybe you need a larger company to manage things like this; but at one place where we switched to Jira we wrote integration into our GUI apps for users to create tickets (and automatically log contextual info), and created very simple "create ticket" screens in Jira itself. The best part was being able have end users open up a ticket wherever they were most comfortable and it could get routed to the appropriate department without losing any history (i.e. open a ticket because of an error message in an app, but get routed to hardware to replace a video card or driver). We went from having 5 separate ticketing systems (a few home built) to Jira. It always felt like you could abstract the complexity if you needed, but the power was there if necessary. But I have no idea what was involved with setting up and managing Jira. The last place I worked we co-opted another app and used it for issue tracking. Search and discoverability was so poor that most everyone used their email to find any tickets that weren't assigned to them. I find it weird that companies can use GitHub exclusively for issue tracking. Not just that it's so bare bones, but many of the things that have tickets aren't for a specific software project. I guess they use different ticketing systems for different departments?