4 ms·
Problem with Jira: Its customers are not its users. My past managers had a great time with Jira. But if I have to migrate or create tasks in Jira the only eff
by eftychis 4y ago
Problem with Jira: Its customers are not its users.
My past managers had a great time with Jira.
But if I have to migrate or create tasks in Jira the only efficient and effective way I have found is paying for a desktop license. It doesn't suck -- that much.
Otherwise, it is a destroyer of productivity for its users. It is also a source of lock in, that is usually unnecessary.
I find Github projects to cover most if not all of the needs, for instance, in an efficient manner. Most managers though also don't/shouldn't care about the micro tasks of a project, so an excel sheet has done that job.
The consequence of who the Jira customer is, is its lack of efficiency and chaos. It is too customizable and fails to preserve any form of usability to offer that customizability. I have seen Managers being joyful of achieving the "ultimate Jira," only for everyone in the team to have to learn to abide by the new process, only so that 1-2 people can keep track of tasks and velocity without hitting github or gitlab.
You get great statistics, but if I have to spend 1/5 of my workweek on petting Jira, you lose that.
Managers love Jira, that is why it keeps coming up.
You need one new manager to come in, say they know Jira, and using it will solve all of the company's velocity issues, to end up with people writing articles of how they hate Jira.