Find features that should be read-only but are not when a group/project is archived

Developer Experience Request

Summary

Background

We recently developed a group archival feature that builds on our existing project archival capabilities. When projects or groups are archived, they should become completely read-only, i.e., no writes should be allowed.

Problem

Our archival features have gaps that allow some writes to go through when they shouldn't. For example, users can still update certain settings on the project settings page even when the project is archived.

What We Need

We need assistance from the quality department to help identify all the places where archived projects/groups should be read-only, but currently aren't. This could be done through automated testing, manual testing, or both.

Requester Information

• Name: Abdul Wadood
• Team: grouporganizations
• Role: Senior Backend Engineer
• Slack Handle: Abdul Wadood

Request Details

• Urgency: Medium
• Requested Completion Date: 2025-10-15
• Is this blocking any release or milestone? No