-
-
Notifications
You must be signed in to change notification settings - Fork 95
Description
Overview
When an admin uses the "User Permission Search" feature and navigates into either the "Admins" or "Project Members" search results, edits a user profile, and then clicks "Back to Search," they should be returned to the same search type with updated results. This ensures any profile changes (e.g., removing a user from a project) are reflected immediately upon return.
Context
Currently, when an admin navigates into either the "Admins" or "Project Members" search results, edits a user profile, and then clicks "Back to Search," they are always redirected to the "Admins" search—even if they originally came from the "Project Members" search. Additionally, the list of users is not refreshed to reflect recent updates (e.g., if a user is removed from a project, they still appear in the "Project Members" list as part of that project).
Action Items
- Investigate current navigation and state persistence logic for "User Permission Search."
- Update functionality so that:
- The system remembers whether the admin was viewing "Admins" or "Project Members" before editing.
- After clicking "Back to Search," the same search is reloaded automatically.
- The search results are refreshed to reflect recent profile edits (e.g., users removed from a project no longer appear in "Project Members", admin users changed from "VRMS: Admin: Yes" no longer appear in the list of admins).
- Test for edge cases:
- Editing multiple fields on the user profile.
- Removing/adding a user to/from a project.
- Changing VRMS Admin Status from "Yes" to "No"
- Be sure to revert user profiles once completing testing.
Resources/Instructions
- Review existing "User Permission Search" component and routing logic in VRMS codebase.
Screen recording
Project.Management.bug.mov
Metadata
Metadata
Assignees
Labels
Type
Projects
Status