Closed Matvey-Kuk closed 1 year ago
@raphael-batte 's comments from #525:
Schedules list:
Schedule detailed page:
Hey team, I decided to do a pretty diligent "final check". There is a chance that some of points mentioned here are not actual bugs. Please ignore them in this case:
Tested in ops.grafana.net, r36-v1.0.50, chrome:
https://user-images.githubusercontent.com/3284841/199861595-8e8cdfa7-5097-4ef3-b12e-cb8d841fc192.mov
I think it's a frontend & backend bug. Frontend shouldn't lock after 500's. Backend obviously shouldn't give us 500's :)
https://user-images.githubusercontent.com/3284841/199862402-6afbd3df-918b-48ea-8ea0-7fe6ff0cde32.mov
https://user-images.githubusercontent.com/3284841/199862733-8a5cb83b-fb80-4fe5-9583-293dd9b5f8eb.mov
I didn't realize we already show all schedules in "Schedules alpha" page. So #0 and #1 are not relevant. Let's just remove old schedules page.
- Cannot delete override which is happening now:
@maskin25 I checked the backend part, the override deletion works the same as deletion of regular shifts.
When making a DELETE request, backend returns 204 and sets the until
property to current time. This seems to be working fine for regular (non-override) shifts, so could you please check if there's some issue on the frontend part for overrides?
- Cannot delete override which is happening now:
@maskin25 I checked the backend part, the override deletion works the same as deletion of regular shifts. When making a DELETE request, backend returns 204 and sets the
until
property to current time. This seems to be working fine for regular (non-override) shifts, so could you please check if there's some issue on the frontend part for overrides?
FYI, I was also checking, indeed the until
is being set, but there is some change required in the backend to enforce the until
in overrides shifts (no changes should be required in the frontend as far as I can tell), I have a PR in progress with the update (and some other schedule-related fixes I'm working on)
- Cannot delete override which is happening now:
@maskin25 I checked the backend part, the override deletion works the same as deletion of regular shifts. When making a DELETE request, backend returns 204 and sets the
until
property to current time. This seems to be working fine for regular (non-override) shifts, so could you please check if there's some issue on the frontend part for overrides?FYI, I was also checking, indeed the
until
is being set, but there is some change required in the backend to enforce theuntil
in overrides shifts (no changes should be required in the frontend as far as I can tell), I have a PR in progress with the update (and some other schedule-related fixes I'm working on)
good, let me know when you're done
[ ] Prop 1. Add more clear message UI to iCal and API calendars. + Management buttons should be hide
[ ] Prop 2. Remove message from the top and add tooltips for disabled buttons.
[ ] Add overrides feature to iCal/API schedules
User presentation visual issues
[ ] shift color border should be positioned to the center or outside parent shape (now it is inside and we can see artifacts)
[ ] users outside working hours should be disabled visually. Example - Singapore users already outside their working hours but look similar to others.
[ ] some users have 2rows name-presentation
Closing this due to agreement not to make it a permanently open issue. @raphael-batte please file separate issues 🙏
Logical blocks: https://github.com/grafana/oncall/issues/531