HN Explorer

What project management / issue / ticket managent tool do you use?

4 points by mattwritescode ↗ HN
I am researching some alternatives to trac for my team. What project / ticket / issue apps do you use and why do you like or dislike it.

We are a team of 15 looking for something which is easy to use and track work loads.

13 comments

[ 3.2 ms ] story [ 43.3 ms ] thread
AngeloR
Like: Fogbugz (small-ish team), Trello (small team)

Don't like: Jira, Whiteboard (like.. literally a whiteboard)

Want to try: Zenhub

ljk
what don't you like about jira?
andymurd
We use JIRA at work, and there are good and bad aspects.

My biggest peeve is that management always want to configure it to do time-tracking. This makes engineers hate the tool and lie to it, making it useless for bug tracking.

drakonka
Fogzbugz looks homey and adorable and I just registered.
kvcrawford
I'm using Zenhub at my current company. I preferred Pivotal Tracker, which we used at my last company. It just feels kind of janky overloading Github's website.

TBH, though, I struggle to find any other meaningful negative differences.

lokio9
Basecamp
jesseg17
I'm not a big fan of Basecamp. I find lack of support for code snippets and specific issue tracking make it inferior to GH Issues and Trello.
warewolf
Trello - Color coding on priority, fast notifications and easy to use.

Slack - Quick communication and easy integration to other apps/tools

MalcolmDiggs
Asana - Easy for non-technical folks to grok, all the features I need for non-coding projects (like a marketing project for example)

Pivotal Tracker - More technical features specifically for software development, steeper learning curve, good bug tracking.

Slack - Good for office-wide communication. Easy to use for everbody.

Bugherd - Bug tracking system which integrates into the user-facing components of your web-app. Makes gathering feedback/bug-reports from the public very easy.

romanr
hiTask.com - manage tasks, projects in a team, your way.
andersthue
Do you use a special methodology (agile/scrum/timeblock) and need something to fit that or are you running your project ad-hoc?

If it's a case of the latter then I would advise to look into adopting a methodology and a systemized way of working before locking yourself into a tool.

In my experience there is a big correlation between using a methodology and having a solid foundation to build a solid business.