Do managers not fucking understand that Jira is meant to eliminate all this stupid "What's the status with X?", and "Is Y done yet?" chatter. Our communication channels should be on business logic and other global updates about the company, not about fucking workflow status updates because you have nothing else to do with your day but ping me every 5 minutes.

LOOK AT THE REVIEW COLUMN ON JIRA. I MEAN ITS LITERALLY CALLED REVIEW. SO REVIEW IT AND DO YOUR FUCKING JOB.

I swear the devs consistently have a better overview on timelines and project status than management does - which is sad, because this is literally the definition of management!!!

Ergh. Consider Trello and Jira being kept written in technical jargon only. We need to translate from technical to non technical for other people to understand

@darkwind nag the project manager then?

Hey mate, how much longer do you think this is gonna take? We got clients waiting for this y'know.

@darkwind That sounds more like a preference.

Devs already got a comprehensive taxonomy, so if it doesn't suit managers' cup of tea, guess what... Pay monthly for non-technical ticket system that will suit only managers. Or ask your devs to invent Managerese locale (en_MA) for existing self-hosted system, so everyone can be happy.

Jira is, most of the time, way too complicated for the "mouth breathers" (managers) to understand. They simply cannot comprehend the concept.

They want to use it because: "wE aRe aGiLe!!" and "EvErYoNe eLsE iS uSiNg iT".

I have given up on Jira a long time ago.

Mouth breathers will never understand, so why keep losing hair over it?

What about idle chatter while destressing in a work environment that should not be ?

People like to talk
Companies like working people till they don't need them and laying them off
Would work out if there was something that took care of the workers so how about a little inefficiency?
Besides doesn't jira suck ?

"Do managers not fucking understand" - yes.

I don't understand how anyone can think JIRA is too complicated. Let me give you a 30 second run down:

1. Click "New"

2. Add title

3. Add description

4. Select bug or task

5. Save

From there it is LITERALLY a drag-and-drop interface. I don't know how much easier it could get. Don't want to know what programs they are using a day to day work that would be easier than that.

I don't think UX is the issue, most managers know how to navigate Jira and use it. But they haven't understood the concept.

They know the "how", they just haven't figured out the "why" part.

Take ticket priority as an example, I saw a post the other day about managers putting the wrong priority on tasks, maybe it was your post.

They know "how" to put priority on tickets, but when they are assigning "SUPER EXTREME ULTRA MEGATRON PRIO"-priority on every ticket, it tells me that they have not figured out how to deal with agile processes.

Same thing with asynchronous communication, but lets not go into that.

I hope you keep your hair, stay strong.

Imagine for a moment a thought experiment.
You are in a large room with dozens of dinner tables, but otherwise empty.
On the table next to you there is a cup with a single ice cube, slowly melting. You must put a new ice cube in the cup as soon as the current one is done melting, every second the cup waits without having a new solid cube counting against you.
With a single cup, you could just leave the ice cube there and rest for a bit, knowing full well that you can see the moment the ice fully melts.
Now imagine there is another cup and ice cubes on every one of the 30+ dinner tables. Even just putting in new ice cubes is now a challenge by itself, for you have to run from table to table.
And air flow and heating variations mean that is basically impossible to predict with precision how long does each individual ice cube takes to melt.

Looking at a cup is simple enough. But still human nature would rather have each cup report on its own ice cube ASAP. Then add anxiety to the system

That is how we end up with managers anxiously requiring updates from each of the waaaaay-too-many melting projects or issues they are responsible for, and as often as possible. Also, "hustle culture" means that people who are promoted into mouth-breathing "management" positions are allergic to saying "no" to "new #challenges or #opportunities" or any other bullshit euphemism du jour for "stuff to do".

I frankly wish I knew something about chatbots to make a update-answering bot that just copy/pastes Jira statuses. Or about talking people out of anxiety attacks. That and some courage to say "no" is all that managers need.

@swagnette I hear product owner instead of manager here (as there is a claim to be AgILe). If your PO assigns super importance to everything that is the sign of a super incompetent PO. A competent PO does the exact opposite, decreasing the priority as much as possible so the highest impact is reached because the important tickets emerge.

As a team you should fire this one. Or do a demonstration in his/her office by all picking a ticket and jelling it's the most important one. Keep doing that until everything is ordered. This brings the chaos the PO creates to their doorstep.

If the conversation is on the phone make up some big story about how the whole thing crashes and has the potential to kill handicapped children in Ghana. Then when someone asks you about it say you don't know what he's talking about but it's on the review column.

@m3ml3ak interesting how you honey in on ghana

@AvatarOfKaine it was there ot Paraguay but I didn't want to try to spell Paraguay without coffee.

@m3ml3ak prolly because this was my comment originally
Pay money lol

I'm a lead dev and I stopped using Jira in our startup because my managers (the founders) made my life hell with expectations on top of my extremely modular-responsibility role.

My work is no longer visible, and I no longer care- so I'm quitting next month (taking a vacay first lol).