I wrestle with this every few weeks. The goal of Mantis is really to be a bugtracker and not a project/task management system. Unfortunately, it appears that the coupling achieved from using two separate tols isn't good enough for most users. That basically means that things like this will slowly creep into Mantis. However, Mantis will likely never be a good project management tool: just a bug tracker that can do some project management.

i think a combination of both would make it really stand out. I'm using it for just about everything here .. bug reports / help requests ... haven't tried project management yet.

I really agree that the two tools should be separate: specialise your tools, and use the appropriate APIs if you wish to integrate them. By adding extra 'addons', you lose focus of what the application is really about. Maybe what we should be doing is looking at enhancing (and encouraging the use of!) the API.

have it be a toggle in the config_inc1.php under defaults if someone doesnt want to see it they can toggle it off through there. I personally think it would be very useful. You can see the top5 bugs assigned to you by priority or something.

Ramon

I think that mantis has a lot of potential as a task tracking tool actually. The new version of mantis is basically making the tool in a versatile tracking tool of just about anything. I work for a company that is using mantis for bug tracking requirements tracking, etc and I am looking into the possability of task tracking. I have created a couple of categories for: tasks and milestones. Then using the custom fields I have a start date, end date and percentage complete. I then created a custom php page that will query the mantis database and using the jpgraph tool I can create dynamic gantt charts for all the tasks and milestones for my projects. I agree that its not a 100% fit. ----- buts its pretty damn close

edited on: 03-26-03 12:54

I really think we should keep our focus on bug tracking, adding such features will distract the development team and will make Mantis more complicated to use. I agree with "updater"'s opinion that we can probably provide the user with easier means to integrate with other tools or with tools developed in-house.

I would propose that Mantis remain a bug/feature tracker. However, since the backend is a database, it can dovetail with a parallel, open-software effort for project management. This way, there will be separate interfaces with different functionality, but they will rely on the same consistent project data. Just a thought.

I have been tweaking mantis to do both for us. two thumbs up to the development team they did a fine job coding (IMO) and in a matter of weeks (with little or no experience with PHP on my part) I've been able to transform Mantis into both a helpdesk/bugtracking solution and a Project Management system. for me these two go hand in hand as most of our projects stem from bugs/helpdesk requests. so I added a isaproject field to the mantis_bug_table if this is 1 you get to see a bunch of additional information if this is 0 you see basically an unmodified mantis. once something is deemed a project it gets moved into a different mantis "project" and my manager can track its progress. I added things like percent complete. due date. requestor(aka reporter) priority. customer. billing hours. I added a bunch of information for users to fill out when the sign up. phone number, facility, contact name.

I say keep up the good work. I dread your next realease because I know your going to add a bunch of stuff that I'm going to really want and for me it is going to be a complete rewrite to re-add all my changes.

what am I saying.... I'm not sure .... I think keeping them seperate from your poing of view would be the best Idea. you get into a lot of personal opinions when you start digging to deep and you'd just end up doing work that people would want to change anyway. If I can make the changes I wanted to the system then anyone can.

Thank you for taking the time to report a problem with mantis.

Since this problem report was originally made, a number of releases have occured.
It appears that this issue has either been fixed, or may not be a relevant report for the current release.

Unfortunately you are not using the latest version and the problem might already be fixed. Please download the latest release from http://www.mantisbt.org/download.php [^]

If you are able to reproduce this bug in the current release, or have some more information on how this feature could be improved in the current release. Please either change the mantis version on this bug report
to the version you tested and change the status back to "Open", or open a new issue report with more information.

Again, thank you for your continued support and report.