I've just upgraded from FB 7.1.13 to 8.0.32 (for Windows).
In importing our legacy defect tracking system, I created a large number of "transiently-active" users to preserve the history of who initially reported the defect. Once we went "live," I noticed that these users showed up as e.g. "User 133" instead of "Brad Majors" for accounts of users lacking administrative privileges. I determined at that time this problem could be resolved by temporarily activating the account, providing the account with write permission for the group associated with the case projects, and then deactivating the user again. I eventually got the nerve to run the following SQL:
INSERT INTO acl (sSectionName, ixSection, ixPerson, iPermission) SELECT 'Group', '1', person.ixPerson, '1' FROM person WHERE person.fDeleted=1;
I am aware of this question about user name visibility, which has helped me understand the reason for the problem.
After upgrading, however, I have encountered the same problem again. I can use the same procedure I used before of activating the user, granting group membership, and the deactivating the user, but it is slightly more troublesome now, as all our licences are now in use, and I don't understand the new permission model and the schema well enough to risk modifying the database directly.
This seems to me a (slight) flaw in the otherwise seamless upgrade process.
Can anyone suggest a shortcut I could take to remedy this?