Skip to content
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

[BUG] CRUD operation leaving visible stale data in UI with no loading indicator #1743

Open
1 task done
ibolton336 opened this issue Mar 5, 2024 · 1 comment
Open
1 task done
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/normal Higher priority than priority/minor. Nice to have. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@ibolton336
Copy link
Member

Is there an existing issue for this?

  • I have searched the existing issues

Konveyor version

7.0.2

Priority

Critical

Current Behavior

Currently when a user performs any CRUD operation, we are showing a notification but rely on the next successful fetch to update the table data. On slow connections, this can result in some confusion re: if the users request has truly gone through as successful.

Screen.Recording.2024-03-05.at.10.10.14.AM.mov

Expected Behavior

I propose that we show a loading indicator within the modal while the operation is still ongoing. Once the operation is complete, we can then close the modal & perform a fetch of the relevant data so that the user is not left feeling as if the app is frozen. This change will inspire confidence in the application & improve error handling.

How Reproducible

Always (Default)

Steps To Reproduce

No response

Environment

- OS:

Anything else?

No response

@ibolton336 ibolton336 added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 5, 2024
@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@konveyor-ci-bot konveyor-ci-bot bot added the needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. label Mar 5, 2024
@ibolton336 ibolton336 self-assigned this Mar 8, 2024
@sjd78 sjd78 added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/normal Higher priority than priority/minor. Nice to have. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. labels Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/normal Higher priority than priority/minor. Nice to have. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: 🔖 Ready
Development

No branches or pull requests

2 participants