Enable delete role including users

Abierto
#841 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
java
Área
full-stack

Línea de trabajo

The issue does not name files or tests. First clarify which proposed option to implement, then trace the existing role and user deletion flows in the repository. Done means bulk deletion follows the agreed scope and users who cannot yet be deleted receive notifications.

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

Descripción

needs refinement

New Feature Request

Summary

Problem: What is the pain point? (e.g., "Users cannot filter results by date.")
We want to enable deleting a role including all users. Now needs to be done one-by-one for a user. This does not scale to roles with large amount of users.

Value: Why should we build this? (e.g., "Improves data accessibility for
power users.")

Proposed Solution

Option 1: limit functionality to to enable 'delete all' for all selected users after 'select all users'.

Option 2: enable delete role including all users.

Both options should include notifications when users could not yet be deleted.

  • Action: Describe the logic or flow change.
  • Design: [Link to Figma/Screenshots]
  • Impact: Does this affect existing APIs or UI components?

Developer Checklist

To be completed by the developer during implementation.

  • Add required changes and feature flags config files
  • Create and document database changes and migrations
  • Create and document API changes and migrations
  • check for backwards compatibility
  • Updated CHANGELOG and other documentation where needed

Testing and QA

Describe how to verify and test this change.

Test Environment and Setup
  1. Point to [URL/Branch]
  2. Use account with [Role/Permissions]
Test Checklist
  • Happy Path: Feature works as intended under normal conditions.
  • Edge Case: [Describe specific test item]
  • Validation: [Describe specific test item]
  • UI/UX: Verified layout across screen sizes.

Extra Information

Add any other context, related issues, or technical notes here.

Lenguaje dominante
Java
Estrellas
6
Forks
8
Merge medio
1 d 15 h
PR fusionados (30 d)
14

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

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 OpenConext/OpenConext-Invite

Todos los issues de OpenConext/OpenConext-Invite

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.