[ 
http://mifosforge.jira.com/browse/MIFOS-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58457#action_58457
 ] 

keithwoodlock commented on MIFOS-3117:
--------------------------------------

Jeff, the reason it is skipping those dates is:

currently the algorithm finds the next installment to update (based on interval 
period from today), so in your example, the first meeting schedule remains 
unchanged as it falls within one installment period, however the date to start 
generating new schedules is calculated of the 'next installment' which in this 
case is 2-3 weeks in the future and because of the holidays/moratoria. as a 
result its misses out on 'valid' dates for the new meeting schedule.

What should be done is the date of the 'last installment' before 'future 
installments start' should be used to determine when to start generating future 
schedules from.

> Individual client that is added to a group not picking up new group's meeting 
> schedule
> --------------------------------------------------------------------------------------
>
>                 Key: MIFOS-3117
>                 URL: http://mifosforge.jira.com/browse/MIFOS-3117
>             Project: mifos
>          Issue Type: Bug
>          Components: Clients
>    Affects Versions: Shamim D
>            Reporter: jbrewster
>            Assignee: keithwoodlock
>            Priority: Major
>             Fix For: Shamim D, Release E - Iteration 1
>
>         Attachments: issue3117.zip, screenshot-1.jpg, screenshot-2.jpg
>
>
> Client created without Group membership, then added to a group with different 
> meeting day is not picking up the group's meeting day in the 
> customer_schedule action dates.
> Repro steps:
> 1. create new client "test client" that meets on Wednesdays.
> 2. add weekly client fee, first fee is due on 23 June.
> 3. Add group membership for client.  Select group "MyGroup1233266255641" 
> which meets every Thursday.
> 4. check new fee due - still says 23 June.  Stop/started tomcat to be sure no 
> batch job was required.  Still see next customer fee due on 23 June instead 
> of 24 June.
> 5.  Start to create a new loan and see the default disbursal date is 23 June, 
> which is incorrect since client meets on the 24th (Thursday)
> Expected result:  customer_schedule action dates moved from Wed to Thu for 
> this client.
> Actual Result:
> Action dates are still Wednesday.
> Will attach zipped db with the data used for this test.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues

Reply via email to