Opened 13 years ago
Last modified 4 years ago
#9274 new enhancement
rename fields based on ticket type
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | DynamicFieldsPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.11 |
Description
I'd like to have different label for the "Summary" field based on different ticket types. Would love to have a way to configure this.
Attachments (0)
Change History (5)
comment:1 Changed 13 years ago by
Status: | new → assigned |
---|
comment:2 Changed 13 years ago by
yes I am using dynfields plugin now and I have found it immensely useful!
I need this feature for /newticket and /ticket at least. To have /report and /query would be even better if not too much work.
And I can live with internal field names remaining the way they were. Thanks.
comment:3 Changed 6 years ago by
Owner: | Rob Guttman deleted |
---|---|
Status: | assigned → new |
comment:4 follow-up: 5 Changed 4 years ago by
It seems like there might a few internal variables that could benefit from using a "label" (and/or be hidden). I'm going to try and follow up and find out who might know what to do... and how I might be able to lend a hand...
comment:5 Changed 4 years ago by
Replying to Aikido Guy <aikidoguy@…>:
It seems like there might a few internal variables that could benefit from using a "label" (and/or be hidden). I'm going to try and follow up and find out who might know what to do... and how I might be able to lend a hand...
I'd like to eventually incorporate all of the features of BlackMagicTicketTweaksPlugin. That plugin uses ITemplateStreamFilter
from Genshi, so it's deprecated with Trac 1.4.
Where are all of the locations you would want/need the field name to be changed? Examples include:
And to be clear, the change would only be "cosmetic" - i.e., the internal field name would remain "summary". Would this still be of value?
Question: are you using this dynfields plugin now?