[UICAL-273] Duplicate Calendar Error Upon Save & Close Created: 07/Jul/23 Updated: 09/Nov/23 Resolved: 09/Nov/23 |
|
| Status: | Closed |
| Project: | ui-calendar |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P3 |
| Reporter: | Sarah Johnson | Assignee: | Pax Nguyen |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | 4, support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | Bama Sprint 178, Bama Sprint 177 |
| Development Team: | Bama |
| Release: | Poppy (R2 2023) Bug Fix |
| Affected Institution: |
!!!ALL!!!
|
| RCA Group: | TBD |
| Affected releases: |
Orchid (R1 2023), Nolana (R3 2022)
|
| Description |
|
Overview: When duplicating a calendar, current functionality prevents user from Saving and closing the new calendar if exception dates do not fall within the calendar's start and end date range. The Calendar name and date range then revert back to the original data from the calendar being duplicated Steps to Reproduce:
Expected Results: The calendar will save with the current adjustments as a draft so that exceptions and open/close times can be entered later.
OR the error message will alert the user that the exceptions need to be updated as well, without impacting the changed calendar name and date range. Actual Results: Upon save & close, an error message displays at the top of the screen if there are any exceptions that fall outside of the new calendar's date range. The calendar name and date ranges then revert back to the data that was stored in the calendar that is being duplicated. Additional Information: Ideally, a library would be able to duplicate a calendar with a new name and start and end dates. Then, upon saving and closing the new calendar, they could come back into it to edit any exceptions. At the very least, the updated calendar name and date ranges would persist despite the error message so that the exceptions could be updated accordingly. URL: |
| Comments |
| Comment by Ann-Marie Breaux (Inactive) [ 11/Jul/23 ] |
|
Hi Noah Overcash There was no dev team on this bug, Looks like it should be Bama? Please reassign if that's not correct. Thank you! |
| Comment by Anya [ 28/Aug/23 ] |
|
Support : steven turner please be aware . Marking this as a P3 - cause the libraries could make a new cal and not duplicate it. |
| Comment by Charlotte Whitt [ 18/Sep/23 ] |
|
Support : steven turner please be aware of this ticket. The bug has gotten the priority as a P3, but is affecting all libraries. |
| Comment by Anya [ 25/Sep/23 ] |
|
Support : steven turner please be aware of this ticket. The bug has gotten the priority as a P3, but is affecting all libraries. |
| Comment by Thomas Trutt [ 02/Oct/23 ] |
|
SUPPORT: Noah Overcash or steven turner, please see the comment above. Please assign an owner and a release. |
| Comment by steven turner [ 02/Oct/23 ] |
|
We are reviewing, and finding and appropriate dev, and expected due date. We have not yet confirmed the bug. |
| Comment by steven turner [ 02/Oct/23 ] |
|
This is now being worked on. |
| Comment by Anya [ 09/Oct/23 ] |
|
Support: steven turner what is the release target. |
| Comment by steven turner [ 09/Oct/23 ] |
|
Anya, we should be finished, hopefully, with the bug by end of day. |
| Comment by Anya [ 16/Oct/23 ] |
|
Support: steven turner what is the release target? Currently, it is not set in the details of the Jira Ticket. Thanks |
| Comment by steven turner [ 16/Oct/23 ] |
|
I am unsure. Hopefully this week. |
| Comment by Anya [ 23/Oct/23 ] |
|
Support: steven turner what is the release target? Currently, it is not set in the details of the Jira Ticket. Thanks Will this be part of Poppy- for now, we have put it into Poppy bugfix - but let us know if that is correct. |
| Comment by steven turner [ 23/Oct/23 ] |
|
When I speak to my programmers today at our 3 pm standup, I will be able to project a release target and ETA at that point, and I will modify the Jira ticket. We are attempting to target Poppy. |
| Comment by steven turner [ 30/Oct/23 ] |
|
We are still working on resolutions. ETA is not known at this time, too many factors. |
| Comment by steven turner [ 02/Nov/23 ] |
|
Discussing today - we cannot replicate - |
| Comment by steven turner [ 03/Nov/23 ] |
|
I believe this item cannot be reproduced, checking with devs. |
| Comment by steven turner [ 03/Nov/23 ] |
|
Yes, cannot be duplicated by two devs. We need the reporter to contact either Noah or Pax to discuss environment, browser, etc. |
| Comment by Sarah Johnson [ 03/Nov/23 ] |
|
I responded to Pax in Slack yesterday afternoon to let him know we were using our training environment which is on Orchid-SP-6. |
| Comment by steven turner [ 07/Nov/23 ] |
|
thank you, Sarah. |