[
http://mifosforge.jira.com/browse/MIFOS-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jbrewster updated MIFOS-4257:
-----------------------------
Affects Version/s: Elsie F
Was able to reproduce, see client 0032-000000191 on
http://ci.mifos.org:8085/mifos. Attaching screenshots and assigning to the
developer queue.
> 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: jbrewster
> Priority: Critical
> Fix For: 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
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
