Opened 15 years ago
Last modified 5 years ago
#6648 new enhancement (wontfix)
Hide fields instead of dropping them
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Component: | SimpleTicketPlugin |
Severity: | normal | Keywords: | |
Cc: | falkb | Trac Release: | 0.11 |
Description
We are using trac 0.11 as a feedback system for one of our websites, using links to the newticket URL with parameters to preset fields such as the component (along the lines of "http://my.trac/newticket?component=SomeComponent"). It would be nice if the form would include this preset value, but hide it from the user (i.e. use a hidden form field). This way we could people enter tickets attached to the right component without them being able to change it.
Attachments (0)
Change History (5)
comment:1 Changed 13 years ago by
Cc: | falkb added; anonymous removed |
---|---|
Summary: | Use hidden fields instead of dropping them → Hide fields instead of dropping them |
comment:2 Changed 13 years ago by
Owner: | changed from Noah Kantrowitz to Ryan J Ollos |
---|
comment:3 Changed 13 years ago by
After reading this I wonder if SimpleTicketPlugin actually "hides" or "drops" when doing data['fields'] = [f for f in data['fields'] if f['name'] not in self.fields]
(?). And if I'm right and it's "dropping", which other way would "hiding" go?
I'm quite interested in such stuff at least because of trac:#10320 but know nearly nothing about the internal architecture yet...
comment:4 Changed 5 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Please use DynamicFieldsPlugin.
comment:5 Changed 5 years ago by
Owner: | Ryan J Ollos deleted |
---|---|
Status: | closed → new |
The BlackMagicTicketTweaksPlugin hides ticket fields by modifying the Genshi template stream (
filter_stream
inITemplateStreamFilter
). We might be able to do something similar here. I'd consider a patch for inclusion.