Hi,
We're using v 1.2 of mantis and I've had good success with customizing the majority of options for our use. I really like the program and am anxious to deploy it to our dev staff. One of the things I'm trying to do is remove the FEEDBACK and RESOLVED states as those don't apply to our workflow. I was successful in removing all the other states but these two keep displaying @20@ and @80@ in the drop downs (using English as the lang).
I've created all the required files and used the same approach for the successful removals so I'm stumped on this. I've also searched the docs, forum and bug db for this but didn't find anything.
Flies created:
config_inc
custom_constants
custom_strings
Are these tied to other values someplace that I'm not looking at? Can anyone shed light on how to remove these or where to look?
Thank you in advance for any guidance you can provide!
Problem removing Feedback and Resolved states
Moderators: Developer, Contributor
Re: Problem removing Feedback and Resolved states
I had a short look at the sourcecode to find hardcoded status related things.
At first sight I just found the following default settings.
Change them in your config_inc.php to be sure that these status values can not be accessed.
(But not really knowing whether this is your problem)
At first sight I just found the following default settings.
Code: Select all
$g_bug_reopen_status = FEEDBACK;
$g_bug_feedback_status = FEEDBACK;
$g_bug_readonly_status_threshold = RESOLVED;
$g_bug_resolved_status_threshold = RESOLVED;(But not really knowing whether this is your problem)
Re: Problem removing Feedback and Resolved states
Thank you for the reply! I had found and changed those instances already but it didn't fix the issue.
What did end up fixing the issue was going into the Mange --> Manage Configuration --> Configuration Report and deleting the value for the workflow that was stored there. Once I deleted this value, the states went away without changing anything else. The value that was stored there was a "work in progress" workflow path that I had customized but was not the final one.
I'm not sure what action causes those values to get stored and why they seem to override the config file. Even though everything appears to be working, a new value has not shown up on that page since I deleted the previous one.
What did end up fixing the issue was going into the Mange --> Manage Configuration --> Configuration Report and deleting the value for the workflow that was stored there. Once I deleted this value, the states went away without changing anything else. The value that was stored there was a "work in progress" workflow path that I had customized but was not the final one.
I'm not sure what action causes those values to get stored and why they seem to override the config file. Even though everything appears to be working, a new value has not shown up on that page since I deleted the previous one.