remove user_entry table and use party instead
Using the party table will better facilitate users in the database and not require users to enter themselves twice. Will need to add initials field to party for this.
This will cause some problems for the importing tool.
included special set of instructions for databases that are pre 2.0.6 on import.
importing from older databases now works OK. Entry works fine, too without user_entry. I never liked my name for that table, anyway, so I'm glad it's gone for that reason, too. Best reason is that we don't have 2 tables to track similar data (party/users)
Original Bugzilla ID was 2815
Also available in: Atom