-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delay in Displaying User Name and ID after Creation #214
Labels
Comments
R-Sourabh
added a commit
to R-Sourabh/user-management
that referenced
this issue
Apr 18, 2024
1 task
R-Sourabh
added a commit
to R-Sourabh/user-management
that referenced
this issue
Apr 19, 2024
…age on Users page(hotwax#214)
R-Sourabh
added a commit
to R-Sourabh/user-management
that referenced
this issue
Apr 19, 2024
ymaheshwari1
added a commit
that referenced
this issue
Apr 19, 2024
Fixed: case to not display the previous created/selected user information on creating new user by adding a loader(#214)
ymaheshwari1
moved this from 👀 In review
to ⏸️ Dev complete
in Digital Experience Platform
Apr 22, 2024
Issue verified and working fine in release v1.9.0. Hence, closing this ticket. |
github-project-automation
bot
moved this from 🛠 In QA
to ✅ Done
in Digital Experience Platform
Apr 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
After creating a new user, the user interface should immediately display the newly created user's name and ID without any delay or displaying outdated information.
Steps to reproduce the issue
Login the app with valid credentials.
Create a new user in the application by providing first name and last name.
Observe the user interface immediately after user creation.
Notice that the previously displayed username and ID are still visible for a few seconds before being updated with the new user's information.
Environment details
App version: v1.8.0
App environment: UAT
Additional information
https://jam.dev/c/0231523d-8b35-495f-883b-34a7cd82ded8
The text was updated successfully, but these errors were encountered: