We have a woman at my company whose job is to update Jira ticket statuses.
Instead of allowing the developers to update the statuses themselves, she will often prematurely update statuses from "In Development" to "Ready for QA" before any code is merged. Or she'll update a ticket that isn't yet being worked on to "In Development". It repeatedly causes a lot of confusion.
I think she feels the need to be so hands on with updating the statuses in order to justify her job, which, in my opinion, shouldn't exist.
My actual job was to make sure the tickets were clear, relevant and ready to work on (as opposed to a stream-of-consciousness wishlist from managers). I gathered requirements, represented the devs in planning meetings, cleared their hurdles and QA'd their work. I was basically a prep cook for the devs.
I work with someone who has that job. The stream of consciousness is much preferable. I need to know the big picture, not some distilled set of requirements. Give requirements and I will spend half my time trying to "reverse engineer" the big picture from them, which is a big waste. And an even bigger waste if I get it wrong. Not sure why our industry is so obsessed with obscuring information.
Although I appreciate having someone to move boxes around for me. I cry a little every time I have to go near that horrid UX.
"We have a non-binary, genderqueer, genderfluid, agender, bigender, demiboy, demigirl, two-spirit, androgynous, neutrois, third gender, polygender, maverique, hijra, kathoey, fa'afafine, man, or woman at my company whose job is to update Jira ticket statuses."
Instead of allowing the developers to update the statuses themselves, she will often prematurely update statuses from "In Development" to "Ready for QA" before any code is merged. Or she'll update a ticket that isn't yet being worked on to "In Development". It repeatedly causes a lot of confusion.
I think she feels the need to be so hands on with updating the statuses in order to justify her job, which, in my opinion, shouldn't exist.