Initializing ticket custom fields

2 views

Skip to first unread message

Tim Hatch

unread,

Dec 21, 2006, 3:20:56 PM12/21/06

to Trac Development

This is about the third time I've been bitten by this. I don't know if
it's "by design" or a genuine bug.

1. Create some tickets
2. Add a custom field, anything you like
3. Comment on a ticket, leaving the custom field blank.

I then get a cryptic email that says "field_name => " implying that it
went from "empty" to "empty", along with my comment. I think I
understand why this is happening (nonexistent changing to the null
string), but wonder if it's supposed to show up as a change.

Ideas?

Tim

Tim Hatch

unread,

Dec 21, 2006, 4:41:54 PM12/21/06

to Trac Development

I decided this was ticket-worthy, so followups to
http://trac.edgewall.org/ticket/4447