Live data from Hacker News

Why Jira Sucks

whyjirasucks.com

31–40 of 530 posts

Re: Why Jira Sucks

#31
post #5

All I want from Jira is to allow me to use Markdown.

It's definitely not all I want, but that would be huge. Also in Confluence, please.

I've made the switch back to Redmine for my personal projects. By now it has full Markdown support for issues and wiki. Faster than Jira, and easier to use.

Re: Why Jira Sucks

#32
What is missing in my opinion? It is consistency between the atlassian products and/or adherence of industry “standards”

Confluence and JIRA use a different markup language for posts and none of them uses Markdown (in any flavour), which I would also use to write in-code documentation, like in a README file

Re: Why Jira Sucks

#33

Every 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…

why oh why does it have to be this sloooow ?

Re: Why Jira Sucks

#35
post #15
post #13

Great 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…

Are both equally correct?

Yes, but only one is easy to read correctly.

Re: Why Jira Sucks

#36
post #5

All I want from Jira is to allow me to use Markdown.

It has a markup language that accomplishes the same thing effectively but has a completely different syntax. This is super annoying when you are bouncing between pull requests in Atlassian Bitbucket and JIRA tickets. I have tried to create a heading with # only to end up with an at least a hundred times.

I imagine this is because JIRA (2002) predates Markdown (2004), or at least its mainstream popularity when GitHub adopted it.

Re: Why Jira Sucks

#38

What would you have us use instead? Trello?

My go-to options are the following:

- Whatever GitHub/GitLab provides if I need the most basic level of tracking.

- Trello for a more polished experience, a few additional ticket/board related features and easier involvement of non-developers.

- Linear if there's a bigger team that needs more than a bunch of boards (backlogs, roadmaps, projects, teams etc.).

Re: Why Jira Sucks

#40
1. It is dog slow.

2. It is dog slow.

3. It is dog slow.

...

When my team had an important as-quickly-as-possible sprint, we dropped Jira and switched to Google Docs as it was much easier and faster than Jira.

My conclusion was that Jira doesn't do much for developers that can't be done in some Google Docs/Sheets.

Post reply on HN