It become a problem when a PM gets his hands on it, included about 50 steps with manual approvals etc.
There's arguments to be made on both sides, and there's never just one answer. Default JIRA flow for some people is probably a godsend compared to what they're coming from, and yes, for other operations, having it mimic what's already in place probably needs to be done.
I actually joined the company just as they were about to move to Redmine, and recommended Jira instead after playing around with the Redmine test instance for a while. They were worried about the cost though, and I didn't have much say yet, but in the end switching to Redmine was the best argument for getting Jira. I didn't even have to push for it - after a few months my manager came to me and said he'd already got the funds approved!
Last few years we use Redmine mostly. In the beginning I had mixed feelings about it. Now I'm OK with it.
We sometimes need to switch to Jira in our projects. It's always a pain nowadays. I used to love Jira time reports, now I just don't get them.
My perspective: Redmine covers the basics we need, don't have the feature creep problem and does reporting (time reporting) really really well.
Rant mode continued: In several projects we use YouTrack [0]. Initially I was very excited: e.g. great UX etc .. But! It's time reporting capabilities are just rudimentary.
In the end we do the following: created internal tool too fetch time reports from different systems and to push to our Redmine system (via REST API). Redmine serves our reporting needs well. Still, in some extreme cases also use excel via ODBC..