[ 
http://mifosforge.jira.com/browse/MIFOS-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=69246#comment-69246
 ] 

Lukasz Chudy commented on MIFOS-2033:
-------------------------------------

Issue still exists in Release 2.2
                
> Group Details Portfolio at Risk does not get updated along with the status 
> change of a loan account
> ---------------------------------------------------------------------------------------------------
>
>                 Key: MIFOS-2033
>                 URL: http://mifosforge.jira.com/browse/MIFOS-2033
>             Project: mifos
>          Issue Type: Bug
>          Components: Groups, Loan Account
>    Affects Versions: Release 1.1
>         Environment: Platform: All, OS: All
>            Reporter: arpita_a
>            Assignee: mifosdeveloperqueue
>             Fix For: Unscheduled
>
>
> Hi,
> Steps to repro:
> 1. Log into Mifos.
> 2. Find Group_16 (with weekly meeting schedules on tuesday). Click on "open 
> new 
> account:loan".
> 3. Select a loan product and create a loan account with this product.
> 4. Disburse the loan created.
> 5. Similarly, create one more loan account (using a different loan 
> product)for 
> the same client and disburse that loan too.
> 6. Thus, say the loan accounts are created with today's date i.e, 23.06.2008.
> 7. Now. log out and take the system date to 7.07.2008 and make the payment 
> due 
> on that date only for the first loan account.
> 8. On the Admin page, click on "View Lateness/Dormancy Definition" and set 
> the "Lateness Definition" for loan accounts as "1 day" .
> 9. Again log out, take the system date to 9.07.2008 and run the batch jobs 
> too 
> by putting the time at 0:00 hours.
> 10 Log in and check the 2nd loan account on which no payment was made.
> Expected: the status changes to "Active in bad Standing" and under 
> "Performance 
> History" on the Group page, POrtfolio At Risk should get updated to 0.5.
> Actual: the status of the loan account changes, but Portfolio at Risk doesn't 
> get updated.
> Plz note, PAR gets updated at a later point but at what point exactly is not 
> known. Ideally it should have got updated with the status change.
> Environment:
> Operating System / Arch / Version Windows XP / x86 / 5.1 
> Java Vendor / Version Sun Microsystems Inc. / 1.5.0_10 
> Database Vendor / Version MySQL / 5.0.45-community-nt 
> Database Driver / Version MySQL-AB JDBC Driver / mysql-connector-java-5.1.5 ( 
> Revision: ${svn.Revision} ) 
> Application Server Apache Tomcat/6.0.16 
> Mifos Database Version 199 
> Subversion Revision Number 13248 
> Thanks,
> Arpita

--
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 of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of 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-d2dcopy2
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues

Reply via email to