Mantis Bug Tracker - Forums

By default, messages are only sent to the originator, or handler of the issue. If you look at the Manage -> Manage Configuration -> Email Notifications page, you can add additional access levels for each type of message.

With respect to authentication, the plan was to make it modular to allow one to pick from several supplied methods, or plug in your own. It's still in the concept stage. As for the manual, I'd suggest that you join the developer's list. We're looking to port the manual into a text file form. possibl...

The "Assign to:" button should show up is the user meets the threshold requirement of 'update_bug_assign_threshold', or if not found, 'update_bug_threshold'. These default to developer.

Once you enter the database information, it should validate the information (printing about 10 lines) and then try to access the database. The button you checked should print the required SQL queries, rather than applying them to the database.

Are there any errors in your apache log?

A quick google on this error message seems to indicate that php and/or apache were not compiled correctly (the pcre errors). With this failing, I would expect that many things won't work properly. (Ref. http://lists.debian.org/debian-apache/2 ... 00109.html ).

I added this code under #6093.

I'll look into that, but you could try to approach it from the Manage Project angle. At the bottom of the page, there is a user list, and you can re-assign access levels there.

The email is formatted in core/email_api.php, function email_format_bug_message(). I think that there is a thread in this forum somewhere about adding this kind of information.

email_bugnote_limit is broken in the current release. I think that it has been bugged as well.

I mis-understood.

You could set the anonymous user to "viewer" for the project in question. They would only be able to see things and not report issues.

Mantis currently doesn't do this. If you re-assign the issue back to the submitter, how does it get re-routed to the designer if the issue is re-opened? Re-assigning it also severly complicates the process of figuring out who resolved the issues. An alternative is for reporters to look for issues th...

Yes. You can make the project private and add all users but the anonymous one to the project.

Under newer versions of IIS, you also need to give READ access to everybody for it to work.

The ftp method is not well tested in recent releases.

There is an email check in admin/check.php (near the botton of the screen).

The notifications need to be enabled by user access level before the messages will be sent. The user preferences only serve to turn off messaging.

"Report Issue" in the top menu. You need to create projects and categories first.