Issue Summary

When an Assets Object Type is deleted, the Attributes, Attribute Values and Objects that are within that Object Type are also deleted. If during the Object Type deletion the process runs into an error, this can cause the process to fail to complete causing Objects and the Object Type itself to remain in the system and visible via the user interface or API, however the attributes and attribute data remains in the system in an orphaned state.

Steps to Reproduce

1. Navigate to Assets via the User Interface
2. Select a Schema
3. Choose an Object Type to delete
4. Delete the Object Type that was chosen

The errors that cause the process to break can be different, however this has been seen with foreign key issues related to ticket connections. One of the errors seen in UI is:

We were unable to delete your object type. Please check your network and try again.

Expected Results

The deletion process completes in full and removes all the data that is within the Object Type.

Actual Results

If a backend error causes the process to fail, it leaves the Object Type in situ and in most cases leaves the Objects themselves in place, however Attributes and the values stored in the Attributes are missing.

Within the User Interface, trying to access Objects results in an error modal indicating something had gone wrong:

Something's gone wrong

Our team has been notified. If the problem persists, please contact Atlassian Support.
ERROR: 1XM0QIU

Reload page

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

Note: If the deletion was in error and the data can be recreated (ie the data can be re-imported into Assets as your team have a local copy of it), renaming the broken Object Type will allow the Object Type to be recreated.

This will create a new Object Type including a new id so automations, custom fields and such that use the id will need to be updated.

UPDATE: We have a workaround now. When there are failures on object types deletes, customer will either see all the objects back, or see all the objects gone but the object type(s) still in place.

If objects are put back, customer can re-try deleting the object type.

If objects are gone, customer can proceed to delete the object type after 30 mins because it takes the system 30 mins to clean up all the objects and related data. If object type delete failed, wait another 30 mins to delete the object type(s)

UPDATE-2: We have fixed this issue, the above workaround is not valid any more.