All good ideas, but please remember Mantis is a defect tracker. You could opt to couple it to Dotproject ( www.dotproject.net ) see http://www.dotproject.net/vbulletin/showthread.php?t=4614 [^] ) from of experience I know one wants more and more project planning in a defect tracker, up to the level the defectracker does not satisfy anymore. IMHO We better impove dotproject mantis integration.

It's properly right that many people would want more and more project features in Mantis, but why is this a bad thing ?

We are using Mantis with Subversion integration and just needs a little more, but if that means Mantis integration into a project tool like dotProject why even use Mantis. You could make a dotProject/Subversion integration instead.

I am always here... My PC crashed a few days ago, so I am only from work, and dont have here time to some work about it...

I have started creating it allmost exactly as you have wrote it jci000, thought I am more thinking about using a more generale approach:
Initial (who, when, how much).
Added (who, when, how much)
Used (Taken from the current interface???, who?)
As a report on the page will be: Remaining

If you use 'added' instead of 'remaining' you must allow 'added' to be negative in the case that the initial estimate was to high.

You can use the issue with the 'last in time' ETA as target release date.

Jotango

I now about Scrum as well and we have started to us it. I think that what Sirshurf is making is enough to use Mantis as a Scrum tool for starters. If we don't keep this simple we'll newer get finished.

At times it is very difficult to find out where Mantis is going. This is a feature that has been discussed a great deal in the forum over the years, but has never made it to Mantis core. I've been unable to get any developer interested and can't get hold of sirshurf, so yes it must have died :-(

I could still use the functionality, but have solved my immediate problem with a few custom fields and some Excel macros. This means that my demands for this functionality has increased for my full sponsorship, or I might lower the amount.

timecard has created a new field time spent, while the initial field becomes total time. since the initial field was time spent earlier, the billing page will show estimated billing instead of spent billing like before.

For now it contains advanced time registring functionalities and some reports. Can be configured to use customizable 'types' of work (like business and functional analysis, development, testing, deployment,...).

I'm planning on adding more 'project management' functionalities:
- add notion of 'hourly rate' and 'hours per week' for users
- display timelines of projects with versions, tickets planned for that version with their estimates, done and todo,...
- add reports that display the tickets which are most overdue, interesting numbers per user,...

BTW: We have made an compact, aggregated view of the roadmap, so you can see all scheduled versions and the number of issues open / resolved / closed. It has some very simple way of guessing the completion date, by just adding all estimated durations (custom field of each issue), which is nevertheless somehow useful to get an idea of how well we are in time. I'll upload a screenshot in a second. We just had no time up to now to make this available.

Hi, We have been playing around with burndown etc and are using the attached spreadsheet. The Focus is on Project and then a version of the Project. Essentially we agree a block of items for a given version release, assign who is doing which ones, and export the data and then run it through this spreadsheet to determine completion dates of each task based on Prority, Assigned to, working time, and hours estimate. It's a bit crude, and we'd prefer it if it was al "in" Mantis, but hopefully someone else will find it helpful.