[
http://mifosforge.jira.com/browse/MIFOS-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kay Chau updated MIFOS-2774:
----------------------------
Assignee: mifosdeveloperqueue
Fix Version/s: Gazelle Backlog
been there for awhile
> No change history entry recorded when an inactive savings account is
> re-activated due to a deposit
> --------------------------------------------------------------------------------------------------
>
> Key: MIFOS-2774
> URL: http://mifosforge.jira.com/browse/MIFOS-2774
> Project: mifos
> Issue Type: Bug
> Components: Savings Account
> Affects Versions: Release 1.4
> Reporter: johnwoodlock
> Assignee: mifosdeveloperqueue
> Fix For: Gazelle Backlog
>
>
> When an inactive savings account gets a deposit it gets reactivated.
> However, a change history record isn't created.
> This happens regardless of whether collection sheet or the savings accounts
> payments page is used.
> Initial impact analysis tech info.
> There are two methods which handle savings deposits... both in SavingsBO
> 1. makePayment(final PaymentData paymentData) by way of
> AccountBO.applyPayment(final PaymentData paymentData)
> 2. deposit(final AccountPaymentEntity payment, final CustomerBO
> payingCustomer)
--
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
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
