Ask HN: What are you using for project management?

I use GitHub projects/issues with the WakaTime integration, but most of my projects are open-source or the company already uses GitHub private repos.

Trello also works well alongside GitHub issues.

Currently using wheatbin to manage my various project assets. It's an open source kanban app you self host: http://wheatbin.com

Used to use Asana but finding JIRA to provide the necessary amount of structure for me to be disciplined.

I use Teamwork but plotting a jump to JIRA for more functionality.

My company uses Asana.

I've worked with multiple small teams that used Redmine. Worked fine each time, no complaints.

We use pivotal tracker which is awesome. We use labeling conventions heavily to customize for our workflows.

We use Lighthouse App. It's got just enough features for us and pretty simple.

My team comfortably uses Asana and appreciates its flexibility; but I'd rather be using Jira. Asana has one highly useful feature we never found similar functionality for in Trello: being able to assign a task to more than one project.

We use two great project management platforms:

1. Walking around asking people what the fuck is going on

2. Outlook

To wake is pain; I long for the release of death

We are using Tuleap[1] b/c flexibility and good agile support

[1] https://tuleap.org

We put post-its on a wall and feel productive moving them around.

The rest of the week we stick to good old micromanagement. Jira is great for that.

Trello as a kanban board. Simple but good enough.

Jira with a kanban board for individual to-dos (we have a LOT of bugs and small change requests to track). Trello to track the big picture project pipeline.

Nothing beats Jira as a bug database in my experience because it really is a database.

But you have to configure it for your own process (which for a healthy team mostly means lifting restrictions, IME), and there's a huge learning curve for initial configuration.

Plus it can be overwhelming for non-technical people to learn to use.

My experience is that engineers grumble for a week or two about the learning curve, but if you give them generous permissions plus a walk-through a couple days in, they quickly learn to appreciate its power.