Bug 15483

Summary: in a weekly serial subscription, the second planned issue corresponds to third publisheddate
Product: Koha Reporter: Koha Team University Lyon 3 <koha>
Component: SerialsAssignee: Bugs List <koha-bugs>
Status: CLOSED WORKSFORME QA Contact: Testopia <testopia>
Severity: major    
Priority: P5 - low CC: colin.campbell, nick
Version: Main   
Hardware: All   
OS: All   
GIT URL: Initiative type: ---
Sponsorship status: --- Comma delimited list of Sponsors:
Crowdfunding goal: 0 Crowdfunding committed: 0
Crowdfunding contact: Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:
Attachments: skipping_second_planneddate

Description Koha Team University Lyon 3 2016-01-06 15:14:07 UTC
Created attachment 46333 [details]
skipping_second_planneddate

in a weekly serial subscription, the second planned issue corresponds to third plannedddate
Lest's take the following simple example :
a weekly serial, subscription startdate 2016-01-01, enddate 2017-12-31, beginning by number 1 planned on 2016-01-02
we are expecting number 2 to be planned on 2016-01-09 but the results is :
N°1 - 2016 	2016-01-02 	
N°2 - 2016 	2016-01-16 	
N°3 - 2016 	2016-01-23 	

Curiously, it works from the 2016-01-04 as first planneddate.
N°1 - 2016 	2016-01-04 	
N°2 - 2016 	2016-01-11 	
N°3 - 2016 	2016-01-18

But, we have sometimes the same problem when going through one year to another :
N°43 - 2015  2015-12-21
N°44 - 2016  2016-01-04
N°1  - 2016  2016-01-18

Olivier Crouzet
Comment 1 Nick Clemens (kidclamp) 2019-12-10 14:57:20 UTC
Cannot recreate, please add details of numbering pattern used if this issue recurs