Mantis Bug Tracker - Forums

check this out if it helps: http://mantisbt.org/forums/viewtopic.php?f=3&t=15398

Mysterious... One thing you can try: can you create a new user as a reporter or so, add this user to the project as developer and assign the issue to him. (anyways this is the preferred way to handle users). It suppose to make no difference but who knows. Again, your problem can not be reproduced on...

I was not able to reproduce this issue with a fresh installation of mantis. You can go to "manage/manage configuration/workflow threshold" and check the status in the "Status to set auto-assigned issues to" field. I think this field may have "new" in it instead of "...

Actually I made a mod which does the job for you: open your bug_change_status_page.php and make a search for the following string: "<!-- Fixed in Version -->" couple lines below the string you will find something like this: <?php } } ?> Now hit couple enters below this and copy the followi...

I understand your question, and I believe you made a legit point here. In the other hand I dont believe it is possible with the current release of mantis. You need to modify probably one or two php files. Its not a very big deal though. Just to make one point: when you move the issue to "resolv...

Something is wrong in your system and since mantis 1.1.8 is not supported you need to update to the latest version to get relevant answers to your questions. You can go to manage/manage configuration/email notification (if it exists under 1.1.8 ) and check the checkboxes. Modify them if suitable. Th...

I guess setting your main project to private will resolve your problem.

I am not sure if I understand what you would like to achieve. The history tracks all the changes ever made on the issue, so you can easily determine which change occures at which status. If it only the notes then you can modify the php scripts to lets say add the status at the beginnig of all notes ...

I am not sure if I understand the question. You can enable your custom fields on a project basis, but that means all the issues in that project will have that/those fields. You can specify which fields appear when the issues is reported/resolved etc If the question is if you can enable certain custo...

I am afraid that a issue can not be resolved. As far as I know the current mantis version does not support this type of exceptions, so either you allow the reporters to see private issues, or you can not assign issues to them.

You can enable the anonymous account though and achieve anonymous reporting:
http://www.mantisbt.org/wiki/doku.php/m ... ous_access

I dont think anonymantis is supported on this forum. I have never heard about it.

Do you use private issues? If so then check your $g_private_bug_threshold variable, it must be

$g_private_bug_threshold = REPORTER;

Maybe misunderstood your question a bit. Sorry about that. I had used mantis without a cronjob and have found no issues with duplicated messages or so.

I assume all emails are stored separately. That makes sense since if you wouldnt use the cronjob then all emails would be sent immediately. Cronjob does nothing else from the user perspective than delaying the messages for a while and then email all of them at once later. (but feel free to correct me)