Enable delete role including users

未关闭
#841 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
java
领域
full-stack

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Java
星标
6
派生
8
平均合并
1 天 15 小时
30 天内合并 PR
14

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

OpenConext/OpenConext-Invite 的其他 Issue

查看 OpenConext/OpenConext-Invite 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。