After using Issue Manager for a while, you may find that you have issues in the database that are no longer relevant to your efforts (for example, issues that are closed or pertain to unsupported products). The more issues in the database, the longer actions (such as queries) take to execute. To help you improve performance, you can archive issues. You can then run actions against the smaller number of active (not archived) issues.
When you archive issues, Issue Manager moves the issues from the DEFECT and related tables to the ARCHIVE and related tables. All issue information is preserved. (By comparison, active issues remain in the DEFECT table, and users can take the usual actions on them.)
Users may view archived issues on the Issue Details page but they cannot take actions on them because they are read-only. Archived issues do not appear in users’ inboxes. However, users may still run queries, reports, and graphs against archived issues. Archiving “hides” issues in a database, but it does not delete them.
You may however, want to make your production database smaller by creating a new custom database that imports only the active issues and related information from the original database.
If you archive an issue that is being displayed (but not edited) on a user’s desktop, the user won’t know about the change until they log out and log back in again, exits and restarts, or tries to take an action on the issue.