[UICAL-262] Calendar not allowing save with open hours on Google Chrome Created: 14/Feb/23  Updated: 24/Mar/23  Resolved: 01/Mar/23

Status: Closed
Project: ui-calendar
Components: None
Affects versions: None
Fix versions: 8.0.4

Type: Bug Priority: P1
Reporter: Molly Driscoll Assignee: Noah Overcash
Resolution: Done Votes: 0
Labels: Support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: JPEG File bugfest_cal.jpg     JPEG File snapdev_cal.jpg    
Issue links:
Duplicate
duplicates UICAL-239 Editing a calendar shows false error ... Closed
Sprint:
Development Team: Bama
Release: Nolana (R3 2022) Hot Fix #1
Potential Workaround: Use Firefox to manage calendars.
RCA Group: TBD
Affected releases:
Nolana (R3 2022)

 Description   

Overview: After the upgrade to Nolana, I am trying to create a new calendar in Settings > Calendar and am prevented from saving. There is an error indicator in the UI, but when I open developer tools, I don’t see any requests initiated when I click save.

Steps to Reproduce:

  1. Log into Bugfest Nolana with admin permissions.
  2. Open the Settings app.
  3. Click Calendar > All calendars
  4. Click Actions > New
  5. Enter a calendar name
  6. Enter a start date of 01/01/2024.
  7. Enter an end date of 05/31/2024
  8. Under Hours of operation:
    1. Select status = open
    2. Start day = Sunday
    3. Start time = 09:00 AM
    4. End day = Sunday
    5. End time = 05:00 PM
  9. Click Save & close

Expected Results: Calendar is saved with one opening day.
Actual Results: A red exclamation point appears in the start time field. If you “fix” that field, the indicator moves to the end time field. This continues to happen. Saving does not do anything and no error are present in developer tools.
**

Additional Information: I am able to replicate in a local tenant and on Bugfest Nolana in Chrome, but Firefox works as expected. This has been experienced by some of my colleagues as well.

Cheryl Malmborg confirmed that she was able to successfully create and save a calendar with open hours in Chrome on version 109.0.5414.75, but began experiencing the same behavior I am reporting after Chrome auto-updated to version 110.0.5481.100. I am on version 110.0.5481.100, as well.

Potential related issues:

https://folio-org.atlassian.net/browse/UICAL-253

https://folio-org.atlassian.net/browse/UICAL-251

https://folio-org.atlassian.net/browse/UICAL-261

https://folio-org.atlassian.net/browse/STCOM-1088 

URL:
Interested parties: Michelle Suranofsky Brooks Travis Cheryl Malmborg Erin Nettifee 



 Comments   
Comment by Molly Driscoll [ 14/Feb/23 ]

Additional details and troubleshooting measures available in Slack thread here: https://folio-project.slack.com/archives/C3G05TF3R/p1675258127868779

Comment by Cheryl Malmborg [ 14/Feb/23 ]

I was able to successfully edit a fixed due date schedule and enter a request expiration date using the date picker.

Comment by Erin Nettifee [ 15/Feb/23 ]

Molly Driscoll you were not able to replicate this on Snapshot, right? If that's correct, I would argue for downgrading this to a P2, since the affected release is out already and since a workaround exists. See https://folio-org.atlassian.net/wiki/pages/viewpage.action?spaceKey=DQA&title=Defect+Priority+Definition+for+Functional+Issues

Comment by Molly Driscoll [ 15/Feb/23 ]

Erin Nettifee correct; I was not having this problem on Snapshot. 

That's an interesting point about the priority. I think I'll defer to the Support SIG on this. While I cannot recreate the problem in Firefox, I've been told repeatedly that Chrome is our only supported browser, so I'm personally unclear if routing outside of Chrome for a workaround is viable. It'd be nice to have that clarified in the priority definitions for the future.

Comment by Molly Driscoll [ 15/Feb/23 ]

I also recently had this ticket escalated out of local support: https://folio-org.atlassian.net/browse/CIRC-1737

I'm not sure the issues are related, but where it's manifesting with short-term loans and a calendar error, I wanted to raise in case it alters the priority of either issue/if it can help establish a pattern at all.

Comment by Cheryl Malmborg [ 15/Feb/23 ]

I see one difference between bugfest and snapshot. In snapshot, the time picker opens with blank hours and minutes ( hh mm). In bugfest, the time picker opens with the current local time.

I don't know if this is significant. Screen shots attached.

Comment by steven turner [ 16/Feb/23 ]

I believe this is resolved.

Comment by Oleksii Petrenko [ 22/Feb/23 ]

Deployed to Nolana bf env. Please proceed with verification

Comment by Noah Overcash [ 01/Mar/23 ]

Oleksii Petrenko would you please deploy ui-calendar v8.0.4 to BF for verification?

Comment by Sobha Duvvuri [ 02/Mar/23 ]

Oleksii Petrenko : May I know if this has been verified on Bugfest?

Comment by Noah Overcash [ 02/Mar/23 ]

Sobha Duvvuri still waiting on this version to be added to BF; PR

Comment by Noah Overcash [ 23/Mar/23 ]

Sobha Duvvuri I've been able to manually verify it's fixed in BF; if you would please do the same to confirm then we can close this ticket!

Comment by steven turner [ 23/Mar/23 ]

Thanks Noah.

Comment by Oleksii Petrenko [ 24/Mar/23 ]

Deployed and test at Nolana bf - https://foliotest.testrail.io/index.php?/runs/view/2159

Closing

Generated at Thu Feb 08 22:23:08 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.