[
http://mifosforge.jira.com/browse/MIFOS-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
keithwoodlock reassigned MIFOS-2952:
------------------------------------
Assignee: keithwoodlock (was: Kay Chau)
> MFI Joining date is account creation date, not the real joining date for the
> center/group/client
> ------------------------------------------------------------------------------------------------
>
> Key: MIFOS-2952
> URL: http://mifosforge.jira.com/browse/MIFOS-2952
> Project: mifos
> Issue Type: Improvement
> Components: Clients
> Affects Versions: Release 1.5.0.1
> Reporter: Ryan Whitney
> Assignee: keithwoodlock
> Fix For: Unscheduled
>
>
> Discussion came up on developer list, decided to just file the bug
> "All,
> Entry of the record into Mifos does not necessarily match the joining date
> for the client (so the name is misleading). Seems to me we should track in
> the database the date/timestamp the record was entered and then have an
> editable field for the joining date."
> This issue comes up a LOT from MFI's, especially as they are entering in
> already existing clients into Mifos.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://mifosforge.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Mifos-issues mailing list
Mifos-issues@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mifos-issues
