Modify

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#8241 closed enhancement (fixed)

Preferences enhancement proposal - option to disable rule as default pref

Reported by: ralf.wohner@… Owned by: robguttman
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:

  1. 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.
  2. 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 4 years ago by robguttman

  • Status changed from new to assigned

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:

field.show_when_type = enhancement (pref:disable)

.. the idea being that you can set a default preference to enable (the default so not required) or disable. 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.

comment:2 Changed 4 years ago by ralf.wohner@…

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 4 years ago by robguttman

(In [9665]) refs #8241: can now disable a preference by default via "(pref:disable)"

comment:4 Changed 4 years ago by robguttman

  • Resolution set to fixed
  • Status changed from assigned to 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 4 years ago by robguttman

  • Summary changed from Preferences enhancement proposal to Preferences enhancement proposal - ion to disable pref by defaultopt

comment:6 Changed 4 years ago by robguttman

  • Summary changed from Preferences enhancement proposal - ion to disable pref by defaultopt to Preferences enhancement proposal - option to disable pref by default

comment:7 Changed 4 years ago by robguttman

  • Summary changed from Preferences enhancement proposal - option to disable pref by default to Preferences enhancement proposal - option to disable reul as default pref

comment:8 Changed 4 years ago by hasienda

(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 4 years ago by ralf.wohner@…

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 4 years ago by robguttman

  • Summary changed from Preferences enhancement proposal - option to disable reul as default pref to Preferences enhancement proposal - option to disable rule as default pref

Great, let me know how it works for you, Ralf.

Add Comment

Modify Ticket

Action
as closed The owner will remain robguttman.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.