Bug 22178 - Add start and end date for repeated holidays
Summary: Add start and end date for repeated holidays
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
: 24671 39424 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-01-21 08:04 UTC by Katrin Fischer
Modified: 2025-11-19 09:20 UTC (History)
10 users (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Katrin Fischer 2019-01-21 08:04:45 UTC
When weekly or other repeating holidays are changed it will always effect dates in the future, but also in the past. For fine calculation and other reasons this can cause problems. It would be nice if it would possible to start and and repeated holidays at specific dates.
Comment 1 Katrin Fischer 2020-03-15 16:50:43 UTC
*** Bug 24671 has been marked as a duplicate of this bug. ***
Comment 2 Andrew Fuerste-Henry 2020-06-29 15:57:20 UTC
Agreed! This is also an issue if a library wants to do something like mark themselves closed on Sundays over the summer. It'd be great to be able to do that as a holiday repeating on the same day of the week within a range.

Or, at the very least, we should somehow make it clear that those date ranges are not used with repeating holidays. Right now, it's a bit of a trap.
Comment 3 Michael Adamyk 2023-01-09 21:06:20 UTC
I agree. Our consortium has multiple libraries that change their hours and days open over the summer, and it's difficult to make the change. The fact that any new holiday created does display the "To date" even if it's not a range holiday makes it confusing for libraries when that option doesn't work. 

It looks like Bug 17015, a complete overhaul for the Koha calendar, might fix this problem if it gets pushed. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17015
Comment 4 Lindsay 2024-02-26 20:10:40 UTC
Agreed. It makes it hard to make changes to the schedule in advance, because it will affect everything in the past and not at the "start date" you are clicking on.
Comment 5 Katrin Fischer 2025-04-06 16:08:05 UTC
*** Bug 39424 has been marked as a duplicate of this bug. ***
Comment 6 Juliet Heltibridle 2025-11-18 23:38:36 UTC
The way this currently works doesn't make a lot of sense. When you add a weekly repeatable holiday, it gives you an option to choose a start and end date, but it doesn't actually apply those. We are going to need to begin closing our library on Sundays in January, but we will be open on Sundays until the end of the year. So if a patron checks out an item in December on a Sunday, they will be given a Sunday due date. But if we add the repeating holiday in December, it will apply to the days in December we are still open. Since we have some items with a 1 week renewal period and others with 3 weeks, this doesn't work for us.
Comment 7 Katrin Fischer 2025-11-19 09:20:02 UTC
(In reply to Juliet Heltibridle from comment #6)
> The way this currently works doesn't make a lot of sense. When you add a
> weekly repeatable holiday, it gives you an option to choose a start and end
> date, but it doesn't actually apply those. We are going to need to begin
> closing our library on Sundays in January, but we will be open on Sundays
> until the end of the year. So if a patron checks out an item in December on
> a Sunday, they will be given a Sunday due date. But if we add the repeating
> holiday in December, it will apply to the days in December we are still
> open. Since we have some items with a 1 week renewal period and others with
> 3 weeks, this doesn't work for us.

I believe start and end date only work for the "on a range" settings. Not for the weekly ones. This could be better in the GUI, but works as currently intended. Just saying it's not quite a bug, but a missing feature - still quite needed.