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.
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.