IQSS / IQSS/dataverse-frontend

“Group Creation Failed” when creating a group that initially includes another group as a member, no stack trace

Open
#831 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
31
Forks
26
Avg merge
4d 13h
Merged PRs (30d)
4

Description

Summary:
On internal (running a recent develop build), creating a new group with another group selected as a member during creation fails with a UI error banner: “Group Creation Failed.” Creating the group first and then adding the subgroup(s) afterward succeeds (workaround).

Environment

Server: dataverse-internal

Version/branch: develop (2025-09-15)

Browser: Chrome (latest)

Logs: No relevant stack traces observed in server.log during failure

Steps to Reproduce

Go to Admin > Permissions > Groups (any dataverse scope).
Click Create Group.
Create Group A; add 1–2 user members; save (succeeds).
Click Create Group again.
Create Group B and, before saving, add Group A as a member (along with optional user members).
Click Save.

Actual Result
UI shows a banner: “Group Creation Failed.”
The group is not created.
Server log shows no obvious error lines at the time of the attempt.

Expected Result
Group B is created successfully with Group A listed as a member (and any users), and appears under Manage Permissions > Groups.

Workaround
Create the new group without any members first, save, then edit the group and add users and groups afterward. This path succeeds.

Reproducible on dataverse-internal (develop).

Previous issue was closed since there were other priorities: https://github.com/IQSS/dataverse/issues/5197

https://github.com/user-attachments/assets/47a6f79b-ac05-4663-802c-a9e3d694773b

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Admin > Permissions > Groups create-group flow in the frontend and reproduce the failure using an existing group as a member. Trace the request and error handling for initial group creation, then verify that a group with a subgroup member is created successfully and appears under Manage Permissions > Groups.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authorization, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.