[pcl]

Bear in mind that Jira is hugely customizable. So, saying "I use Jira" is more like saying "I drive a Ford" than like saying "I drive a Mustang."

Your experience will depend on the plugins you've installed, how you've configured custom fields and workflows, your org's SSO policies, the hardware you're deploying it to and how well you keep it up to date (if you're deploying on-prem), etc.

[taneq]

"Customizable" is a two-edged sword. The ultimate in customizable software is an assembler - you can configure it to perform the function of literally any software possible! But its utility at solving any fixed problem is very low.

The purpose of software is to specialize hardware to perform a required function. The more configuration is required to do this, the less overall value the software provides for that function.

As a software designer your job is to maximize the sum of that value across all functions that you support. As a software consumer, though, you just want the least possible configuration to perform your required function.

[lox]

Unless part of the reason you dislike Jira is that customizability.