Karl, Nope. It's not a bug. Having the ability to "MosifyCustomField" merely means that users "in a group" can select or enter a value for that CF *in a ticket *. In order to change what values can be selected, etc. the privilege "AdminCustomField" needs to be applied to a group you want to have this privilege. At our installation, we don't want every "Tom, Dick and Harry" changing values for CF's that others are using, so we create Admin groups for this ability. It keeps the "Chaos factor" down. Hope this helps.
Kenn LBNL On Thu, May 27, 2010 at 4:53 AM, Karl Ove Hufthammer <k...@huftis.org>wrote: > I have a combobox custom field with a number of possible values, e.g., > ‘foo’ and ‘bar’. However, when a user adds a new value, ’baz’, that value is > *not* added to the list of possible values (shown the next time a user > creates a new ticket). > > Is this a bug? And if it’s not considered a bug, is it possible to add this > functionality, so that the list of combobox values is automatically updated > whenever a user adds a new value? It would also be nice if old values were > automatically removed when no tickets have the values anymore (usually when > someone enters and misspells one of the ‘legal’ values, and later fixes it). > > -- > Karl Ove Hufthammer > > Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > Buy a copy at http://rtbook.bestpractical.com
Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
