[Patch] Custom fields with date=false still behave as if it were set to true
|Reported by:||C. G. Brown||Owned by:||Robert Corsaro|
Description (last modified by )
The following custom field entry will still display a date in Trac 0.11.7:
[ticket-custom] test1=text test1.date=false test1.date_empty=false test1.label=Testing test1.value=
The workaround is to remove the date entry altogether but if someone were just doing a quick change of a field this could become an issue. For us it's a an issue, albeit a minor one, because we have our own custom field manager and it's easier to pass false than to hide the value.
I'll see if I can produce a patch.
Change History (5)
comment:1 Changed 6 years ago by
|Summary:||Custom Field date=false still behaves as if it were set to true → [Patch] Custom fields with date=false still behave as if it were set to true|