Ask HN: How do you track issues, todos, features?
For the past few months building our app, we’ve used BugHerd for three main purposes:
1. Tracking issues
2. Posting to-do items
3. Noting new features
BugHerd is great for client websites, but we feel like it’s not quite right for a more long-term build.
Specifically, our lists get so long (we have a few hundred items in the Backlog) that it becomes difficult to find certain issues. Plus, organizing them isn’t that smooth.
I know some use Jira for this sort of thing, but it feels pretty old-fashioned. And, I know there are many other products, but researching all of them seems daunting.
So, I’m going to cheat, and ask: What do you use? Why? Do you like it?
77 comments
[ 5.1 ms ] story [ 163 ms ] threadI'd like to get an idea of what I'm signing up for before I commit.
Been mulling around making a vim plugin like vim-flake to put the todos into the quickfix window on :w
Currently using Pivotal Tracker after coming from a Jira shop, and it's awful. Others seem to like it, but it's too simplistic for my taste. Even something as simple as "A blocks B" isn't possible, and seems to be by design.
If you have an external system for your features (we just use a google docs roadmap) and immediately triage bugs (will fix next sprint, or won't fix), it works great. Lots of discipline required, though, and it takes some understanding of their specific approach before things start to make sense.
For a larger project I use GitHub issues with tags.
I even wrote a Vim syntax plugin for the todo files: https://github.com/tomswartz07/vim-todo
[1] http://phabricator.org/
For instance, I'm the sole developer of my web backend, iOS and android platformy thing and while android studio has good TODO: Integration sublime and Xcode require plugins, it would be awesome to have something that looks at all three repositories and tells me where i have scribbled a TODO: somewhere; or even just for comparing the different method names of my app across platforms -
Perhaps someone knows of some such tool already out there that does this?
There is a 'TODO' tab that shows you all 'TODO's in your project directory. Like so: http://i.imgur.com/TW4jXN8.png
Also, whilst I could do it on the command line, or can do it in each particular development environment (with the right plugins), I want some global overview of the whole shebang
It takes the usual kanban approach that Jira and Trello use, but is contained in a no-nonsense html5 friendly, mobile friendly website. No complaints, free to start, and premium features aren't costly if you need them.
http://www.fogcreek.com/fogbugz/
It could be fun to have a global online poll to see who's using what, to know which tools are the most popular, just out of curiosity.
I've come to conclude that no tool for this will ever satisfy everybody's needs perfectly. Part of that is that everyone has different priorities for their task tracking tool. And frankly, some of those priorities are directly contradictory. What's trackable and detailed to a project manager who lives in the task tracker is heavyweight and clunky to an engineer who sees it as a bookkeeping annoyance. My personal todo.txt is exactly me-focused and only changes when I want it to, but it scales to exactly one engineer.
I think you just have to pick something and use it. Changing tools just adds friction and costs you familiarity. Ideally, the people who have to interact with it the most choose the best tool for them.
For family stuff (eg: shits that has to be done before we go on holidays) we've been using Google doc which allows concurrent access all sort of devices.
I don't use Google doc for my personal list because I'm still more efficient at whacking text in vim. I need evil mode for Google doc :-)
https://news.ycombinator.com/item?id=10610840
This used to be our workflow too and we built Devarist for exactly this purpose.
I've also heard this argument if you're running a product, though I'm not sure how on board I am with it: don't record user requests. The important ones will be requested enough that you'll remember it.
I direct all feature requests go on a list that CS owns and we review it with our customer team, vp eng, myself and qa in a weekly meeting. We talk about the problems, get shared understanding and we collectively agree if we can say "not now". "Worth looking into". "This is easy let's do it now". "This could be tough or easy - needs more info". This is basically what partly feeds a short backlog (~20 items) that gets prioritized during sprint planning. Plus longer term roadmap stories.
Roadmap - a ppt with: Next 3 months (most detail) Next quarter (high level, use cases identified) Next Half (broad themes)
For a team, it's probably not what you need though.
For the free software projects on the web I'm familiar with, many use Bugzilla to deal with issues and feature requests. Also popular, although a little less so, seems to be Trac. They are all over the web - http://bugzilla.redhat.com is one example for Bugzilla, https://core.trac.wordpress.org/tickets/latest an example for Trac.
[0]: https://taiga.io/