This issue will not be solved if we continue to support the old options

• If more native fields added in the future, they will be hidden by default.

Consider that there are also options like enable_product_build, enable_profiles, enable_eta, enable_projection, enable_sponsorship that influence the visibility.

I am not sure if introducing new options without desupporting old options will introduce some confusion.

Looks like we need to rationalize the configuration associated with the following requirements:

1. Disabling a field across all of MantisBT (enable_xxx style).
2. Re-ordering fields on pages like report, update, view, etc.
3. Hiding fields on specific pages like hide severity on report, but have it available on update.
4. Hiding fields based on access level.

We should brainstorm options. We may decide to deprecate options. We may also decide to leave everything as is :) -- will add more as I think about this more.

There are even more feature requests, e.g. users want the visibility on certain pages based on status
https://github.com/mantisbt/mantisbt/pull/612

Next will be to have the visibility based on priority, access level, ....

Maybe offering an event for plugins to hide fields is an option.
Thus, you could write a plugin that's implements just your original feature request, you don't have to deprecate any existing option, you can write other plugins that hide fields based on whatever the author wants, ...

Of course, I would prefer to have some more base functionality in core, have a nice UI for it, ...
But this is a major redesign, maybe in version 3.0 ;-)

Just linking a couple forum posts for this often-requested feature.
Removing default fields
Removing profile fields
User here wants to hide profile fields because they're not required, and then add custom fields for same data because those can easily be set to be required. (Note this expands this ticket to include concept of a field not just being visible or not but being required or not).