Earlier quoted context omitted.
What's wrong with hipchat?
Having recently switched from a workplace that used Slack to one that uses Hipchat, my first answer is "everything". It's less reliable, and reliability is my number one desire in a communications tool. And there are just so many little UI and UX details that Slack gets right that it's a pleasure to use, whereas Hipchat is generally an irritation and a disappointment for me. I guess one way to explain it is that Hipc…
JIRA's BDUF approach to ticketing/bug tracking pleases middle managers whose job is to spend all day clicking around arcane interfaces and finding a way to generate a report that shows their team is highly productive, but it's painful for actual doers to get in there and move stuff around, which means it rarely gets done, which means that the tracking is not very reliable, which means that the value of the bug tracker is dubious. The most important feature any bug tracker can have is that it's low-friction enough that most people will actually use it.
JIRA has tried various things to make this less onerous, including GreenHopper/swimlanes, an attempt to remake JIRA into a Trello-like drag-and-drop interface, but it just never seems to click the same way. For example, today, when I tried to move a ticket in JIRA from the "New" swimlane to the "Done" swimlane, I got a "WORKFLOW EXCEPTION".