Modify

#10854 closed enhancement (wontfix)

need of setting default values for some hidden fields

Reported by: falkb Owned by: bphinz
Priority: normal Component: TicketFieldsPlugin
Severity: normal Keywords:
Cc: Trac Release:

Description

I want to hide some fields because the user should not recognize it. Nevertheless, I want to set a default value for certain hidden fields. I only want to hide the field from the user but it should exist and be active, internally. Is this possible with your plugin?

Attachments (0)

Change History (5)

comment:1 Changed 22 months ago by bphinz

  • Status changed from new to assigned

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.).

comment:2 Changed 22 months ago by falkb

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.

comment:3 follow-up: Changed 22 months ago by 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. 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.

comment:4 in reply to: ↑ 3 Changed 22 months ago by falkb

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.

comment:5 Changed 22 months ago by bphinz

  • Resolution set to wontfix
  • Status changed from assigned to closed

Add Comment

Modify Ticket

Action
as closed The owner will remain bphinz.
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.