Data consistency issue when deleting all milestones and creating a new ticket

[laci@…]

Reproduction:

1) Remove all your milestones and retarget your tickets into the empty milestone.

2) Create a new ticket.

3) The new ticket is under a different milestone called "None" than all the other tickets.

The new ticket should be under the empty milestone, not under the "None" milestone.

[Remy Blank]

Confirmed on current trunk. It seems that reassigning tickets when deleting a milestone will set the milestone field to the empty string, whereas creating a new ticket when no milestones are defined sets the milestone field to NULL.

I wonder if this has something to do with [7570]. Are you using a fresh checkout from 0.11-stable, or an official release?

[Remy Blank]

Replying to rblank:

I wonder if this has something to do with [7570].

No, it hasn't. The behavior is the same before that changeset.

[Remy Blank]

Fixed in [7581]. Thanks for the bug report.

[Christian Boos]

See also #11018. We need to document somewhere what we want it to be. NULL for not yet set, unset or deleted fields seems indeed appropriate.

[Remy Blank]

I'm not completely sure anymore about what we want. At some point we had introduced the empty object so that NULL would be read as a "special" string and we would avoid spurious diffs due to NULL ⇔ "" changes, but IIRC this was only for custom fields.