4 ms·
Don’t mean to create a pile-on, but since you asked, yeah I should explain my barb: Is Jira a UX disaster because of just that? Or is it bad on top of
by mik3y 7y ago
Don’t mean to create a pile-on, but since you asked, yeah I should explain my barb:
Is Jira a UX disaster because of just that?
Or is it bad on top of that?
My opinion - it’s both.
The product has a ton of permutations, as you said, which makes stuff like this happen: Customers who never in the world imagined public issue tracking, suddenly bit by a feature they didn’t even know existed. Conversely I’m sure there are shops, who love this feature, for whom the distinction between “Everyone” and “Open” was always obvious. I don’t envy the team building / supporting the product across all that; I don’t know how I’d do it.
But there are also endemic, continuously-poor design choices large and small. Unannounced and hard to disable major changes to the UI are the standard, and large. I’ll give you one example of the small: Recently, unannounced, the issue comment UI started auto-correcting the capitalization of Atlassian product names in the comment box. Type “JIRA”, get “Jira”. In my words in my issue tracker. (Yes, it was the js app, not the browser). It just always seems so user hostile.
Net net, to me it’s an aging hydra of a product with ongoing missteps. I’d take good design and limited features over what you get here, at least with out heavy investment and expertise.
- the_duke 7y agoNot to mention that it's unbearably slow.
- bragh 7y agoI think it is caused by Atlassian changing their branding: since most people did not bother to capitalize 'JIRA', they branded it as 'Jira'. By the way, I am on an older version of Confluence and it autocorrects the other way: 'Jira' to 'JIRA'.
- wpietri 7y agoThanks! This is exactly what I wanted to know. And now that you describe it, I suspect it's inevitable that anything bad in the first way becomes bad in the second. If the purpose and the use cases are clear, that can guide good design. But if the product is too complex for mere mortals to understand it, then of course the teams building it will eventually turn it into a frankenstein collage of UI issues.
- ownagefool 7y agoI tend to agree Jira is a bit of a mess, but the responsbility needs to be shared with the users. - Why buy a complicated mess? - Why let a random Scrum Master / Product Owner manage it? - Why don't we think we need to protect an IT system we buy like an IT system? Many of the reasons engineers hate Jira are specifically related it being a complicated mess that is hard to use and admin. So if management would listen to engineer about IT systems, maybe this wouldn't happen? Another possibility is we actually did a risk assessment and what we put in Jira isn't of sufficent risk for us to care, so actually IT doesn't need to be involved because we're not super worried about it leaking. There are likely worlds of both involved. My own pet hate is just that it's too slow and often configured in a convoluted way that makes me spend too much time in it.