Emergency closure processing fails if overlap existing closed date

Bug #1869728 reported by Terran McCanna
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
High
Unassigned

Bug Description

In 3.4.2 we are encountering this problem:

If a library has a normal closed date scheduled in the Closed Dates Editor (for example, April 10) and then they enter an emergency closing that encompasses that date (for example, April 5-15) and check the box to Process Immediately, the processing returns 0/0 processed but no other error message.

Tags: admin-pages
Revision history for this message
Diane Disbro (ddisbro) wrote : Re: [Bug 1869728] [NEW] Emergency closure processing fails if overlap existing closed date

Amen!

Diane Disbro
Pronouns: she/her
Branch Manager/Circulation Coordinator
Union Branch
Scenic Regional Library
251 Union Plaza Drive
Union, MO 63084
(636) 583-3224
<email address hidden>

On Mon, Mar 30, 2020 at 9:30 AM Terran McCanna <
<email address hidden>> wrote:

> Public bug reported:
>
> In 3.4.2 we are encountering this problem:
>
> If a library has a normal closed date scheduled in the Closed Dates
> Editor (for example, April 10) and then they enter an emergency closing
> that encompasses that date (for example, April 5-15) and check the box
> to Process Immediately, the processing returns 0/0 processed but no
> other error message.
>
> ** Affects: evergreen
> Importance: Undecided
> Status: New
>
>
> ** Tags: admin-pages
>
> --
> You received this bug notification because you are subscribed to
> Evergreen.
> Matching subscriptions: EV bug mail
> https://bugs.launchpad.net/bugs/1869728
>
> Title:
> Emergency closure processing fails if overlap existing closed date
>
> Status in Evergreen:
> New
>
> Bug description:
> In 3.4.2 we are encountering this problem:
>
> If a library has a normal closed date scheduled in the Closed Dates
> Editor (for example, April 10) and then they enter an emergency
> closing that encompasses that date (for example, April 5-15) and check
> the box to Process Immediately, the processing returns 0/0 processed
> but no other error message.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1869728/+subscriptions
>

Changed in evergreen:
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Steven Mayo (stmayo) wrote :

This may have been incidentally fixed by my patch to https://bugs.launchpad.net/evergreen/+bug/1818912 as I can't seem to replicate on that branch.

Revision history for this message
Terran McCanna (tmccanna) wrote :
Revision history for this message
Andrea Neiman (aneiman) wrote :

Confirming that I cannot recreate this on a test system running a patch for 1818912, so I will mark this one duplicate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.