[
http://mifosforge.jira.com/browse/MIFOS-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
johnwoodlock resolved MIFOS-2956.
---------------------------------
Assignee: johnwoodlock (was: keithwoodlock)
Resolution: Fixed
Story Points: 0
Scheduled For: Release
Fix Version/s: Shamim D
JohnW Fixed in Revision: 4049cfcd34c2f88746698fb9ca721ff5c6aef645
KeithW additional tests added in Revision:
ed8945669713c1ec2500a5dc3af05cb10d7338d3
> RegenerateSchedule batch job ignores closed clients
> ----------------------------------------------------
>
> Key: MIFOS-2956
> URL: http://mifosforge.jira.com/browse/MIFOS-2956
> Project: mifos
> Issue Type: Bug
> Components: Batch jobs
> Affects Versions: Release 1.5
> Reporter: jbrewster
> Assignee: johnwoodlock
> Priority: Major
> Fix For: Shamim D
>
>
> When a client is closed/blacklisted and is part of a center that has its
> meeting day moved, the RegenerateMeeting batch job ignores the closed client.
> The fallout from that is the closed client stays with the previous meeting
> ID, which causes the batch job to fail to delete the old meeting since one or
> more clients still have that meeting ID.
> As Adam noted, the workaround was: "We manually changed the meeting ids for
> customer meetings for the two closed/blacklisted customers to the meeting ids
> in customer_meeting.UPDATED_MEETING_ID."
> This issue was identified while troubleshooting SECDEP customer issue where
> center was not being updated with new schedules - (see MIFOSADMIN-31)
--
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
------------------------------------------------------------------------------
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
