Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Admin can select the same role in the options section without effect

Aperta
  • Qualcosa non va?
#6,313 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
api, backend

Direzione di ricerca

The report identifies the organization membership detail endpoint, /api/organization-members/{membership_id}/, and the frontend organization membership resource. Start by tracing that resource's PATCH request into the backend handler and its tests. Done means selecting the current role does not save a redundant update or refresh updated_at; the issue itself says it is not open for contribution.

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

Descrizione

bug

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Target branch: unstable

Observed behavior

In the role-selection options for a user, an admin can choose the same role the user already has. The UI sends a PATCH request to the organization membership detail endpoint. The request succeeds, but the user's role remains unchanged; the membership record is still saved and its updated_at timestamp is refreshed.

Errors and logs

No error is returned. The PATCH to /api/organization-members/{membership_id}/ returns HTTP 200 with the membership, even when the submitted role matches the existing role. The backend accepts the role and saves the membership rather than rejecting or skipping the redundant update.

Expected behavior

If the selected role matches the user's current role, the system should prevent the redundant update or clearly indicate that no role change is needed. A redundant selection should not be submitted and saved as an update.

User-facing consequences

This creates confusing UX and makes a redundant selection appear to have been applied even though the user's role did not change. It also refreshes the membership's update timestamp, which can make the record appear recently changed.

Steps to reproduce

  1. Sign in as an organization admin.
  2. Open the organization.
  3. Locate the SHARING section of an organization page.
  4. Select a user in the Users section to open their role options.
  5. Choose the same role that the user already has assigned.
  6. Observe that the PATCH request succeeds, the user's role remains the same, and the membership's update timestamp is refreshed.

Context

The frontend's organization membership resource sends the role update as a PATCH to the organization-members detail route. The backend accepts the unchanged role and saves the membership.

AI usage

The bugs were gathered by a human and later turned into issue descriptions with the help of an AI assistant. The assistant was used to draft the wording and structure of the report, and the final text was reviewed and adjusted for accuracy based on the supplied bug summary.

Lingua principale
Python
Stelle
192
Fork
310
Merge medio
2g 17h
PR unite (30g)
69

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 learningequality/studio

Tutte le issue di learningequality/studio

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.