Nice update, but: this is very danger action and there is no comfirmation that it delete entity with (and) 365 relations!!!
In 99% cases i want to remove relation, not delete entity! And red as a warning is not enough.
Yesterday I wrote down a draft of this bug report, but didn’t manage to send it yet today, as a colleague really deleted one ‘customer’ from the ‘CRM’ app and did not even notice this - all tasks, stories, features, epics, products, repositories associated with the client were untied
Also there is no access level “can edit, but can’t delete” to prevent expected negative effects because of this feature
I was disable editor access for all other users for some critical ‘apps’, but for myself, I would also be willing to hide it, because some entities, such as ‘customers’ in app ‘crm’ are relatively “eternal”, it makes no sense to allow them to be deleted so easily, and they are also “root” and contain a lot of connections. Before deleting such an entity, there should be a warning: “Do you want to delete an entity with 365 connections, do you definitely want to do this?”
One of the temporary solutions is to disable this feature until it is noticeably improved
This will not frighten the old-timers, they will probably restore everything from backup if they catch on time (we caught on at the wrong time and made many changes after the indent, so it was easier to restore relations than roll back)
But for beginners, this situation will probably scare them away from Fibery