Mantis Bug Tracker - Forums

Hi!

I have to use 2 timetracking in every bug note. One for billing (external) and one for internal accounting. Of course our customer can only see the external hours.

I tried the internal solution first. I used the bug note private/public status to separate the internal/external hours. It looks great on the customer side, but on our side every hour is summarized not just the private ones.

I tried the TimeCard plugin, but it just didn't work at the bug updates (we use PostgreSQL if it matters).

I think if I can attach 2 custom fields to every bug note and write a custom function which summarizes the hours it will be okay and it isn't a big work.

So, is there any timetracking plugin which can do it, or is there any solution for using custom fields at the bug notes?

We try to change our current ticketing system to Mantis and this is the first milestone.

I'm using Mantis 1.2.9.

Thanks,

Arpad

PS: Sorry for my bad English.

There is also the timetracking plugin.
Perhaps you can use that one for external and use the standard mantis way for internal (or the other way around)

Yes it could work, I'll check the timetracking plugin. You mean this https://github.com/mantisbt-plugins/timetracking ?

There isn't really a plugin which allows configurable custom fields for a bug note? If the time tracking will work this way, I'll probably have to use other custom fields (example: billing status, on/off duty flag).

I can't install the TimeTracking plugin. It failed at the schema creation.

I think I have to write this myself...

how does it fail ? it's very simple install, the only thing it does is adding a table.
However the uninstall doesn't remove the data,
if you have uninstalled it, and want to re-install, it usually understands it's a re-install and doesnt do anything.
but if it doesnt understand, then you might need to delete that table manually

Hi!

I already forget the error message, but that time I debuggeed it deeply and it seemed to be not to easy to solve (maybe related to that we using PostgreSQL, not MySQL). After that I wrote a new, company specific plugin. It worked well, but the management choosed another solution (and later they dropped that too).

Arpad

I added this to the bugtracker
http://www.mantisbt.org/bugs/view.php?id=16497

it would be interesting to know what they replaced mantis with, and then what they replaced that with. seems like they change their minds a lot

maybe better pm that info