Thanks Ryan Actually, I was wonder if there was a better way to handle it using Trac's core.
The problem with the custom field approach, in general, is regarding to the additional join it requires that in some cases. Maybe it is not too relevant, just from the performance point of view or about queries complexity. Some of my queries sums up 3-6 joins, those with multiple custom fields mixed with information from tables related to macros and plugins. EmeCas On Tue, Dec 12, 2017 at 2:09 PM, RjOllos <rjol...@gmail.com> wrote: > > > On Monday, December 11, 2017 at 3:20:33 PM UTC-8, emecas wrote: >> >> Hi >> >> Different than using milestones or a custom field, Is there another way >> to achieve a due date functionality for the tickets? >> >> I have review an interesting plugin (working OK with Trac 1.2) that >> address partially this requirement, QueuesPlugin [1]. >> >> Wonder if someone knows about any alternative way to handle a due date >> concept in Trac. >> > > What are you requirements? In what way does a custom field not fulfill > those requirements? > > - Ryan > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to trac-users+unsubscr...@googlegroups.com. > To post to this group, send email to trac-users@googlegroups.com. > Visit this group at https://groups.google.com/group/trac-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
