Jira's web interface I can live with. I've internalized the workaround for the UI bugs and I've learned to live with the slowness. Sure it reflects all the wors

Jira's web interface I can live with. I've internalized the workaround for the UI bugs and I've learned to live with the slowness. Sure it reflects all the worst aspects of your organizations structure and process but that's not really it's fault. What is it's fault is their REST API. In theory it's a well architected API. Follows REST principles. You can tell they read the whitepaper. But you have to jump through a ton of hoops to get any data beyond surface details. Example: Want to find what epic a User Story is part of? It's a custom field. Which one? depends on how your instance has evolved over time. You'll have to scan through all the fields to find the field id. This is what happens when an API isn't designed to fulfill a particular need but instead is meant to be infinitely customizable. Ergonomic APIs are impossible.