Mantis Bug Tracker - Forums

Never mind. I found the issues Time tracking (HH:MM) start, stop, reset button.

I expected time elapsed was triggered on state transitions. That probably does not make sense considering the interruptions in work that occur daily. Anyway, this feature looks promising for the manager types that want ...

I did a rsync clone of my LAMP stack folder running Mantis to a second virtual machine ( VM ). I made sure the clone worked in the VM, then I repeated upgrading Mantis on the VM until I got it right. Make sure you do a mysqldump before starting. I did both a normal and an XML version just in case ...

1 - After upgrading from 1.2.4 to 1.2.10 I created a new project named "Test Time Tracking"
2 - Create issue named "Get coffee" and assign to myself
3 - Resolve issue in 10 minutes
4 - Created issue "Go to Lunch" and assign to myself
5 - Resolve issue in one hour
6 - With project selected, I select ...

On a possibly related problem...

After upgrading from 1.2.4 to 1.2.10, I no longer receive copies of newly created issues that I create. Email reminders to myself work fine.

I am seeking an overview of how "Time Tracking" works.

1 - When does the issue time tracking begin and end? From issue creation or from the transition to assigned state to issue closed state?

2 - Are there reports for project time totals for all project issues? Or project category totals ...

The problem appears to be that 1.2.10 does not like my 1.2.4 config_inc.php file.

Work around is to copy included 1.2.10 config_inc.php.sample to config_inc.php and manually merge in my 1.2.4 config_inc.php settings.

I am trying to update Mantis 1.2.4 installed from a Bitnami LAMP stack "module" installer. Bitnami puts each app in an apps folder using a generic folder hierarchy, each with their own conf which is in turn included by Apache's httpd.conf.

All php code for the app, Mantis, MediaWiki, etc, is ...

Thanks! My supervisor say that is close enough and he likes the summary page that has some other good stats as well.

Thank you very much for your reply!

-Ed

My boss wants to see which issues have required the most effort based on the time elapsed from the date an issue was submitted to the time the issue was closed (or current date if still open). Is there a way to sort by (lastUpdate - dateSubmitted) or something with similar effect?

Thanks in advance ...

That could be it. The difference between the combined Bitnami Wamp+Mantis install and what I did which was Bitnami Wamp install, followed by Bitnami Mantis module install.

I think LAMP is the way to go. We already have a Jenkins build server running on it and Jenkins has a Mantis plugin which is ...

Never mind.

I imported the Mantis DB from Windows WAMP stack into a LAMP Mantis 1.2.4 and the application error #11 now works as expected (see screenshot ) and informs users of the error. Thanks you for your assistance, but I think I will just move it all to the Linux install and forget about ...

The error originates here. The application error dump confounds users. The actual error message telling the user a necessary field was empty is not visible unless the user scrolls the browser to the far right.

APPLICATION ERROR #11
Full path: C:\Program Files\BitNami-WAMPStack\apps\mantis\htdocs ...

Thank you for your reply.

Do you think it could be the result of recently upgrading from 1.1.8 to 1.2.4 ? I did a mysqldump, installed a new Bitnami updated LAMP 1.2-4 stack, then a new Mantis 1.2.4 Bitnami Module, then did a mysql restore with the dump.

I tried temporarily turning off the ...

Is there a work around for this?

I just upgraded to 1.2.4 and users are complaining about the bug tracking system I selected being broken when they forget to enter required fields. Any tips are appreciated.

Sorry, I do not see the "Fixed in Version Field" in 1.1.6.


1.1.6 was released December 2008, is this a couple of years?


Ahh, I see my problem. It has actually been 1.8 years and not 2.0 years since 1.1.6. I feel very inferior now which must be the point of that comment. Thank you very much for ...