add 'time' as another custom ticket field type

[hoff.st@…]

implementation of custom fields by configuration in [ticket-custom] of trac.ini is stable, quite flexible supporting a number of different types and well integrated into Trac Query, however there is no field type for times/dates,

I recommend a field type utilizing Unix time for this, so time is more appropriate than date (a more special term, that could be derived from time).

While this was requested implicitly years before (see #1962) and several Trac-Hacks to address this among other things (just to mention ​DateFieldPlugin) were showing the enduring demand, there is still no native, clean implementation.? All workarounds (commonly by adding more logic to text fields) suffer from different shortcomings like sub-optimal Query results, date format (inconvenient|incompatible with|not matching to) certain locales, difficulties with input value validation (see #3785), etc.

[hoff.st@…]

I'm not in the position to judge on any of priority, severity, milestone or who should actually do it, but I hope someone will step up to assign this really soon. His functionality seems pretty basic and users already waiting a long time. However it will have to be done carefully, since both native time fields, time (of ticket creation) and changetime where never exposed to be user-editable. This is definitely new, while integration into Trac Query could be reused should copy existing behavior (with from_to matching) as close as possible. Especially the Trac Query functionality is what I can't wait to have ASAP. Any effort would be highly appreciated. No Trac-Hacks, we need support in core this time.

[Remy Blank]

Please search for existing tickets before creating a new one (although the #1962 above might have been a typo). This is a duplicate of #1942.

[hoff.st@…]

Replying to rblank:

Please search for existing tickets before creating a new one (although the #1962 above might have been a typo). This is a duplicate of #1942.

Sorry, but did that query: 'ticket custom field date' in tickets. It returns 84 matches by now, and did other queries with much more matches too, so must have simply missed it. Mentioned #1962 was no typo but another one to conclude, that true custom timefields was nothing requested/on the way. Thanks for pointing me to the existing predecessor.