Start up a classic tracker. Create an issue
with a title and some 
starter change note.
Set the priority and submit the new 
issue.

Now set the superseeder field to a non-existant 
issue
number that is larger than any issue. Also add 
another
user to the nosy list and put a keyword in the topic 
list
along with a bogus keyword, select an assigned to 
person
and try to upload a file, and put in a change 
note.

Submit the changes. You will see an error, but
all 
the entered data has disappeared, except
for the change 
note.

Is there any reason that this preservation of 
data
shouldn't be extended to include all fields?

I think 
that the field() and menu() items should
automatically try to 
keep the data that was submitted,
and if no data was 
submitted, then they should
take on the values that are in the 
hyperdb.

-- rouilj

Logged In: YES 
user_id=9205

I think this is a fundamental design thing: if you change X
entries and one of it is invalid, all changes are thrown
away (even the valid ones).
This has also been reported as a bug in Debian Linux. See
http://bugs.debian.org/193843 for more info.