Several customizations

[Morpheus87]

I tried just changing config_inc.php and just custom_strings_inc.php and unfortunately neither worked.
Are there any other ideas?

[Morpheus87]

I’d like to edit the severity list. This is how it used to be:
10:feature,
20:trivial,
21:Feature-Wunsch,
30:text,
40:tweak,
41:error,
50:minor,
60:major,
70:crash,
80:block,
90:unknown

And this is how I want it to look like.
01:NA,
50:minor,
60:major,
80:block,
90:unknown

Now my problem is, if I change it in config_inc.php and custom_strings_inc.php old entries show up just as numbers (like @40@).
My question is, is it possible to keep the old values only for ‘old’ issues?

I still have this problem. Is there no solution for this?

[atrol]

It's quite confusing to have different severity lists in same project.
IMO the best solution is to migrate the old issue data in database.

[Morpheus87]

My question might be a little bit confusing.
What I am trying to do is, to remove some severities (for example ’20:trivial’) without having the number (@20@) shown in issues with the removed severity (‘trivial’).
I followed the guide and it still does not work.
http://www.mantisbt.org/manual/admin.cu ... enums.html
I also tried it with changing config_inc.php, custom_constants_inc.php, custom_strings_inc.php, strings_english.txt and strings_german.txt but nothing worked.
Does anybody have the same problem?

[atrol]

My question might be a little bit confusing.

It's not confusing, but it makes not that much sense in my opinion.

You want two different lists of severity values in one project: SL1 (the one with 11 values) and SL2 (the one with 5 values, one value not existant in SL1)
MantisBT is not able to deal with more than one list in one project at the same time.
Thus, you would have to change the source code of MantisBT to get it.

Clean solution (sorry, no time for it)

Quick and dirty solution (not recommended)

Step 1, define rules where you want to use SL1 and where you want to use SL2 in MantisBT.
e.g. use SL1 when viewing old issues, when filtering issues, on summary page, ...
use SL2 when entering new issues, updating issues that are entered after SL2 has been activated, ...

Step 2, implement a function F1 that delivers SL1 or SL2 depending on a function parameter

Step 3, implement a function F2 that delivers SL1 or SL2 depending on issue creation date (the day when you introduce SL2).

Step 4, Use F1 and F2 according your defined rules by replacing existing calls at various places in MantisBT code
...

But the solution will be quite confusing for a user, e.g. he will see different severity lists in same project when editing an issue.
That's why I recommend to migrate old severity values and use just the new list.