Mantis Bug Tracker - Forums

This feature has been submitted to CVS. There is also a new UI to change most of the workflow related parameters.

Comments are welcome...

Could you file an issue to this effect at http://bugs.mantisbt.org/ ?

The email system has two parts (actions and recipients). The actions are what you have listed (change in owner, bugnote, sponsor, relationship, or change in status to any defined status or reopened, or deleted). Anytime one of these actions takes place, the email generator is kicked in. The recipien...

2) 'define(XXX, 52)'d a new value in mantis/core/custom_constant_inc.php

The custom constant file is "mantis/custom_constant_inc.php".

We are looking into a bettwe way to capture the manual, and could always use some help in this area.

The current mailing works based on bug status, rather than who submitted the issue. You can set it up so that all reporters are informed of new bugs. There is a detailed description in the manual about half way down the page on http://manual.mantisbt.org/manual.confi ... .email.php.

I believe that there is a bug in 0.19.2 that may cause this behaviour (#4995).

There are still some issues using PHP 5 with Mantis. These have been worked out in the next release. You may want to look at #4995 for one patch.

It sounds like the mail interface is not working at all. Have you tried the mailer test in admin/check.php?

Do you still have '$g_allow_signup' set? $g_allow_signup = ON requires $g_send_reset_password = ON. You need to either create users manually via the Manage -> Manage Users -> Create User route (setting the password manually), or allow signup (and reset_password).

Local changes are made in the config_inc.php file in the main directory. There is a sample file there in the normal distribution (config_inc.php.sample). This allows you to change settings and not have them overridden by the next release. Personally, I don't delete the admin directory. I just make i...

This situation is covered in the manual at http://manual.mantisbt.org/manual.custo ... values.php

You can set "$g_set_view_status_threshold = NOBODY;" and "$g_change_view_status_threshold = NOBODY;". This will not allow anyone to change the view state from the default.

My suggestion would be to set up a project per product. You can then set up releases for 1.0, 1.5, and 2.0. The issues can be assigned to releases using the fixed in version field. (This also allows the Changelog to work properly). I would set up the categories to cover major pieces of the functiona...

You can turn off the email for password change by setting "$g_send_reset_password = OFF;". This will leave the initial password blank. As for the mail problem, I would check which phpMailer mode you are using. The smtp_* parameters are only used when "$g_phpMailer_method = 2;". B...

Adding a relationship is controlled by the $g_update_bug_threshold parameter.

Try in your config_inc.php file. Note that this will allow developers to update the information on an issue as well.