Databases with links or multilinks to retired items 
may be undisplayable after an 
export/delete/import cycle:

a) user X creates a number of issues
b) user X leaves the company
c) roundup admin retires user X from the database

All is well here: user X is still correctly shown in the 
web interface as the creator of his issues. He'll still 
also get shown correctly on any issues on which 
he's nosy or assignto'ed, although when we edit 
such issues we'll be reminded that we need to 
unnosy/unassign him.

However, if we want to migrate the backend as per 
the "Maintaining Roundup" documentation:

d) roundup admin exports database
e) roundup admin deletes db folder
f) roundup admin imports database

the web interface crashes into a traceback when it 
attempts to display any issues on which user X was 
creator, assignedto, or nosy -- although the issue 
is still linked to user X's ID, user X's ID is not found 
in the database.


No big deal for us -- I've just retired a load of 
issues after duplicating a multi-purpose tracker to 
form two more-specific trackers, and I was 
wondering what an export/delete/import cycle 
would do in terms of database size -- but a big 
gotcha for anyone planning to migrate backends.

Logged In: YES 
user_id=6405

This is fixed, thou 

Logged In: YES 
user_id=6405

This is fixed, thou