Frontend: Delete confirmation + reassign-before-delete modals

Aperta
#585 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
58/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python

Direzione di ricerca

Start at the frontend role deletion flow and its existing confirmation modal, then trace how assigned-member counts and role reassignment are handled. Check the relevant modal and mutation tests first; done means both steps match the acceptance criteria, including gating submission, then reassigning before deletion, showing a toast, and refreshing.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

willow

Two-step delete flow (per design):

Step 1 — "Delete ''?" confirmation. Body states the role is assigned to N team members and that you must reassign them to another role before deleting, or confirm to revoke their access permanently. Actions: Cancel, "Reassign members" (secondary -> step 2), "Delete anyway" (destructive — deletes the role and revokes those members' access). A role with 0 members should delete directly from a simple confirm.

Step 2 — "Reassign members before deleting" (after "Reassign members"). Body explains a replacement role will be assigned to the N users to prevent losing access. Controls: a "New role for assigned members" dropdown, a required checkbox "I understand this will update permissions for N members immediately.", actions Cancel / "Reassign & Delete" (destructive, enabled only when a replacement role is chosen and the checkbox is checked). On submit, reassign the members to the chosen role, then delete the original; toast and refresh.

Acceptance
  • Step-1 modal shows the live member count and the three actions; "Delete anyway" deletes + revokes.
  • "Reassign members" opens step 2; step-2 requires replacement role + confirmation checkbox before "Reassign & Delete" is enabled.
  • Submit calls reassign then delete; toast and refresh.
  • Standard roles never reach this flow.

Design: https://www.figma.com/design/xnmQJq1cTRVqNrs31R8zDM/AuthZ---v2?node-id=40000174-2&p=f&t=AfaPxKGH7lD48V93-0

Lingua principale
Python
Stelle
0
Fork
10
Merge medio
5g 12h
PR unite (30g)
23

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di openedx/openedx-authz

Tutte le issue di openedx/openedx-authz

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.