You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an admin, I sometimes create spaces or components that, for various reasons, later make no sense to keep, and I want to delete from the administration panel. Currently, I have the option to delete spaces and components under certain conditions, but these actions cannot be undone.
Describe the solution you'd like
As an admin, when deleting a space, component or resource, I want to have the option to send it to the recycle bin, and be able to restore it if necessary.
We've considered the possibility of directly implementing the hard delete, given the arguments and opinions in favor of this option and against the soft delete:
In a future iteration, and to preserve the social contract principles related to transparency, traceability and integrity, we will implement a public log to allow participants monitor any change, similar to https://lemmy.world/modlog. We acknowledge, nonetheless, that it is now possible to de facto remove content from the platform by admins using the unpublish action.
Could this problem affect users' private data?
No, it's about published content.
Acceptance criteria
Given that I am an admin, when I want to delete a space (Process, Assembly or Conference), then I see the action represented with a trash can.
Given that I am an admin, when I want to delete a component (all components except Sortitions), then I see the action represented with a trash can.
Given that I am an admin, when I want to delete a resource, then I see the action represented with a trash can.
Given that a space is published, when I want to delete it, then I must unpublish it first.
Given that a component is published, when I want to delete it, then I must unpublish it first.
Given that the soft delete functionality has been implemented, when an admin or space admin deletes any space, component or resource, then a record is generated in the admin log.
Given that a space has been deleted, when I enter the recycle bin, then I can restore it.
Given that a component has been deleted, when I enter the recycle bin, then I can restore it.
Given that a resource has been deleted, when I enter the recycle bin, then I can restore it.
Given that I'm a resource author (Proposal, Meeting, Debate), when it gets deleted, then I receive a notification that says: "An admin has deleted your "%{resource_type}" "%{resource_title}"
Added specs (Ivan)
If a space is deleted it should not appear in the global search, nor its components.
Is your new feature request related to a problem?
As an admin, I sometimes create spaces or components that, for various reasons, later make no sense to keep, and I want to delete from the administration panel. Currently, I have the option to delete spaces and components under certain conditions, but these actions cannot be undone.
Describe the solution you'd like
As an admin, when deleting a space, component or resource, I want to have the option to send it to the recycle bin, and be able to restore it if necessary.
Prototype
Figma proto
Describe alternatives you've considered
We've considered the possibility of directly implementing the hard delete, given the arguments and opinions in favor of this option and against the soft delete:
But after debating it, we believe there's no need to give up either way. We will now implement soft delete and later an option for permanent deletion.
Additional context
https://meta.decidim.org/processes/roadmap/f/122/proposals/14589
In a future iteration, and to preserve the social contract principles related to transparency, traceability and integrity, we will implement a public log to allow participants monitor any change, similar to https://lemmy.world/modlog. We acknowledge, nonetheless, that it is now possible to de facto remove content from the platform by admins using the unpublish action.
Could this problem affect users' private data?
No, it's about published content.
Acceptance criteria
Added specs (Ivan)
deleted_atand a concern likePublishable