Feedback issue: Deletion flow enhancements

Background

In &17365, we are updating the current deletion flow for groups and projects in GitLab across 3 iterations as follows:

1. Iteration 1: Basic Recovery Framework
   • Implement consistent pending deletion period before permanent deletion for all pricing tiers
   • Add self-service recovery options for all deleted items
   • Standardize UI for deletion status across user and group namespaces
   • Implement consistent automated renaming to free up paths immediately
2. Iteration 2: Extended Deletion Protection
   • Extend pending deletion period from 7 to 30 days on SaaS
3. Iteration 3: Enhanced Deletion Interface
   • Introduce dedicated "Trash" section in UI for managing deleted items
   • Create clear separation between "Move to Trash" and "Delete Permanently" actions
   • Implement bulk actions for trash management (restore multiple, empty trash)
   • Add filtering and sorting capabilities in the "Trash" UI

See also the related architecture blueprint for reference.

Purpose of this Epic

The purpose of this Epic is to collect feedback from customers and internal team members. Our goals are to identify and prioritize bugs and issues, capture ideas for new features and improvements, and ultimately enhance user satisfaction and product quality. Your input is crucial in helping us understand and address the needs of our users, ensuring that our product continues to evolve and improve.

How to give feedback

1. Check existing feedback & known issues: Before submitting, check to see if there is already an issue linked in this Epic or discussion in the comments of this Epic. If so, comment on the existing thread or leave an emoji reaction to show support.
2. Start a new thread: If your feedback is not listed, start a new thread with a descriptive title in this Epic. Include relevant details, screenshots, and steps to reproduce the issue in expandable sections.
3. Be Specific: Provide as much detail as possible, including device/browser information, steps to reproduce, and expected vs. actual outcomes.

What you can expect from us

1. We will read all of your feedback.
2. We may not respond to all feedback directly.
3. We will create issues for repeatable bugs and assign a priority based on severity.