need of setting default values for some hidden fields

This plugin filters out fields that you don't want to display from the ticket. Those fields still exist in the database, along with whatever default value has been set for them. You could, for example, have a field be displayed, modify it, then hide it, and have it's value be preserved. Creating the field and setting it's default value would still be handled by standard means (CustomFieldAdmin plugin, etc.).

I want to explain it more precise: Using MenusPlugin and ticket templates, I click on a menu entry that calls http://mytracproject/newticket?type=foo&description=[[Include(PageTemplates/XYZ)]] and I wish this showed a ticket form where description is hidden but still internally active, which means the user cannot see the description field but its value must be set to [[Include(PageTemplates/XYZ)]] with creating such a ticket. This behaviour should be dependent on a certain ticket type.

Ah. Then no for a couple of reasons...

(1) This plugin doesn't filter standard fields like description, and (2) The fields are filtered from the data dictionary completely. This was done because one of the issues with simply not displaying the fields is that they are still processed by other templates and/or plugins. When the number of custom fields is very large, this can cause page processing time to become unacceptable.

If you haven't already done so, take a look at the CondFieldsGenshiPlugin, I think it does just what you're looking for.

Replying to bphinz:

Ah. Then no for a couple of reasons... (1) This plugin doesn't filter standard fields like description, and (2) The fields are filtered from the data dictionary completely.

I see. The you probably close this with 'wontfix'.

If you haven't already done so, take a look at the CondFieldsGenshiPlugin, I think it does just what you're looking for.

It doesn't work there either, that's why I was hoping for this plugin.