[
http://mifosforge.jira.com/browse/MIFOS-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
keithwoodlock resolved MIFOS-3117.
----------------------------------
Assignee: mifosqa (was: keithwoodlock)
Resolution: Fixed
Fix Version/s: Release E - Iteration 1
Jeff,
I can see how this is confusing and it is but this is 'expected behaviour'
based on requirements around meetings -
http://www.mifos.org/knowledge/functional-specifications/mfi-information-setup/meetings
the important bit being 'In Mifos 1.5.0 and beyond, when changing a center
meeting date in an installment "period", the change will always be applied in
the next installment "period", where a period is the frequency of your meeting
schedule and the repayment falls in.'
so this is why you are still seeing the first expected payment happening on
'old meeting day', because it fell within one installment period and as such is
not changed...
you will see that the client does now inherit the meeting of the group its
being assigned to and all 'future schedules' meet with the groups meeting
details and not the previous meeting details of the client.
> 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: mifosqa
> 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
