[
http://mifosforge.jira.com/browse/MIFOS-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukasz Chudy updated MIFOS-4257:
--------------------------------
Status: Ready for Showcase (was: Ready for Testing / Resolved)
Verified on 07.02.2011
Bug has been fixed properly.
Commit Identifier: 062c3eb41fda5ffb946b2d2d44088e615d16b920
Build Number: hudson-head-f-release-34
> Client meeting information not persisted
> ----------------------------------------
>
> Key: MIFOS-4257
> URL: http://mifosforge.jira.com/browse/MIFOS-4257
> Project: mifos
> Issue Type: Bug
> Components: Clients
> Affects Versions: Elsie F
> Environment: Master branch
> Reporter: Deepak Paramasivam
> Assignee: Lukasz Chudy
> Priority: Critical
> Fix For: Elsie F - Iteration 10, Elsie F
>
>
> In cerate new client flow once the client information is submitted, the
> meeting schedule information get reset to following values irrespective of
> whatever value we enter.
> If month was chosen, the reset values are
> Location of meeting: meetingPlace
> Meeting: Recur on day 1 of every 1 month(s)
> If week was chosen, the reset values are
> Location of meeting: meetingPlace
> Meeting: Meeting: Recur every 1 Week(s) on Monday
--
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
------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
