We have several projects with a variety of custom fields. Those custom fields are tied to a LOV table so user must select one of the values we have in the table.

We have a situation where we want to change the LOV and make certain values no longer able to use and add new LOV. However, if we delete those values from the LOV table, older tickets will be invalid.

Any thoughts on how to handle this situation?

I think we're looking for something similar to how deleting users and archiving projects work - the records aren't actually deleted from the database to retain referential integrity, but are no longer available for use when creating new records.

Thanks.