RELATED IDEAS
User permissions: prevent users from deleting records
We occasionally have situations where data is deleted and then we realize it needs to be recovered. If we notice this within 7 days we can restore the records from the recycle bin, but we would prefer to disable the ability to delete records for specific users to avoid data loss and to better impose governance.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
3
MERGED
Restrict "reviewers" to delete records
What is the challenge? Current reviewers are deleting records (Initiatives, Releases, Epics, etc.) What is the impact? Lost track of history Describe your idea Ability to include in custom roles the capacity to restrict delete records to only Owners
2
Future consideration
We sometimes have product managers creating placeholders for items that someone else will come to later. The eventual owner sometimes deletes the placeholders in favor of new ones, which would be fine if others weren't already aware of the placeholder Reference Number. We think that removing the Delete permission would cut down on this confusion by encouraging the eventual owner to either use the placeholder or mark it as a dulicate of the new one they created.
We are having issues with individuals deleting initiatives and features causing holes in reporting (was in the before but not after snapshot), "accidentals" that we have to try to recover, and causing orphans to be created. We would like to have the capability to remove the "delete" functionality for contributors in our own workspace and have users instead have initiatives go to "abandoned" and features to "will not implement".