Comment 4 for bug 1745425

I appear to be experiencing this problem on version 3.7.2. In my case, it involves a pattern change. The publication in question switched from bimonthly to quarterly. We deactivated the old pattern, created a new active pattern, and predicted the issues based on the new pattern. However, instead of using the initial values we entered into the Predict New Issues dialog, it ignored them and predicted the next issues based on the ones that had been already received. (It predicted v.45:no.7, etc., instead of predicting v.46:no.1, etc.)

We were able to use the "Edit issue holding codes" option to correct the enumeration and chronology to show what they should have been, and prediction of subsequent issues seems to be working. But it was unexpected to encounter this problem in the web interface, since we never saw this behavior in XUL.

I have added the description about the pattern change to this bug, since it seems to apply here more than it does to bug #1797452. That bug describes the Predict New Issues option failing with a new pattern, while we're instead seeing the same behavior as described in the initial report for this bug.