81–86 of 86 posts
You can judge the quality of a project management tool based on one simple metric - when you sit down to use the thing, do you spend your time thinking about the actual content of the work items? Or do you waste time in the meta-structure of the work, effectively shuffling tickets and story points like it was a game? Jira provides endless ways to engage in useless meta-work, it's nearly the entire purpose of the UI.…
I use Jira and agree with some things on the article, but for other client I have to use Azure DevOps and please give me Jira. Also other thing from this articles "I hate [tool]" is that many people just don't like their job or are burned out, the hate may be coming also from that, not only for a poorly designed tool.
Hah, as funny as that title is, it’s not so funny that security was left off the list in the article.
> It generates amazing reports, fantastic predictions, fancy charts, great managerial tooling, makes imposing processes easier, has robust integrations, etc., and that’s why most managers I’ve spoken to really enjoy Jira, while on-the-floor engineers either range from fiery-eyed hate to toleration. You kinda need to impose process for large projects, and know where you are. The engineers are free to show a better too…
Something I think I could have iterated better in the blog post was that I believe Jira--even without all the bureaucratic processes it promotes--panders solely to higher-level management with zero regard for the ones interfacing with it: the engineers. That's the big issue I see.
I think Linear--by stripping away all the hullabaloo--continues to provide management good insight on team progress without abandoning the ones who actually use it on a daily basis.
I'm really hoping Linear continues to step up to the plate and manages to take on some of the features that make Jira a more attractive piece of software for a lot of people that are familiar with it veering Linear away from its great UI, speed, etc. However, I wonder how many people are actually picking Jira based on its merits rather than it just being what they're accustomed/used to, or simply not knowing there are other options out there.
> It generates amazing reports, fantastic predictions, fancy charts, great managerial tooling, makes imposing processes easier, has robust integrations, etc., and that’s why most managers I’ve spoken to really enjoy Jira, while on-the-floor engineers either range from fiery-eyed hate to toleration. You kinda need to impose process for large projects, and know where you are. The engineers are free to show a better too…
Author here, for the record, I never said the problem was the imposition of processes, I know that is totally necessary, and was listing great "pluses" to Jira as a management tool. Something I think I could have iterated better in the blog post was that I believe Jira--even without all the bureaucratic processes it promotes--panders solely to higher-level management with zero regard for the ones interfacing with it:…
I think we both agree that in the age of VSCode: it is unacceptable for 30+ billion dollar company to have such a sluggish web UI.
I'm an engineer and I actually feel that Jira fails me because it's not flexible enough, some examples include: - issues cannot have more than one assignee - projects cannot have multiple releasable items / components - poor Bitbucket integration
> However, I wonder how many people are actually picking Jira based on its merits rather than it just being what they're accustomed/used to, or simply not knowing there are other options out there.
I pick it still because most people will understand how it works and I am able to customise it the most to fit everyone's needs more than all the other tools out there.