Vouchers sometimes incorrectly replicate expiration dates

[Bradamante]

Occasionally, when a voucher item is modified to add an expiration date, and another voucher item is modified immediately afterward, the second voucher item will "grab" the expiration date from the first one -- the first one's expiration date will appear as the default for the second, even if the second did not have an expiration date attached.

Initial report from Cameo:

I was modifying a pledge voucher to add an expiration date of Nov 15 2007. Once I was finished modifying this voucher, I added a hedgespun item to another voucher belonging to another player and when the cue for expiration date came up, it had 'Nov 15 2007' entered already as the 'default' instead of 'none'.

Bradamante was able to duplicate this by modifying two items on the same pledge voucher in a row.

Interestingly, after the glitch, when Bradamante went back to remove the expiration date from the first item, the first item (despite having an expiration date in its info) appeared in the modification to have a default expiration date of 'none'!

[nivthefox]

This is probably not fixable; @triggers are notoriously easy to produce this sort of effect on.

Is it particularly bothersome?

[Bradamante]

Expiration dates rarely apply to anything but pledges, but pledges it might be an issue on. However, there should (I think) be associated jobs and other material to construct a correct date?