On Monday, February 25, 2019 at 7:19:21 AM UTC-8, [email protected] wrote: > > New custom fields add history record the next time every old ticket is > edited. > > Note: We use Trac 0.12.3 because that's the version our host > (RepositoryHosting.com) uses. I realize that Trac 1.2.3 is the latest > stable release. I can't fix our version without leaving > RepositoryHosting.com. > > I created a custom field in our RH Trac — a checkbox. Then whenever > someone would edit a Trac ticket that existed *before *this custom field > was created, the commit of that edit would result in a history record in > that ticket saying (sorry, I don’t have one of these in front of me) that > the _new_custom_field had been set to its default value. > > Is there any way to create a custom field and not get this behavior? It's > just noise to us. If this is fixed in a later version of Trac, well, I'd > like to know that, too. > > Thank you! >
The behavior still exists. For example, adding: [ticket-custom] checkbox = checkbox checkbox.value = 0 results in: [image: Screen Shot 2019-02-25 at 13.54.03.jpg] <about:invalid#zClosurez> I've also considered this behavior to be displeasing ever since I started using Trac. I created a ticket for the issue: https://trac.edgewall.org/ticket/13133 - 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
