| Issue Number | 75 |
|---|---|
| Summary | [Printing] end date problem on board member name? |
| Created | 2013-09-17 16:47:41 |
| Issue Type | Bug |
| Submitted By | alan |
| Assigned To | alan |
| Status | Closed |
| Resolved | 2014-08-26 11:13:45 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/oceebms/issue.113399 |
OCEDRUEBMS entered 2013-08-13 by Alan Meyer (in Open status)
Bonnie reported on 8/9/2013 that she tried to produce a print packet for a board member who had an ending print date of 8/12/2013. The system said there was nothing to print for this board member. After removing the end date there was something to print.
It appears that the end date processing software has gone awry and needs fixing.
I have this working on DEV. I've also cleaned up the program that Bonnie uses to set printing start and end dates for board members so that it does more error checking and gives more useful error messages.
I'm not quite ready to declare it resolved because I want to do some more testing and think a bit more about the meaning of start and end dates - which are a little ambiguous in the system as to whether they refer to packet creation dates or current dates, or both.
Robin and Bonnie ran into a problem testing this. It was due to a
software configuration error on my part.
I made the changes for this before we created a new version control
branch for EBMS 3.1. Knowing that it was not supposed to be released
until after 3.0 was deployed, and also wanting to think about the
possibly ambiguous meanings of "start date" and "end date" in relation
to packets on the one hand and member print requests on the other, I
didn't put the changes into version control, planning to do it after the
3.1 branch was created. However I did put the software into the live
directory for Dev so it could be tested. I then went to work on other
issues and forgot about this.
Seven days and some consultations later, I created the 3.1 branch. It
only contained the old code for the file that was modified, but I forgot
that and didn't update it or the version control. Checking everything
tonight I couldn't find the changes I had made until I finally realized
what happened. Digging into my old "sandbox" for the 3.0 release, I
found the changes and installed them again on Dev.
Once I discovered all this and installed the correct software, I stopped
trying to trace exactly why the version that Robin and Bonnie tested on
Dev failed. There may have been a mix of software in the directory that
contained an incompatibility somewhere. It could take a few hours to
track down so I stopped work on that.
I apologize for wasting Robin and Bonnie's time on this.
I've committed the new code to version control for EBMS 3.1. Whether or
not we decide to rethink date handling, I think this is an improvement
over what was there.
Please test again and check that printing is working okay on Prod.
If something goes wrong, please don't waste a lot of time on it. Just
let me know and I'll check it out.
Please hold off the testing for a bit.
Looking at this further, I ran into a problem with the new date popups that affects attempts to limit by date. I'll check with Bob on it.
I think the dates are working now. I was doing something in the old date data entry that was incompatible with the popups. It's now fixed.
Bonnie and I just ran several jobs using date ranges to limit the results and it seemed to work well. I'm considering this verified on DEV. Thanks!
Marking this resolved as fixed, ready for deployment to QA.
Verified on QA.
Bonnie hasn't needed to print anything yet, so I'm keeping this open a little longer.
Bonnie confirmed this is working on prod, so I'm closing this issue.
Elapsed: 0:00:00.000653