Fix #5454: Group edits are immediately reflected in the user interface

[guillermo-escire]

References

Fixes #5454

Description

Fixes an issue where edited group details were not immediately reflected in the UI after saving, requiring a manual page refresh.

Instructions for Reviewers

List of changes in this PR:

• Updated GroupFormComponent to refresh the active group state after a successful edit.
• Ensured the form fields are updated immediately using the response payload from the backend.
• Added a unit test to verify that the form reflects updated values after editing a group.

How to test this PR:

1. Log in to DSpace as an administrator.
2. Navigate to Admin → Access Control → Groups.
3. Create a new test group (or use an existing non-system group).
4. Click Edit on the group.
5. Change the group name (e.g. test_group → test_group_updated).
6. Click Save.

✅ Expected behavior:
A success message appears with the updated group name.
The "Group name" field updates immediately without requiring a page refresh.

❌ Previous behavior:
The success message showed the updated name.
The input field still displayed the old name until the page was refreshed.

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You do not need to complete this checklist prior creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

• My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• My PR passes ESLint validation using npm run lint
• My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
• My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
• My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
• My PR aligns with Accessibility guidelines if it makes changes to the user interface.
• My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
• My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
• If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
• If my PR fixes an issue ticket, I've linked them together.

[tdonohue]

👍 Thanks @guillermo-escire ! I tested this and verified this fixes the bug.

[dspace-bot]

Successfully created backport PR for dspace-9_x:

• [Port dspace-9_x] Fix #5454: Group edits are immediately reflected in the user interface #5482

[tdonohue]

@guillermo-escire : It looks like this approach could not be backported cleanly to dspace-9_x because the automatic backport PR #5482 has compilation issues.

If you have a chance to create a manual backport PR for dspace-9_x, then we could still backport this to 9.x.