due_date_update_threshold not working as expected
Posted: 17 Apr 2013, 04:16
I am using Mantis 1.2.11 but will soon update to 1.2.15.
I have checked the changelogs since then but there is no mention of due date that apears relevant to my problem.
Question 1: There is talk in the Forums about Due Date plugins, but I have been using the one provided in the basic installation and it is working well. Is the talk about plugins from the old days before the Due Date field was available and people wrote plugins, or is there something I have missed?
Question 2:
$g_update_bug_threshold is currently set to MANAGER
We want DEVELOPERs to be able to adjust their due dates, but not reword the original issue.
I have set $g_due_date_update_threshold = DEVELOPER; in config.local.php and also (in desperation) due_date_update_threshold to 25 in the config pages
In spite of this there is no control for a DEVELOPER to adjust their due date. Is $g_update_bug_threshold overriding $g_due_date_update_threshold? If not, how can I get this to work?
I have checked the changelogs since then but there is no mention of due date that apears relevant to my problem.
Question 1: There is talk in the Forums about Due Date plugins, but I have been using the one provided in the basic installation and it is working well. Is the talk about plugins from the old days before the Due Date field was available and people wrote plugins, or is there something I have missed?
Question 2:
$g_update_bug_threshold is currently set to MANAGER
We want DEVELOPERs to be able to adjust their due dates, but not reword the original issue.
I have set $g_due_date_update_threshold = DEVELOPER; in config.local.php and also (in desperation) due_date_update_threshold to 25 in the config pages
In spite of this there is no control for a DEVELOPER to adjust their due date. Is $g_update_bug_threshold overriding $g_due_date_update_threshold? If not, how can I get this to work?