-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Response Ops][Cases] Spinner on assigning user to case from case page #191490
[Response Ops][Cases] Spinner on assigning user to case from case page #191490
Conversation
/ci |
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/response-ops-cases (Feature:Cases) |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Async chunks
To update your PR or re-run it, just comment with: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified locally, works as expected 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
elastic#191490) ## Summary Fixes elastic#190303 In 8.15 we disabled a request that showed a spinner while React Query's `isLoading` was true. `isLoading` remains true as long as no data has been received. Because the request was disabled, `isLoading` stayed true the entire time, causing the spinner to be displayed instead of the form that would have activated the request. The fix uses another React Query state called `isFetching`, which is only true while the request is actively being made, so initially, no spinner is shown. ## Release Note Fix endless loading spinner when wanting to add a assignee to a case from the cases list (cherry picked from commit 19f6469)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…ase page (#191490) (#191725) # Backport This will backport the following commits from `main` to `8.15`: - [[Response Ops][Cases] Spinner on assigning user to case from case page (#191490)](#191490) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julian Gernun","email":"17549662+jcger@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-08-29T11:08:33Z","message":"[Response Ops][Cases] Spinner on assigning user to case from case page (#191490)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/190303\r\n\r\nIn 8.15 we disabled a request that showed a spinner while React Query's\r\n`isLoading` was true. `isLoading` remains true as long as no data has\r\nbeen received. Because the request was disabled, `isLoading` stayed true\r\nthe entire time, causing the spinner to be displayed instead of the form\r\nthat would have activated the request. The fix uses another React Query\r\nstate called `isFetching`, which is only true while the request is\r\nactively being made, so initially, no spinner is shown.\r\n\r\n## Release Note\r\nFix endless loading spinner when wanting to add a assignee to a case\r\nfrom the cases list","sha":"19f6469be705d88ec8f3b803e349257d45603f09","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","Feature:Cases","v8.15.0","v8.16.0"],"title":"[Response Ops][Cases] Spinner on assigning user to case from case page","number":191490,"url":"https://github.com/elastic/kibana/pull/191490","mergeCommit":{"message":"[Response Ops][Cases] Spinner on assigning user to case from case page (#191490)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/190303\r\n\r\nIn 8.15 we disabled a request that showed a spinner while React Query's\r\n`isLoading` was true. `isLoading` remains true as long as no data has\r\nbeen received. Because the request was disabled, `isLoading` stayed true\r\nthe entire time, causing the spinner to be displayed instead of the form\r\nthat would have activated the request. The fix uses another React Query\r\nstate called `isFetching`, which is only true while the request is\r\nactively being made, so initially, no spinner is shown.\r\n\r\n## Release Note\r\nFix endless loading spinner when wanting to add a assignee to a case\r\nfrom the cases list","sha":"19f6469be705d88ec8f3b803e349257d45603f09"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/191490","number":191490,"mergeCommit":{"message":"[Response Ops][Cases] Spinner on assigning user to case from case page (#191490)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/190303\r\n\r\nIn 8.15 we disabled a request that showed a spinner while React Query's\r\n`isLoading` was true. `isLoading` remains true as long as no data has\r\nbeen received. Because the request was disabled, `isLoading` stayed true\r\nthe entire time, causing the spinner to be displayed instead of the form\r\nthat would have activated the request. The fix uses another React Query\r\nstate called `isFetching`, which is only true while the request is\r\nactively being made, so initially, no spinner is shown.\r\n\r\n## Release Note\r\nFix endless loading spinner when wanting to add a assignee to a case\r\nfrom the cases list","sha":"19f6469be705d88ec8f3b803e349257d45603f09"}}]}] BACKPORT--> Co-authored-by: Julian Gernun <17549662+jcger@users.noreply.github.com>
Summary
Fixes #190303
In 8.15 we disabled a request that showed a spinner while React Query's
isLoading
was true.isLoading
remains true as long as no data has been received. Because the request was disabled,isLoading
stayed true the entire time, causing the spinner to be displayed instead of the form that would have activated the request. The fix uses another React Query state calledisFetching
, which is only true while the request is actively being made, so initially, no spinner is shown.Release Note
Fix endless loading spinner when wanting to add a assignee to a case from the cases list