View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0020051||mantisbt||customization||public||2015-08-23 22:54||2018-04-23 15:48|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Summary||0020051: Config fields to hide rather than fields to show|
Often users want to hide a field or two. To do that they typically would hard code the rest of the list as the value for the config values below.
That has two issues:
I wonder if we should add similar configs that would have in the array the fields to hide. We could even continue to support the above fields, but recommend using the others to hide fields.
If a field is in the include and hide list, then hide wins.
|Tags||No tags attached.|
This issue will not be solved if we continue to support the old options
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:
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
Next will be to have the visibility based on priority, access level, ....
Maybe offering an event for plugins to hide fields is an option.
Of course, I would prefer to have some more base functionality in core, have a nice UI for it, ...
Just linking a couple forum posts for this often-requested feature.