It’s almost as if the PM is the problem instead of the solution.
I also wouldn’t be so quick to condemn the PM. I’ve seen plenty of developers insist on complex workflows and custom fields because they think they can automate everything, only later to realize they’ve created a second job. The problem is basically the lack of a functioning feedback mechanism to ask “do we need this enough to pay for its care and feeding?”, and I’ve seen people from every role on either side of that, although it’s certainly more common to see business people underestimate the complexity of what they’re asking for.
I think this is a factor of their days being filled with busywork (from my perspective), so naturally the dev should have time enough to do all that during the day as well. The people asking you to fill out all those fields are not the ones actually doing so (or their entire job is filling them out).
(This is the same failure mode as many Agile-as-practiced projects have: once the incentive structure is decoupled from results, someone will have a full time job moving tickets around in a way which is considered productive even if the project is foundering.)