It's no specific feature it's the fact that large enterprise requirements very often translate into a product that isn't very pleasant to use.
Jira allows for a very rigid, formalised process for everything to be built. Few companies resist the temptation, most go all in while chanting "compliance, compliance, COMPLIANCE!" and as a result you have an environment that is a pain to use, has too many mandatory fields everywhere, one allowed status transition workflow (or one per issue/content/whatever type)- it's bureaucracy as a service.
All that takes a lot of time to set up and makes changes within the organisation even harder, because you have one more thing that makes it rigid.
>nunez: JIRA is a really nice product, but one's experience with it heavily depends on who "owns" it
>wwalser: the hellish existence [...] where JIRA comes up [is] because of one of three things:
· Your admin(s) set it up once and hasn't bothered to iterate on those workflows
· The business mapped their autonomy stripping processes onto JIRA intentionally [...]
· You're on an instance that is serving too many people with too few resources
source: How Atlassian Built a $10B Growth Engine | https://news.ycombinator.com/item?id=16052743 (2018Jan:226 points,170 comments)