Here you go....http://agilescout.com/best-agile-scrum-tools/

reviews of tons of tools...some free, some not (I didn't read them, could be a fake site, but they at least listed a LOT of the tools out there)

We used to use xPlanner at my last startup (one of the free ones on the list)....worked fine when we were small, but outgrew it when the team hit around 50..probably outgrew it before then, but thats when it got painful and we switched. Based on the screen shot on the review site though looks like its had some major changes...

The dev team (which I'm no longer part of) now uses Version1. Its most certainly not free, but well we got acquired 6 years ago and now the company has 55,000 employees so that wasn't as much a concern anymore They seem to really like it and it integrates with lots of our other systems.

Bear in mind this is for Enterprise software, not games...but wouldn't think that would matter for a tool like this

The company I work for recently made the switch from Trac (free) to Jira (Paid; hosted or downloadable) which both can do what you describe in the OP. Trac needs a bit of customizing and some plugins and macros which can be a bit time-consuming until you get it right while Jira has it all inbuilt.

Trac was good for us for quite some time and it did the job until the dev-team got bigger, more projects came aboard and we generally needed to work and rely more on the issue-tracking and planning.

Jira is generally easier to use (especially for non-techies) as well as i has a already integrated "agile" mode which makes working with it easier and more fun. The close integration with the documentation-system "confluence" is also a pro. Said that Jira has its drawbacks most of all being slow and some quirks in the UI.

Considering the monthly fee one has to pay versus free software that is hosted inhouse a rough estimate of the ToC might be worth it. A free software package might be even more expensive in the end if you need to buy extra hardware to run it on and if you do the server maintenance yourself (getting less time on your projects) or hire somebody to do it for you.

I used Redmine, which is great, apart from the whole Ruby/Ruby on Rails thing which means terrible security implications as of late. I used to really like JIRA but can't afford to pay for a plan.

I never liked Trac - too clunky, only really usable by programmers unless you put a lot of effort into it.

I use Jira in the "corporate world", but for other projects, I use a physical wall plain and simply. It remains the most agile tool to date and it can be adjusted realtime (works wonderfully unless some team members are away).

Trello works too, but its not perfect.

In regards to Trello time estimating...

If you use google docs with Trello, you might be able to mine the cards/lists for info related to the checklists. Basically using a checklist to form an estimate of time (define each checklist entry as a day, half day, or hour). Then mine the card for the number of checks remaining (versus initial count) as the project progresses. This will give you initial estimate, and velocity if mapped against days.

http://kevinpelgrims.com/blog/2012/03/06/project-progress-tracking-with-google-docs-and-trello

Ex:

- We have a IPAD GAME board.

- On that board we have a GAME PROTOTYPE list (among other lists related to concepting and full development)

- On that GAME PROTOTYPE list, we have a GRAPHICS ENGINE card.

- On that GRAPHICS ENGINE card I estimate 10 days to complete the engine. I create a detailed description of what I intend to do, and place a checklist with 10 items, each called "1 day of work complete."

- As the prototype progresses I check off each day of work.

- Other team members check off their progress as well for ARTWORK and GAMEPLAY on the same prototype card.

- If I need more days I add another day to the checklist.

- My manager is subscribed to the card so he is notified of any changes I make.

I haven't needed to do this yet, but I imagine implementing this in the next few months. Or looking for a paid solution.

My team is always in google docs and google drive/chat, so using Trello in this manner makes sense. But we're very small. Have no experience with Trello's signal/noise ratio with large teams.