Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#6,313 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
api, backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
192
Forks
310
Merge medio
2 d 13 h
PR fusionados (30 d)
67

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de learningequality/studio

Todos los issues de learningequality/studio

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.