#8241 closed enhancement (fixed)
Preferences enhancement proposal - option to disable rule as default pref
| Reported by: | Owned by: | Rob Guttman | |
|---|---|---|---|
| Priority: | normal | Component: | DynamicFieldsPlugin |
| Severity: | normal | Keywords: | |
| Cc: | Trac Release: | 0.11 |
Description
It would be nice if I as an admin could hide a field from users until they desire to explicitly see it, but only for the allowed types.
My problems:
- Using
(pref)adds the option to DISable a field/rule, not to ENable it, so with 150 already existing users it would break my neck to introduce a new "default hidden" field that single users can enable. - Removing the check at the preferences item "Show field when type = enhancement" will not hide the field always, but insteas show it always, even for types for which the field isn't appropriate.
Attachments (0)
Change History (10)
comment:1 Changed 14 years ago by
| Status: | new → assigned |
|---|
comment:2 Changed 14 years ago by
Yes, that really sounds good. And in the case of multiple types, there should be a dropdown box to choose the default one from in addition to the checkbox for "enable".
Respectively, you always could have a dropdown only which offers "disable" as the default and the other type(s) when opened.
The whole effect of this option would be a simple, tidy interface for new users with the possibility to add advanced fields for advanced users.
comment:3 Changed 14 years ago by
comment:4 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Ralf, please give this enhancement a whirl when you get a chance and let me know how it works for you and if it addresses all of your needs. Thanks.
comment:5 Changed 14 years ago by
| Summary: | Preferences enhancement proposal → Preferences enhancement proposal - ion to disable pref by defaultopt |
|---|
comment:6 Changed 14 years ago by
| Summary: | Preferences enhancement proposal - ion to disable pref by defaultopt → Preferences enhancement proposal - option to disable pref by default |
|---|
comment:7 Changed 14 years ago by
| Summary: | Preferences enhancement proposal - option to disable pref by default → Preferences enhancement proposal - option to disable reul as default pref |
|---|
comment:8 Changed 14 years ago by
(In [9689]) DynamicFieldsPlugin: Merge changeset [9665] to 0.12 branch, refs #8241.
This adds "(pref:disable)" syntax here. Code has been modified a bit in order to stricter follow PEP8, especially line-length < 80 chars.
comment:9 Changed 14 years ago by
Sorry, been on holyday :-) I will test the new version within the next few days. Thank you a lot for the fast response and solution.
comment:10 Changed 14 years ago by
| Summary: | Preferences enhancement proposal - option to disable reul as default pref → Preferences enhancement proposal - option to disable rule as default pref |
|---|
Great, let me know how it works for you, Ralf.
Thanks for the enhancement suggestion, Ralf. If I understand you correctly, another way of saying what you want is an option to have the preference for a given rule be disabled by default? So the Trac config could look something like this:
.. the idea being that you can set a default preference to
enable(the default so not required) ordisable. Would that work for you?I'm not saying that this will definitely be my solution, but it's one possible approach - more importantly is knowing whether it would address your problem or not.