3 ms·

In my previous job we used JIRA as our SCRUM board (cross teams, i.e. product, back, front, data science and design) and GitHub as our VCS. It was working prett

In my previous job we used JIRA as our SCRUM board (cross teams, i.e. product, back, front, data science and design) and GitHub as our VCS. It was working pretty well. I don't get all the bad reviews about JIRA on HN. Not saying it's the best tool ever but it does the job. I wonder if it's because JIRA is more associated to a management tool than a developers tool? BTW they made a new version (I didn't try it): https://www.atlassian.com/blog/jira-software/the-new-jira-begins-now https://www.atlassian.com/blog/jira-software/the-new-jira-be...

Karunamon 8y ago
It can be either - I find that most complaints about Jira boil down to the complainer being forced to use a system, the end users of which didn’t get a seat when it was being designed (and so the result is a bureaucratic mess), or, misconfigured and unnecessarily slow and clunky.
- beatgammit 8y ago
  That's mostly my reason for disliking it. We used Bugzilla for a while, but management wanted more integration with other services, and we didn't have anyone in house that we could spare to build it (and plugins didn't exist for it). Jira filled more of what management wanted, so we adopted it. At first, I (tech lead) sat down with our QA team and we came up with something that worked reasonably well, and developers and QA were pretty happy. Seeing the success, upper management stepped in and wanted some changes. We pushed back sometimes and made slow progress, but eventually upper management took over and started making changes that everyone hated (lots of micromanagement). However, there are a few tangible things about the product itself that I dislike, such as: - slow loading times (apparently taking a few seconds to fully load is "acceptable") - too many options for customization, which makes it too easy for management to break stuff trying to do things "the right way" (especially permissions on transitions) - can't remove states from a workflow without copying and replacing the workflow (seriously, why?) - no dark theme (I'm only half joking) I'm trying to get a feel for what people dislike about it in case my hobby project of building an issue tracker ever gets serious enough to become interesting for outsiders.

Karunamon 8y ago

It can be either - I find that most complaints about Jira boil down to the complainer being forced to use a system, the end users of which didn’t get a seat when it was being designed (and so the result is a bureaucratic mess), or, misconfigured and unnecessarily slow and clunky.

beatgammit 8y ago
That's mostly my reason for disliking it. We used Bugzilla for a while, but management wanted more integration with other services, and we didn't have anyone in house that we could spare to build it (and plugins didn't exist for it). Jira filled more of what management wanted, so we adopted it. At first, I (tech lead) sat down with our QA team and we came up with something that worked reasonably well, and developers and QA were pretty happy. Seeing the success, upper management stepped in and wanted some changes. We pushed back sometimes and made slow progress, but eventually upper management took over and started making changes that everyone hated (lots of micromanagement). However, there are a few tangible things about the product itself that I dislike, such as: - slow loading times (apparently taking a few seconds to fully load is "acceptable") - too many options for customization, which makes it too easy for management to break stuff trying to do things "the right way" (especially permissions on transitions) - can't remove states from a workflow without copying and replacing the workflow (seriously, why?) - no dark theme (I'm only half joking) I'm trying to get a feel for what people dislike about it in case my hobby project of building an issue tracker ever gets serious enough to become interesting for outsiders.