Why Jira Sucks
11–20 of 530 posts
Re: Why Jira Sucks
#12All I want from Jira is to allow me to use Markdown.
Re: Why Jira Sucks
#13> When the users need the features from Jira and request them to configure the plugins for many application scenarios, which contribute to the overall complexity of UIs.
Becomes
> When users need features from Jira they request plugins, which contributes to UI complexity.
Not a criticism - just thought this might help!
Re: Why Jira Sucks
#14What would you have us use instead? Trello?
Re: Why Jira Sucks
#15Great article. As you are likely not native English, just as a tip you can actually simplify a lot of statements by removing the word ‘the’. As one example: > When the users need the features from Jira and request them to configure the plugins for many application scenarios, which contribute to the overall complexity of UIs. Becomes > When users need features from Jira they request plugins, which contributes to UI co…
Re: Why Jira Sucks
#16Every bullet point says "Missing...", but I feel like the main issue about Jira is that it has waaay to many features, and that it's super slow! The only bullet point I do agree with, is that Jira is missing an easy (or IMHO a minimalist / simple) interface. The tool is a mess, and the people using it are probably also using it in the wrong way, making the whole situation way worse. Don't get me wrong, I like Jira to…
Re: Why Jira Sucks
#17Every bullet point says "Missing...", but I feel like the main issue about Jira is that it has waaay to many features, and that it's super slow! The only bullet point I do agree with, is that Jira is missing an easy (or IMHO a minimalist / simple) interface. The tool is a mess, and the people using it are probably also using it in the wrong way, making the whole situation way worse. Don't get me wrong, I like Jira to…
The interface used to be simpler and less in the way of getting things done. Then they added personas, UX and tried to "help" the user. You now need more clicks to accomplish the same stuff while information is more hidden than before also. There's no way to cater every possible workflow without feature bloat. However, the space is ripe for simpler, more accessible solutions that supports work across multiple project…
Atlassian products are all like this, and each one is a horrible trash fire.
Confluence is the worst wiki product I've ever used. Gross syntax, slow, clunky plugin system, awkward permissions. Install MediaWiki and be done with it.
Bitbucket is slow and feels like it's from the 90s. It doesn't seem to do multithreading well - sometimes force pushed branch rebases pick up a new, unrelated author. A bug that hasn't been fixed in years, and only one of many. How many times will merging not actually work?
Jira is a special kind of hell. It's like every team needs their own embedded Atlassian solutions engineer to get it into a usable state. Not an EM or PM, but a specially dedicated role just to deal with Jira nonsense. Why even bother?
Atlassian is like Salesforce for business process, but if it were written by all-remote temp contractors churning through Jira tickets themselves.
Re: Why Jira Sucks
#18Agreed it is now far too complex and the cloud version appallingly slow. I no longer recommend it to anyone.
What would you recommend now?
Re: Why Jira Sucks
#19Re: Why Jira Sucks
#20What would you have us use instead? Trello?