Details
-
Bug
-
Status: Closed (View Workflow)
-
P1
-
Resolution: Done
-
None
-
None
-
Bama
-
TBD
Description
Overview:
Experienced today on Snapshot and Snapshot-2. On both environments I am logged in as the diku_admin user.
On Snapshot, I am unable to set time slots as expected. The end time input is basically not workable. Both the start and end time fields remain with a red ! and I cannot get an end time to stay in the box. Here's a screencast (~2 mins long, with audio narration describing what I'm typing) calendar-bug.mp4
On Snapshot-2, I can get an end time to say in the end time box, but the calendar will not save.
This behavior does not appear to be on Bugfest Nolana, so something has changed between then and Snapshot now.
Expected Results:
Actual Results:
Additional Information:
URL:
Interested parties: ncovercash sjturner1
TestRail: Results
Attachments
Issue Links
- duplicates
-
UICAL-239 Editing a calendar shows false error message in start date field on save, if start date was edited
-
- Closed
-
-
UICAL-259 bump stripes to 8.0.0 for Orchid/2023-R1
-
- Closed
-
- relates to
-
STCOM-326 Use reduxFormField() with <Timepicker>
-
- Closed
-
-
STCOM-568 TimeDropdown generates console warning
-
- Closed
-
-
STCOM-652 Fix accessibility problems for Timepicker
-
- Closed
-
-
STCOM-707 refactor Timepicker away from componentWillReceiveProps
-
- Closed
-
-
STCOM-1088 Timepicker Refactor
-
- Closed
-