[jira] [Assigned] (FINERACT-67) undo last tranche not working
[ https://issues.apache.org/jira/browse/FINERACT-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-67: Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > undo last tranche not working > - > > Key: FINERACT-67 > URL: https://issues.apache.org/jira/browse/FINERACT-67 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: bharath c >Assignee: Shaik Nazeer Hussain > > not able to undo the last tranche when for a loan with multiple tranches > disbursed > steps to reproduce. > create a multi tranche loan ex(2 tranche loan) > define the EMI amount while disbursing the 2nd tranche. > then try to undo that tranche -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-67) undo last tranche not working
[ https://issues.apache.org/jira/browse/FINERACT-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-67: - Assignee: Markus Geiss (was: Shaik Nazeer Hussain) > undo last tranche not working > - > > Key: FINERACT-67 > URL: https://issues.apache.org/jira/browse/FINERACT-67 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: bharath c >Assignee: Markus Geiss > > not able to undo the last tranche when for a loan with multiple tranches > disbursed > steps to reproduce. > create a multi tranche loan ex(2 tranche loan) > define the EMI amount while disbursing the 2nd tranche. > then try to undo that tranche -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-67) undo last tranche not working
[ https://issues.apache.org/jira/browse/FINERACT-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-67. Assignee: Shaik Nazeer Hussain (was: Adi Raju) > undo last tranche not working > - > > Key: FINERACT-67 > URL: https://issues.apache.org/jira/browse/FINERACT-67 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: bharath c >Assignee: Shaik Nazeer Hussain > > not able to undo the last tranche when for a loan with multiple tranches > disbursed > steps to reproduce. > create a multi tranche loan ex(2 tranche loan) > define the EMI amount while disbursing the 2nd tranche. > then try to undo that tranche -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-59) Interest calculation for flat interest loans incorrect for "Same as repayment period"
[ https://issues.apache.org/jira/browse/FINERACT-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-59. Assignee: Shaik Nazeer Hussain (was: Markus Geiss) tested and working as expected > Interest calculation for flat interest loans incorrect for "Same as repayment > period" > - > > Key: FINERACT-59 > URL: https://issues.apache.org/jira/browse/FINERACT-59 > Project: Apache Fineract > Issue Type: Bug >Reporter: Sander van der Heijden >Assignee: Shaik Nazeer Hussain >Priority: Critical > > After the recent refactoring of the interest calculation code, the generation > of flat interest loan schedules is having unexpected behaviour when the 'Same > as Repayment period' calculation type is selected. > Scenario: > - 6 month flat loan of 10,000 > - Interest rate of 20% annual > - Disbursement date: 01-03-2016 > - First repayment date: 09-03-2016 > Expected result: > - Total interest of 10,000 * (20%/12)*6 terms = 1000 > Current result: > - Total interest calculated over 6 months + 8 days (the extra 8 at the start > of the loan). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-59) Interest calculation for flat interest loans incorrect for "Same as repayment period"
[ https://issues.apache.org/jira/browse/FINERACT-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-59. -- Resolution: Fixed > Interest calculation for flat interest loans incorrect for "Same as repayment > period" > - > > Key: FINERACT-59 > URL: https://issues.apache.org/jira/browse/FINERACT-59 > Project: Apache Fineract > Issue Type: Bug >Reporter: Sander van der Heijden >Assignee: Markus Geiss >Priority: Critical > > After the recent refactoring of the interest calculation code, the generation > of flat interest loan schedules is having unexpected behaviour when the 'Same > as Repayment period' calculation type is selected. > Scenario: > - 6 month flat loan of 10,000 > - Interest rate of 20% annual > - Disbursement date: 01-03-2016 > - First repayment date: 09-03-2016 > Expected result: > - Total interest of 10,000 * (20%/12)*6 terms = 1000 > Current result: > - Total interest calculated over 6 months + 8 days (the extra 8 at the start > of the loan). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-62) Adding configuration for Collecting disbursement charge from the fund source of the payment type
[ https://issues.apache.org/jira/browse/FINERACT-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-62. > Adding configuration for Collecting disbursement charge from the fund source > of the payment type > > > Key: FINERACT-62 > URL: https://issues.apache.org/jira/browse/FINERACT-62 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Loan >Reporter: venkat Ganesh >Assignee: Markus Geiss >Priority: Minor > Attachments: After.png, Before.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-68) validation for center meeting rescheduling(Should not allow to reschedule FRP of loans under that center
[ https://issues.apache.org/jira/browse/FINERACT-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-68. Assignee: Shaik Nazeer Hussain (was: Adi Raju) > validation for center meeting rescheduling(Should not allow to reschedule FRP > of loans under that center > > > Key: FINERACT-68 > URL: https://issues.apache.org/jira/browse/FINERACT-68 > Project: Apache Fineract > Issue Type: Improvement >Reporter: bharath c >Assignee: Shaik Nazeer Hussain > > rescheduling of first repayment date should not be allowed from center > rescheduling feature -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-144) Performance improvement for accrual job
[ https://issues.apache.org/jira/browse/FINERACT-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-144. --- Resolution: Fixed Assignee: subramanyasn (was: Markus Geiss) Resolved with https://github.com/apache/incubator-fineract/pull/66 > Performance improvement for accrual job > > > Key: FINERACT-144 > URL: https://issues.apache.org/jira/browse/FINERACT-144 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges >Reporter: Sachin Kulkarni >Assignee: subramanyasn > > For each loan picked up by the accrual job it tries to fetch the Loan > Charges. The query used to fetch the loan charges has a sub query which does > not have loan id in the where clause this is making query performance issue. > Adding loanId in this loan charge query improves the performance of accrual > batch job. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-148) The sum of dividend to be posted does not match with total Dividend Amount
[ https://issues.apache.org/jira/browse/FINERACT-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268064#comment-15268064 ] Shaik Nazeer Hussain commented on FINERACT-148: --- Robert can you reproduce this scenario on demo server and share the product details to us. > The sum of dividend to be posted does not match with total Dividend Amount > -- > > Key: FINERACT-148 > URL: https://issues.apache.org/jira/browse/FINERACT-148 > Project: Apache Fineract > Issue Type: Bug >Reporter: Ippez Roberts >Assignee: Markus Geiss > Attachments: Dividend totals.png > > > Create a share product. > Create share accounts with varying number of shares > Initiate a dividend with a certain dividend amount > Click on this initiated dividend > The total amount allocated does not match with the dividend amount -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (FINERACT-148) The sum of dividend to be posted does not match with total Dividend Amount
[ https://issues.apache.org/jira/browse/FINERACT-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268064#comment-15268064 ] Shaik Nazeer Hussain edited comment on FINERACT-148 at 5/3/16 4:19 AM: --- Robert can you reproduce this scenario on demo server and share the product details to us. We failed to reproduce this on staging server. Please have a look at https://staging.openmf.org/#/dividends/2/ was (Author: nazeer1100126): Robert can you reproduce this scenario on demo server and share the product details to us. > The sum of dividend to be posted does not match with total Dividend Amount > -- > > Key: FINERACT-148 > URL: https://issues.apache.org/jira/browse/FINERACT-148 > Project: Apache Fineract > Issue Type: Bug >Reporter: Ippez Roberts >Assignee: Markus Geiss > Attachments: Dividend totals.png > > > Create a share product. > Create share accounts with varying number of shares > Initiate a dividend with a certain dividend amount > Click on this initiated dividend > The total amount allocated does not match with the dividend amount -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-148) The sum of dividend to be posted does not match with total Dividend Amount
[ https://issues.apache.org/jira/browse/FINERACT-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268235#comment-15268235 ] Shaik Nazeer Hussain commented on FINERACT-148: --- Yes I agree there is rounding off issue with +-1 and will work on that. But in your example the difference is 10,000. That's what surprises me. Can you create the issue you have mentioned with 10,000 difference on demo server > The sum of dividend to be posted does not match with total Dividend Amount > -- > > Key: FINERACT-148 > URL: https://issues.apache.org/jira/browse/FINERACT-148 > Project: Apache Fineract > Issue Type: Bug >Reporter: Ippez Roberts >Assignee: Markus Geiss > Attachments: Dividend totals.png > > > Create a share product. > Create share accounts with varying number of shares > Initiate a dividend with a certain dividend amount > Click on this initiated dividend > The total amount allocated does not match with the dividend amount -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FINERACT-157) Query share accounts returns Internal server error
[
https://issues.apache.org/jira/browse/FINERACT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaik Nazeer Hussain reassigned FINERACT-157:
-
Assignee: Shaik Nazeer Hussain (was: Markus Geiss)
> Query share accounts returns Internal server error
> --
>
> Key: FINERACT-157
> URL: https://issues.apache.org/jira/browse/FINERACT-157
> Project: Apache Fineract
> Issue Type: Bug
> Components: Shares
>Reporter: Terence Denzil Monteiro
>Assignee: Shaik Nazeer Hussain
>
> When making a GET request with URL /fineract-provider/api/v1/accounts/share,
> a list of share accounts should be returned as in the API docs
> https://demo.openmf.org/api-docs/apiLive.htm#shareaccount_list. Instead the
> platform responds with:
> {
> "timestamp": 1463490341729,
> "status": 500,
> "error": "Internal Server Error",
> "exception": "java.lang.NullPointerException",
> "message": null
> }
> This API should return a list of shares, which can be limited by paging and
> truncation of records if response size needs to be limited, but it should
> send back a sane response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (FINERACT-157) Query share accounts returns Internal server error
[
https://issues.apache.org/jira/browse/FINERACT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaik Nazeer Hussain resolved FINERACT-157.
---
Resolution: Fixed
Assignee: subramanyasn (was: Shaik Nazeer Hussain)
As part of pull request 119, it is fixed.
> Query share accounts returns Internal server error
> --
>
> Key: FINERACT-157
> URL: https://issues.apache.org/jira/browse/FINERACT-157
> Project: Apache Fineract
> Issue Type: Bug
> Components: Shares
>Reporter: Terence Denzil Monteiro
>Assignee: subramanyasn
>
> When making a GET request with URL /fineract-provider/api/v1/accounts/share,
> a list of share accounts should be returned as in the API docs
> https://demo.openmf.org/api-docs/apiLive.htm#shareaccount_list. Instead the
> platform responds with:
> {
> "timestamp": 1463490341729,
> "status": 500,
> "error": "Internal Server Error",
> "exception": "java.lang.NullPointerException",
> "message": null
> }
> This API should return a list of shares, which can be limited by paging and
> truncation of records if response size needs to be limited, but it should
> send back a sane response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (FINERACT-145) Some of the scheduler jobs in demo version is not getting executed as scheduled
[ https://issues.apache.org/jira/browse/FINERACT-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-145: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > Some of the scheduler jobs in demo version is not getting executed as > scheduled > --- > > Key: FINERACT-145 > URL: https://issues.apache.org/jira/browse/FINERACT-145 > Project: Apache Fineract > Issue Type: Bug > Components: System >Reporter: subramanyasn >Assignee: Shaik Nazeer Hussain >Priority: Critical > Attachments: Mifos X Client 2016-04-29 03-43-10.png > > > In demo version some of the scheduler jobs are not getting executed as it is > scheduled. Some of them will not get executed as it has to get executed on a > daily basis. After restarting the server of the demo version it executes, but > the same issue exists after few days again. > Please find the screen shot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FINERACT-181) Not able to apply additional shares displays internal server error
[ https://issues.apache.org/jira/browse/FINERACT-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-181: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > Not able to apply additional shares displays internal server error > -- > > Key: FINERACT-181 > URL: https://issues.apache.org/jira/browse/FINERACT-181 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Reporter: subramanyasn >Assignee: Shaik Nazeer Hussain >Priority: Critical > Attachments: Shares and disvidents.png > > > 1. Create a basic share product with following datasets. > Total Shares:100 > Total Shares to be Issued:50 > Nominal/Unit Price:0.5 > Total Shares Capital Value:25 > Shares per Client:10 ( Min: , Max : ) > 2. Create an active savings product for a client. > 3. Submit new share application for a client on 01 June 2016 approve and > activate on same date. while creating select the above savings product. > 4.Click on additional shares and apply for 10 shares on 02 June 2016. > > Not able to save the page, displays internal server error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-181) Not able to apply additional shares displays internal server error
[ https://issues.apache.org/jira/browse/FINERACT-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-181. --- Resolution: Fixed Assignee: subramanyasn (was: Shaik Nazeer Hussain) > Not able to apply additional shares displays internal server error > -- > > Key: FINERACT-181 > URL: https://issues.apache.org/jira/browse/FINERACT-181 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Reporter: subramanyasn >Assignee: subramanyasn >Priority: Critical > Attachments: Shares and disvidents.png > > > 1. Create a basic share product with following datasets. > Total Shares:100 > Total Shares to be Issued:50 > Nominal/Unit Price:0.5 > Total Shares Capital Value:25 > Shares per Client:10 ( Min: , Max : ) > 2. Create an active savings product for a client. > 3. Submit new share application for a client on 01 June 2016 approve and > activate on same date. while creating select the above savings product. > 4.Click on additional shares and apply for 10 shares on 02 June 2016. > > Not able to save the page, displays internal server error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FINERACT-183) Not able to save Edit Fixed deposit product page displays Internal server error
[ https://issues.apache.org/jira/browse/FINERACT-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-183: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > Not able to save Edit Fixed deposit product page displays Internal server > error > --- > > Key: FINERACT-183 > URL: https://issues.apache.org/jira/browse/FINERACT-183 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Reporter: subramanyasn >Assignee: Shaik Nazeer Hussain >Priority: Critical > > 1. Create simple fixed deposit product, > 2. Click on edit Fixed deposit product, do not modify any field and click on > submit button. > > Not able to save the page displays internal server error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-183) Not able to save Edit Fixed deposit product page displays Internal server error
[ https://issues.apache.org/jira/browse/FINERACT-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-183. --- Resolution: Fixed Assignee: subramanyasn (was: Shaik Nazeer Hussain) Resolved with PR 153 > Not able to save Edit Fixed deposit product page displays Internal server > error > --- > > Key: FINERACT-183 > URL: https://issues.apache.org/jira/browse/FINERACT-183 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Reporter: subramanyasn >Assignee: subramanyasn >Priority: Critical > > 1. Create simple fixed deposit product, > 2. Click on edit Fixed deposit product, do not modify any field and click on > submit button. > > Not able to save the page displays internal server error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-162) Savings: Show "Interest Earnings/Overdraft Interest not yet posted" in Summary
[ https://issues.apache.org/jira/browse/FINERACT-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-162. - Resolution: Fixed Tested by Subramanya and working as expected > Savings: Show "Interest Earnings/Overdraft Interest not yet posted" in Summary > -- > > Key: FINERACT-162 > URL: https://issues.apache.org/jira/browse/FINERACT-162 > Project: Apache Fineract > Issue Type: New Feature > Components: Savings >Reporter: Avinash Kumar >Assignee: subramanyasn > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-145) Some of the scheduler jobs in demo version is not getting executed as scheduled
[ https://issues.apache.org/jira/browse/FINERACT-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-145. - Resolution: Fixed Tested by Subranya and working as expected > Some of the scheduler jobs in demo version is not getting executed as > scheduled > --- > > Key: FINERACT-145 > URL: https://issues.apache.org/jira/browse/FINERACT-145 > Project: Apache Fineract > Issue Type: Bug > Components: System >Reporter: subramanyasn >Assignee: Shaik Nazeer Hussain >Priority: Critical > Attachments: Mifos X Client 2016-04-29 03-43-10.png > > > In demo version some of the scheduler jobs are not getting executed as it is > scheduled. Some of them will not get executed as it has to get executed on a > daily basis. After restarting the server of the demo version it executes, but > the same issue exists after few days again. > Please find the screen shot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-191) After first tranche disbursement if the loan is foreclosed the repayment schedule generated is not proper
[ https://issues.apache.org/jira/browse/FINERACT-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-191. --- Resolution: Fixed Assignee: subramanyasn (was: Shaik Nazeer Hussain) Fixed with PR 157 > After first tranche disbursement if the loan is foreclosed the repayment > schedule generated is not proper > - > > Key: FINERACT-191 > URL: https://issues.apache.org/jira/browse/FINERACT-191 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: subramanyasn >Assignee: subramanyasn > Attachments: Foreclosure14.png > > > 1. Create a loan product with principal 1, ROI 12% pa, repaid every 1 > month, loan term 12 months, Tranche count as 2. > 2. Submit new loan application for a client on 01 January 2016, first tranche > of 5000 on 01 January 2016 and amount as 5000, 2nd tranche on 01 March 2016. > 3. Approve and disburse 1st tranche on 01 January 2016. > 4. Foreclose the loan on 15 January 2016. > >Click on repayment schedule in which principal due for 15 January is > >displaying as 1 and balance of loan as -5000. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FINERACT-191) After first tranche disbursement if the loan is foreclosed the repayment schedule generated is not proper
[ https://issues.apache.org/jira/browse/FINERACT-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-191: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > After first tranche disbursement if the loan is foreclosed the repayment > schedule generated is not proper > - > > Key: FINERACT-191 > URL: https://issues.apache.org/jira/browse/FINERACT-191 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: subramanyasn >Assignee: Shaik Nazeer Hussain > Attachments: Foreclosure14.png > > > 1. Create a loan product with principal 1, ROI 12% pa, repaid every 1 > month, loan term 12 months, Tranche count as 2. > 2. Submit new loan application for a client on 01 January 2016, first tranche > of 5000 on 01 January 2016 and amount as 5000, 2nd tranche on 01 March 2016. > 3. Approve and disburse 1st tranche on 01 January 2016. > 4. Foreclose the loan on 15 January 2016. > >Click on repayment schedule in which principal due for 15 January is > >displaying as 1 and balance of loan as -5000. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FINERACT-182) Loan is not going to closed state after foreclosing if the specified due date charge is applied and waived
[ https://issues.apache.org/jira/browse/FINERACT-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-182: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > Loan is not going to closed state after foreclosing if the specified due date > charge is applied and waived > -- > > Key: FINERACT-182 > URL: https://issues.apache.org/jira/browse/FINERACT-182 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: subramanyasn >Assignee: Shaik Nazeer Hussain > Attachments: Foreclosure11.png > > > 1. Create a loan product with daily interest calculation, principal 1, > ROI 12% pa, repaid every 1 month. > 2. Create a client and submit new loan application for a client on 01 June > 2016. Apply specified due date charge of 100 flat. on 15 June 2016. approve > and disburse the loan. > 3. Waive charge on 15 June 2016. > 4.Fore close the loan on 20 June 2016. > > After foreclosure of loan the loan is not getting closed, instead charge is > > displaying as -ve amount, in summary page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-182) Loan is not going to closed state after foreclosing if the specified due date charge is applied and waived
[ https://issues.apache.org/jira/browse/FINERACT-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-182. --- Resolution: Fixed Assignee: subramanyasn (was: Shaik Nazeer Hussain) Fixed with PR 158 > Loan is not going to closed state after foreclosing if the specified due date > charge is applied and waived > -- > > Key: FINERACT-182 > URL: https://issues.apache.org/jira/browse/FINERACT-182 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: subramanyasn >Assignee: subramanyasn > Attachments: Foreclosure11.png > > > 1. Create a loan product with daily interest calculation, principal 1, > ROI 12% pa, repaid every 1 month. > 2. Create a client and submit new loan application for a client on 01 June > 2016. Apply specified due date charge of 100 flat. on 15 June 2016. approve > and disburse the loan. > 3. Waive charge on 15 June 2016. > 4.Fore close the loan on 20 June 2016. > > After foreclosure of loan the loan is not getting closed, instead charge is > > displaying as -ve amount, in summary page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-49) Waived charges and zero installment charges amounts not excluded from total charges amount on reschedule loan preview
[ https://issues.apache.org/jira/browse/FINERACT-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398887#comment-15398887 ] Shaik Nazeer Hussain commented on FINERACT-49: -- @ Emmanuel can you describe little more on this. > Waived charges and zero installment charges amounts not excluded from total > charges amount on reschedule loan preview > - > > Key: FINERACT-49 > URL: https://issues.apache.org/jira/browse/FINERACT-49 > Project: Apache Fineract > Issue Type: Bug >Reporter: Emmanuel Nnaa >Assignee: Markus Geiss >Priority: Minor > > Waived charges and zero installment (installment with zero principle and > interest) charges amounts not excluded from total charges amount on > reschedule loan preview. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-55) Standing instruction not disabled at loan/savings account closure
[ https://issues.apache.org/jira/browse/FINERACT-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401551#comment-15401551 ] Shaik Nazeer Hussain commented on FINERACT-55: -- For any reason, if the loan/savings becomes active then user has to enable standing instructions manually. > Standing instruction not disabled at loan/savings account closure > - > > Key: FINERACT-55 > URL: https://issues.apache.org/jira/browse/FINERACT-55 > Project: Apache Fineract > Issue Type: Bug >Reporter: Emmanuel Nnaa >Assignee: Markus Geiss >Priority: Minor > > All standing instructions linked to a savings/loan should be disabled when > the status of the entity changes to 600. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-55) Standing instruction not disabled at loan/savings account closure
[ https://issues.apache.org/jira/browse/FINERACT-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-55. Resolution: Fixed Assignee: subramanyasn (was: Markus Geiss) Verified by Subramanya. Working as expected > Standing instruction not disabled at loan/savings account closure > - > > Key: FINERACT-55 > URL: https://issues.apache.org/jira/browse/FINERACT-55 > Project: Apache Fineract > Issue Type: Bug >Reporter: Emmanuel Nnaa >Assignee: subramanyasn >Priority: Minor > > All standing instructions linked to a savings/loan should be disabled when > the status of the entity changes to 600. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-57) Set closure properties of reactivated closed client entity to null
[ https://issues.apache.org/jira/browse/FINERACT-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-57. Resolution: Fixed Assignee: subramanyasn (was: Markus Geiss) Verified by Subramanya. Working as expected > Set closure properties of reactivated closed client entity to null > -- > > Key: FINERACT-57 > URL: https://issues.apache.org/jira/browse/FINERACT-57 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Emmanuel Nnaa >Assignee: subramanyasn > > If a closed client is reactivated, the following properties should be set to > null: > 1. closureDate > 2. closureReason > 3. closedBy -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-70) Rename deleted standing instruction by appending "_deleted_" string and the id
[
https://issues.apache.org/jira/browse/FINERACT-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaik Nazeer Hussain closed FINERACT-70.
Resolution: Fixed
Assignee: subramanyasn (was: Markus Geiss)
Verified by Subramanya. Working as expected
> Rename deleted standing instruction by appending "_deleted_" string and the id
> --
>
> Key: FINERACT-70
> URL: https://issues.apache.org/jira/browse/FINERACT-70
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: Emmanuel Nnaa
>Assignee: subramanyasn
>Priority: Minor
> Attachments: Deleted stadning insructions.png
>
>
> Rename deleted standing instruction by appending "_deleted" string and the id.
> Add the following method to "AccountTransferStandingInstruction" class:
> {code}
> public void delete() {
> this.status = StandingInstructionStatus.DELETED.getValue();
> this.name = this.name + "_deleted" + this.getId();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (FINERACT-44) Cannot delete an inactive charge associated with a product (loan/savings)
[
https://issues.apache.org/jira/browse/FINERACT-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaik Nazeer Hussain closed FINERACT-44.
Resolution: Fixed
Assignee: subramanyasn (was: Markus Geiss)
Verified by Subramanya. Working as expected
> Cannot delete an inactive charge associated with a product (loan/savings)
> -
>
> Key: FINERACT-44
> URL: https://issues.apache.org/jira/browse/FINERACT-44
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Emmanuel Nnaa
>Assignee: subramanyasn
>Priority: Minor
>
> The SQL statement in the methods (isAnyLoansAssociateWithThisCharge and
> isAnySavingsAssociateWithThisCharge) that check if a charge is attached to a
> product (loan or savings) does not include the "and is_active = 1" criterion.
> *Solution*
> {code}
> final String sql = "select if((exists (select 1 from m_loan_charge lc where
> lc.charge_id = ? and lc.is_active = 1)) = 1, 'true', 'false')";
> final String sql = "select if((exists (select 1 from m_savings_account_charge
> sc where sc.charge_id = ? and sc.is_active = 1)) = 1, 'true', 'false')";
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (FINERACT-47) Expired user password cannot be updated by the same user
[
https://issues.apache.org/jira/browse/FINERACT-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaik Nazeer Hussain resolved FINERACT-47.
--
Resolution: Fixed
Assignee: subramanyasn (was: Markus Geiss)
> Expired user password cannot be updated by the same user
>
>
> Key: FINERACT-47
> URL: https://issues.apache.org/jira/browse/FINERACT-47
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Emmanuel Nnaa
>Assignee: subramanyasn
>Priority: Minor
>
> The "SynchronousCommandProcessingService.publishEvent" method calls the
> method "PlatformSecurityContext.authenticatedUser()" that does not exempt the
> update of a user's data from the password expiration check.
> *Change the following line*
> {code}
> final AppUser appUser = this.context.authenticatedUser();
> {code}
> *To*
> {code}
> final AppUser appUser =
> this.context.authenticatedUser(CommandWrapper.wrap(actionName, entityName,
> null, null));
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (FINERACT-47) Expired user password cannot be updated by the same user
[
https://issues.apache.org/jira/browse/FINERACT-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaik Nazeer Hussain closed FINERACT-47.
Verified by Subramanya. Working as expected
> Expired user password cannot be updated by the same user
>
>
> Key: FINERACT-47
> URL: https://issues.apache.org/jira/browse/FINERACT-47
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Emmanuel Nnaa
>Assignee: subramanyasn
>Priority: Minor
>
> The "SynchronousCommandProcessingService.publishEvent" method calls the
> method "PlatformSecurityContext.authenticatedUser()" that does not exempt the
> update of a user's data from the password expiration check.
> *Change the following line*
> {code}
> final AppUser appUser = this.context.authenticatedUser();
> {code}
> *To*
> {code}
> final AppUser appUser =
> this.context.authenticatedUser(CommandWrapper.wrap(actionName, entityName,
> null, null));
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (FINERACT-50) Add "mandatory" property to code value entity
[ https://issues.apache.org/jira/browse/FINERACT-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-50. Resolution: Fixed Assignee: subramanyasn (was: Markus Geiss) Verified by Subramanya. Working as expected > Add "mandatory" property to code value entity > - > > Key: FINERACT-50 > URL: https://issues.apache.org/jira/browse/FINERACT-50 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Emmanuel Nnaa >Assignee: subramanyasn > > Adding the "mandatory" property makes it possible to set a code value as > mandatory or non-mandatory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-190) Client accounts API shows multiple entries for same share account
[ https://issues.apache.org/jira/browse/FINERACT-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-190. - Resolution: Fixed Assignee: subramanyasn (was: Terence Denzil Monteiro) Verified by Subramanya. Working as expected > Client accounts API shows multiple entries for same share account > - > > Key: FINERACT-190 > URL: https://issues.apache.org/jira/browse/FINERACT-190 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Reporter: Terence Denzil Monteiro >Assignee: subramanyasn > Attachments: dup-accts.jpg > > > Steps to reproduce: > For a given client, > Create a share account > Approve the account > Activate the account > Using a REST client, reject the account > Now we have an account for which activated_userid and rejected_userid are > both set. Now try the API > /clients/:clientId/accounts > This yields multiple records for the share account we created. This is an > issue with the SQL query for fetching the share account list for a client. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-206) When deleting a group with with a user who has roles. It throws com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Cannot delete or update a par
[ https://issues.apache.org/jira/browse/FINERACT-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-206. - Resolution: Fixed Assignee: subramanyasn (was: Markus Geiss) Verified by Subramanya. Working as expected > When deleting a group with with a user who has roles. It throws > com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: > Cannot delete or update a parent row: a foreign key constraint fails > - > > Key: FINERACT-206 > URL: https://issues.apache.org/jira/browse/FINERACT-206 > Project: Apache Fineract > Issue Type: Bug >Reporter: andrewDzakpasu >Assignee: subramanyasn > > To replicate this issue. > 1. Create a group > 2. Add a client to the group > 3. Give the client a group role ex. chairman > 3. Remove the client from the Group > 4. Try deleting the group > You will get > com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException > because in the m_group_roles the group id exist there as a foreign key -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-45) The "getRejectedByUser" method in the "LoanRescheduleRequest" entity class returns the wrong value.
[
https://issues.apache.org/jira/browse/FINERACT-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaik Nazeer Hussain closed FINERACT-45.
Resolution: Fixed
Assignee: subramanyasn (was: Markus Geiss)
Verified and working as expected
> The "getRejectedByUser" method in the "LoanRescheduleRequest" entity class
> returns the wrong value.
> ---
>
> Key: FINERACT-45
> URL: https://issues.apache.org/jira/browse/FINERACT-45
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Emmanuel Nnaa
>Assignee: subramanyasn
>Priority: Minor
>
> The "getRejectedByUser" method in the "LoanRescheduleRequest" entity class
> returns the "approvedByUser" property instead of the "rejectedByUser"
> property as value.
> change the following method:
> {code}
> public AppUser getRejectedByUser() {
> return this.approvedByUser;
> }
> {code}
> to:
> {code}
> public AppUser getRejectedByUser() {
> return this.rejectedByUser;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (FINERACT-53) Make the "clientId" URL parameter optional for "loan details template" retrieval
[ https://issues.apache.org/jira/browse/FINERACT-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-53. Resolution: Fixed Assignee: subramanyasn (was: Markus Geiss) working as expected > Make the "clientId" URL parameter optional for "loan details template" > retrieval > > > Key: FINERACT-53 > URL: https://issues.apache.org/jira/browse/FINERACT-53 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Emmanuel Nnaa >Assignee: subramanyasn >Priority: Minor > > It should be possible to retrieve a loan details template without providing a > "clientId" URL parameter. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-65) Implement ability to schedule & e-mail reports
[ https://issues.apache.org/jira/browse/FINERACT-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-65. Resolution: Fixed Assignee: subramanyasn (was: Markus Geiss) > Implement ability to schedule & e-mail reports > -- > > Key: FINERACT-65 > URL: https://issues.apache.org/jira/browse/FINERACT-65 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Emmanuel Nnaa >Assignee: subramanyasn >Priority: Minor > > Some reports take a bit longer to run, therefore we should be able to allow > our users to schedule them overnight to be e-mailed. > The way this should work is: > - Add e-mailaddress to users and make it mandatory (possibly already in > MifosX) > - Allow users to configure schedule entries which consist of: > - One or multiple target users (e-mailaddresses) > - Set the preferred subject and content of the e-mail (Look at user generated > documents API in MifosX for replacing certain variables) > - Choose the run frequency of the report (daily, weekly, every x'th day of > the month etc, cron-like flexibility with a UI) > - Pick the preferred output format (PDF/XLS/CSV) > These reports should be picked up by a scheduled job overnight and then run > in serial to avoid performance hits and sent out to the users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-71) "AuditReadPlatformServiceImpl.retrieveEntries" returns duplicate results for users without the "ALL_FUNCTIONS" and "CHECKER_SUPER_USER" permissions.
[ https://issues.apache.org/jira/browse/FINERACT-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-71. Resolution: Fixed Assignee: subramanyasn (was: Markus Geiss) > "AuditReadPlatformServiceImpl.retrieveEntries" returns duplicate results for > users without the "ALL_FUNCTIONS" and "CHECKER_SUPER_USER" permissions. > > > Key: FINERACT-71 > URL: https://issues.apache.org/jira/browse/FINERACT-71 > Project: Apache Fineract > Issue Type: Bug >Reporter: Emmanuel Nnaa >Assignee: subramanyasn >Priority: Minor > > "AuditReadPlatformServiceImpl.retrieveEntries" returns duplicate results for > users without the "ALL_FUNCTIONS" and "CHECKER_SUPER_USER" permissions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-61) Incorrect penalty and fee charges amount inserted into the "m_loan_arrears_aging" table
[
https://issues.apache.org/jira/browse/FINERACT-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaik Nazeer Hussain closed FINERACT-61.
Resolution: Fixed
Assignee: subramanyasn (was: Markus Geiss)
Tested by Subramanya and working as expected.
> Incorrect penalty and fee charges amount inserted into the
> "m_loan_arrears_aging" table
> ---
>
> Key: FINERACT-61
> URL: https://issues.apache.org/jira/browse/FINERACT-61
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Emmanuel Nnaa
>Assignee: subramanyasn
>Priority: Minor
>
> The "waived charges amount" and "written-off charges amount" are not deducted
> from the charges amount when calculating the "penalty charges overdue" or
> "fee charges overdue".
> *Example:*
> The "fee charges overdue" query should be:
> {code}
> SUM(ifnull(mr.fee_charges_amount, 0) -
> ifnull(mr.fee_charges_writtenoff_derived, 0) - "
> + "ifnull(mr.fee_charges_waived_derived, 0) -
> ifnull(mr.fee_charges_completed_derived, 0))
> {code}
> and not:
> {code}
> SUM((ifnull(mr.fee_charges_amount,0) -
> ifnull(mr.fee_charges_completed_derived, 0)))
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (FINERACT-245) Introduce RAT checks
[ https://issues.apache.org/jira/browse/FINERACT-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-245: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > Introduce RAT checks > > > Key: FINERACT-245 > URL: https://issues.apache.org/jira/browse/FINERACT-245 > Project: Apache Fineract > Issue Type: Task >Reporter: Myrle Krantz >Assignee: Shaik Nazeer Hussain > > GIVEN a contributor or committer forks the fineract code base, and builds it > locally to fix bugs and add features, > WHEN an apache policy violating library dependency is accidentally introduced > to the source code, > THEN the build fails. > See https://github.com/apache/incubator-geode/blob/develop/gradle/rat.gradle > for an example of how to do this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-266) Copy license files while building war file
Shaik Nazeer Hussain created FINERACT-266: - Summary: Copy license files while building war file Key: FINERACT-266 URL: https://issues.apache.org/jira/browse/FINERACT-266 Project: Apache Fineract Issue Type: Task Reporter: Shaik Nazeer Hussain Assignee: Markus Geiss Copy license files while building war file -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FINERACT-266) Copy license files while building war file
[ https://issues.apache.org/jira/browse/FINERACT-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-266: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > Copy license files while building war file > -- > > Key: FINERACT-266 > URL: https://issues.apache.org/jira/browse/FINERACT-266 > Project: Apache Fineract > Issue Type: Task >Reporter: Shaik Nazeer Hussain >Assignee: Shaik Nazeer Hussain > > Copy license files while building war file -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-266) Handling License issues for both source and binary distributions
[ https://issues.apache.org/jira/browse/FINERACT-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-266: -- Summary: Handling License issues for both source and binary distributions (was: Copy license files while building war file) > Handling License issues for both source and binary distributions > > > Key: FINERACT-266 > URL: https://issues.apache.org/jira/browse/FINERACT-266 > Project: Apache Fineract > Issue Type: Task >Reporter: Shaik Nazeer Hussain >Assignee: Shaik Nazeer Hussain > > Copy license files while building war file -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-266) Handling License issues for both source and binary distributions
[ https://issues.apache.org/jira/browse/FINERACT-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-266. --- Resolution: Fixed > Handling License issues for both source and binary distributions > > > Key: FINERACT-266 > URL: https://issues.apache.org/jira/browse/FINERACT-266 > Project: Apache Fineract > Issue Type: Task >Reporter: Shaik Nazeer Hussain >Assignee: Shaik Nazeer Hussain > > Copy license files while building war file -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-245) Introduce RAT checks
[ https://issues.apache.org/jira/browse/FINERACT-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-245. --- Resolution: Fixed > Introduce RAT checks > > > Key: FINERACT-245 > URL: https://issues.apache.org/jira/browse/FINERACT-245 > Project: Apache Fineract > Issue Type: Task >Reporter: Myrle Krantz >Assignee: Shaik Nazeer Hussain > > GIVEN a contributor or committer forks the fineract code base, and builds it > locally to fix bugs and add features, > WHEN an apache policy violating library dependency is accidentally introduced > to the source code, > THEN the build fails. > See https://github.com/apache/incubator-geode/blob/develop/gradle/rat.gradle > for an example of how to do this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-288) Client's Image Uploaded Not Showing on UI in Amazon S3
[ https://issues.apache.org/jira/browse/FINERACT-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-288: -- Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > Client's Image Uploaded Not Showing on UI in Amazon S3 > -- > > Key: FINERACT-288 > URL: https://issues.apache.org/jira/browse/FINERACT-288 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain > > 1. Create a Client and activate him/her. > 2. On Client's page click on 'Upload Client Image' > 3. Select the Client's photo and click on upload. > In the database, (m_image and m_client), it is showing the image is uploaded > but it can not be seen on Client's page in UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-288) Client's Image Uploaded Not Showing on UI in Amazon S3
[ https://issues.apache.org/jira/browse/FINERACT-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-288. --- Resolution: Fixed Assignee: Markus Geiss (was: Shaik Nazeer Hussain) > Client's Image Uploaded Not Showing on UI in Amazon S3 > -- > > Key: FINERACT-288 > URL: https://issues.apache.org/jira/browse/FINERACT-288 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Reporter: Santosh Math >Assignee: Markus Geiss > > 1. Create a Client and activate him/her. > 2. On Client's page click on 'Upload Client Image' > 3. Select the Client's photo and click on upload. > In the database, (m_image and m_client), it is showing the image is uploaded > but it can not be seen on Client's page in UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-288) Client's Image Uploaded Not Showing on UI in Amazon S3
[ https://issues.apache.org/jira/browse/FINERACT-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734966#comment-15734966 ] Shaik Nazeer Hussain commented on FINERACT-288: --- [~edcable][~santoshmath] This issue exists from 2013. > Client's Image Uploaded Not Showing on UI in Amazon S3 > -- > > Key: FINERACT-288 > URL: https://issues.apache.org/jira/browse/FINERACT-288 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Reporter: Santosh Math >Assignee: Markus Geiss > > 1. Create a Client and activate him/her. > 2. On Client's page click on 'Upload Client Image' > 3. Select the Client's photo and click on upload. > In the database, (m_image and m_client), it is showing the image is uploaded > but it can not be seen on Client's page in UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-267) Foreclosure Issue: Loan with Installment fee status is overpaid
[ https://issues.apache.org/jira/browse/FINERACT-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-267. --- Resolution: Fixed Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > Foreclosure Issue: Loan with Installment fee status is overpaid > --- > > Key: FINERACT-267 > URL: https://issues.apache.org/jira/browse/FINERACT-267 > Project: Apache Fineract > Issue Type: Bug > Components: Charges, Loan > Environment: Ubuntu >Reporter: Ram Awale >Assignee: Shaik Nazeer Hussain > > Foreclosure for a loan which has a installment fee is changing status to over > payment instead of closed loan. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-267) Foreclosure Issue: Loan with Installment fee status is overpaid
[ https://issues.apache.org/jira/browse/FINERACT-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-267. - Santosh tested and working as expected > Foreclosure Issue: Loan with Installment fee status is overpaid > --- > > Key: FINERACT-267 > URL: https://issues.apache.org/jira/browse/FINERACT-267 > Project: Apache Fineract > Issue Type: Bug > Components: Charges, Loan > Environment: Ubuntu >Reporter: Ram Awale >Assignee: Shaik Nazeer Hussain > > Foreclosure for a loan which has a installment fee is changing status to over > payment instead of closed loan. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-260) Validation need to be added if the client charge is applied before client activation date
[ https://issues.apache.org/jira/browse/FINERACT-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-260. --- Resolution: Fixed Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > Validation need to be added if the client charge is applied before client > activation date > - > > Key: FINERACT-260 > URL: https://issues.apache.org/jira/browse/FINERACT-260 > Project: Apache Fineract > Issue Type: Bug >Reporter: Edward Cable >Assignee: Shaik Nazeer Hussain >Priority: Minor > Attachments: Screen Shot 2016-11-22 at 3.21.31 PM.png > > > Migrated over from MifosForge. > Original Description: > If the client activation date is on 01 June 2016 and the charge for a client > is getting applied before that date then validation need to be added, and > proper error message should get displayed > Steps to Reproduce > 1. Add a client charge, select a due date prior to client activation date. > 2. Submit and it successfully goes through. > Expected Behavior > 1. Upon submission of charge with a due date prior to activation date of the > client, a proper error message should be displayed stating that the the > charge due date is before the client activation date. > See https://demo3.openmf.org/#/viewclient/10 for an example. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-260) Validation need to be added if the client charge is applied before client activation date
[ https://issues.apache.org/jira/browse/FINERACT-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-260. - Santosh tested and working as expected > Validation need to be added if the client charge is applied before client > activation date > - > > Key: FINERACT-260 > URL: https://issues.apache.org/jira/browse/FINERACT-260 > Project: Apache Fineract > Issue Type: Bug >Reporter: Edward Cable >Assignee: Shaik Nazeer Hussain >Priority: Minor > Attachments: Screen Shot 2016-11-22 at 3.21.31 PM.png > > > Migrated over from MifosForge. > Original Description: > If the client activation date is on 01 June 2016 and the charge for a client > is getting applied before that date then validation need to be added, and > proper error message should get displayed > Steps to Reproduce > 1. Add a client charge, select a due date prior to client activation date. > 2. Submit and it successfully goes through. > Expected Behavior > 1. Upon submission of charge with a due date prior to activation date of the > client, a proper error message should be displayed stating that the the > charge due date is before the client activation date. > See https://demo3.openmf.org/#/viewclient/10 for an example. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-357) Address the review comments as part of 0.5.0-incubating release
Shaik Nazeer Hussain created FINERACT-357: - Summary: Address the review comments as part of 0.5.0-incubating release Key: FINERACT-357 URL: https://issues.apache.org/jira/browse/FINERACT-357 Project: Apache Fineract Issue Type: Task Components: User Management Reporter: Shaik Nazeer Hussain Assignee: Shaik Nazeer Hussain As part of 0.5.0-incubating release, we have got the following review comments which should be addressed for 0.6.0-incubating release. 1) Maven repo should be included in place of war file for the next release 2) Gradle should be integrated in the top level directory. Currently it is integrated with fineract-provider. (RAT issue) 3) Including License and License.md will confuse the people 4) The LICENSE maye be missing a license for jquery 5) Remove the list of software included in the binary release from the source release LICENSE file. It’s fine to have two different license files 6) The convenience binary file is missing LICENSE, NOTICE and DISCLAIMER in the top level, however the LICENSE and NOTICE file is inside the war and look correct -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-357) Address the review comments as part of 0.5.0-incubating release
[ https://issues.apache.org/jira/browse/FINERACT-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-357: -- Description: As part of 0.5.0-incubating release, we got the following review comments from IPMC members which should be addressed for 0.6.0-incubating release. 1) Maven repo should be included in place of war file for the next release 2) Gradle should be integrated in the top level directory. Currently it is integrated with fineract-provider. (RAT issue) 3) Including License and License.md will confuse the people 4) The LICENSE maye be missing a license for jquery 5) Remove the list of software included in the binary release from the source release LICENSE file. It’s fine to have two different license files 6) The convenience binary file is missing LICENSE, NOTICE and DISCLAIMER in the top level, however the LICENSE and NOTICE file is inside the war and look correct was: As part of 0.5.0-incubating release, we have got the following review comments which should be addressed for 0.6.0-incubating release. 1) Maven repo should be included in place of war file for the next release 2) Gradle should be integrated in the top level directory. Currently it is integrated with fineract-provider. (RAT issue) 3) Including License and License.md will confuse the people 4) The LICENSE maye be missing a license for jquery 5) Remove the list of software included in the binary release from the source release LICENSE file. It’s fine to have two different license files 6) The convenience binary file is missing LICENSE, NOTICE and DISCLAIMER in the top level, however the LICENSE and NOTICE file is inside the war and look correct > Address the review comments as part of 0.5.0-incubating release > --- > > Key: FINERACT-357 > URL: https://issues.apache.org/jira/browse/FINERACT-357 > Project: Apache Fineract > Issue Type: Task > Components: User Management >Reporter: Shaik Nazeer Hussain >Assignee: Shaik Nazeer Hussain > > As part of 0.5.0-incubating release, we got the following review comments > from IPMC members which should be addressed for 0.6.0-incubating release. > 1) Maven repo should be included in place of war file for the next release > 2) Gradle should be integrated in the top level directory. Currently it is > integrated with fineract-provider. (RAT issue) > 3) Including License and License.md will confuse the people > 4) The LICENSE maye be missing a license for jquery > 5) Remove the list of software included in the binary release from the source > release LICENSE file. It’s fine to have two different license files > 6) The convenience binary file is missing LICENSE, NOTICE and DISCLAIMER in > the top level, however the LICENSE and NOTICE file is inside the war and look > correct -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-357) Address the review comments for 0.6.0-incubating release
[ https://issues.apache.org/jira/browse/FINERACT-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-357: -- Summary: Address the review comments for 0.6.0-incubating release (was: Address the review comments as part of 0.5.0-incubating release) > Address the review comments for 0.6.0-incubating release > > > Key: FINERACT-357 > URL: https://issues.apache.org/jira/browse/FINERACT-357 > Project: Apache Fineract > Issue Type: Task > Components: User Management >Reporter: Shaik Nazeer Hussain >Assignee: Shaik Nazeer Hussain > > As part of 0.5.0-incubating release, we got the following review comments > from IPMC members which should be addressed for 0.6.0-incubating release. > 1) Maven repo should be included in place of war file for the next release > 2) Gradle should be integrated in the top level directory. Currently it is > integrated with fineract-provider. (RAT issue) > 3) Including License and License.md will confuse the people > 4) The LICENSE maye be missing a license for jquery > 5) Remove the list of software included in the binary release from the source > release LICENSE file. It’s fine to have two different license files > 6) The convenience binary file is missing LICENSE, NOTICE and DISCLAIMER in > the top level, however the LICENSE and NOTICE file is inside the war and look > correct -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-357) Address the review comments for 0.6.0-incubating release
[ https://issues.apache.org/jira/browse/FINERACT-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15787494#comment-15787494 ] Shaik Nazeer Hussain commented on FINERACT-357: --- 1) I am not sure whether it is feasible to have maven repo as we are distributing deployable war file. Waiting for mentors to give their opinion. 2) I believe, integrating RAT on top level directory is unnecessary effort as either we need to duplicate the gradle scripts at top level for RAT only or we need to move the complete source and build scripts from fineract-provider to top level directory. I think providing details how to run RAT check in readme file will suffice? 3) License.md will be renamed 4) Added jQuery license for v1.7, v1.7.1 5) Will remove the license files of source from binary and binary licenses from source > Address the review comments for 0.6.0-incubating release > > > Key: FINERACT-357 > URL: https://issues.apache.org/jira/browse/FINERACT-357 > Project: Apache Fineract > Issue Type: Task > Components: User Management >Reporter: Shaik Nazeer Hussain >Assignee: Shaik Nazeer Hussain > > As part of 0.5.0-incubating release, we got the following review comments > from IPMC members which should be addressed for 0.6.0-incubating release. > 1) Maven repo should be included in place of war file for the next release > 2) Gradle should be integrated in the top level directory. Currently it is > integrated with fineract-provider. (RAT issue) > 3) Including License and License.md will confuse the people > 4) The LICENSE maye be missing a license for jquery > 5) Remove the list of software included in the binary release from the source > release LICENSE file. It’s fine to have two different license files > 6) The convenience binary file is missing LICENSE, NOTICE and DISCLAIMER in > the top level, however the LICENSE and NOTICE file is inside the war and look > correct -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-309) Editing 'Product Mix' Not Working
[ https://issues.apache.org/jira/browse/FINERACT-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-309. --- Resolution: Fixed Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > Editing 'Product Mix' Not Working > > > Key: FINERACT-309 > URL: https://issues.apache.org/jira/browse/FINERACT-309 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain > > 1. Go to Admin>>Products and click on 'Product Mix' > 2. Create a product mix for a given loan product with allowed and restricted > product access. > 3. And then Edit the product mix with different allowed and restricted > products access and click on 'Submit' button. > Clicking on 'Submit' button doesn't show any effect. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-361) Getting error.msg.loanschedule.emi.amount.must.be.greter.than.interest on loan submit
[ https://issues.apache.org/jira/browse/FINERACT-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-361. --- Resolution: Fixed > Getting error.msg.loanschedule.emi.amount.must.be.greter.than.interest on > loan submit > - > > Key: FINERACT-361 > URL: https://issues.apache.org/jira/browse/FINERACT-361 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Adi Raju >Assignee: Adi Raju >Priority: Critical > > Submittal of loan application throws > error.msg.loanschedule.emi.amount.must.be.greter.than.interest error with > below parameters: > InterestRate is really high (For eg, 11% per month) > Interest Recalculation enabled > Monthly or yearly repayment > Disbursement date is between 29, 30, 31 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-357) Address the review comments for 0.6.0-incubating release
[ https://issues.apache.org/jira/browse/FINERACT-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820488#comment-15820488 ] Shaik Nazeer Hussain commented on FINERACT-357: --- The following review comments are addressed as part of 0.6.0-incubating release. I am closing this issue and creating two separate issues to address remaining two review comments. 3) Including License and License.md will confuse the people 4) The LICENSE maye be missing a license for jquery 5) Remove the list of software included in the binary release from the source release LICENSE file. It’s fine to have two different license files 6) The convenience binary file is missing LICENSE, NOTICE and DISCLAIMER in the top level, however the LICENSE and NOTICE file is inside the war and look correct > Address the review comments for 0.6.0-incubating release > > > Key: FINERACT-357 > URL: https://issues.apache.org/jira/browse/FINERACT-357 > Project: Apache Fineract > Issue Type: Task > Components: User Management >Reporter: Shaik Nazeer Hussain >Assignee: Shaik Nazeer Hussain > > As part of 0.5.0-incubating release, we got the following review comments > from IPMC members which should be addressed for 0.6.0-incubating release. > 1) Maven repo should be included in place of war file for the next release > 2) Gradle should be integrated in the top level directory. Currently it is > integrated with fineract-provider. (RAT issue) > 3) Including License and License.md will confuse the people > 4) The LICENSE maye be missing a license for jquery > 5) Remove the list of software included in the binary release from the source > release LICENSE file. It’s fine to have two different license files > 6) The convenience binary file is missing LICENSE, NOTICE and DISCLAIMER in > the top level, however the LICENSE and NOTICE file is inside the war and look > correct > Relevant e-mails: > http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CE4A4287E-8A78-4A61-9666-0F111BFA9D7C%40classsoftware.com%3E > http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CCA%2BULb%2BvcXGe5C%2ByiXdGS2gTD3vnpcs1e%3DoW5D6hffLSt%2BmOn0A%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-372) Include maven repo as part of Apache Fineract release
Shaik Nazeer Hussain created FINERACT-372: - Summary: Include maven repo as part of Apache Fineract release Key: FINERACT-372 URL: https://issues.apache.org/jira/browse/FINERACT-372 Project: Apache Fineract Issue Type: Test Reporter: Shaik Nazeer Hussain Assignee: Markus Geiss We are including war file as part of binary artifacts. As part of 0.5.0-incubating release IPMC members suggested to include maven repo in place of war file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-373) include gradle on top level directory instead of sub-directory(fineract-provider)
Shaik Nazeer Hussain created FINERACT-373: - Summary: include gradle on top level directory instead of sub-directory(fineract-provider) Key: FINERACT-373 URL: https://issues.apache.org/jira/browse/FINERACT-373 Project: Apache Fineract Issue Type: Test Reporter: Shaik Nazeer Hussain Assignee: Markus Geiss Gradle build scripts are included as part of fineract-provider. IPMC members suggested to have this on top level directory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-373) include gradle on top level directory instead of sub-directory(fineract-provider)
[ https://issues.apache.org/jira/browse/FINERACT-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-373. - Resolution: Duplicate Duplicate of https://issues.apache.org/jira/browse/FINERACT-371 > include gradle on top level directory instead of > sub-directory(fineract-provider) > -- > > Key: FINERACT-373 > URL: https://issues.apache.org/jira/browse/FINERACT-373 > Project: Apache Fineract > Issue Type: Test >Reporter: Shaik Nazeer Hussain >Assignee: Markus Geiss > > Gradle build scripts are included as part of fineract-provider. IPMC members > suggested to have this on top level directory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-372) Include maven repo as part of Apache Fineract release
[ https://issues.apache.org/jira/browse/FINERACT-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-372. - Resolution: Duplicate Duplicate of https://issues.apache.org/jira/browse/FINERACT-368 > Include maven repo as part of Apache Fineract release > - > > Key: FINERACT-372 > URL: https://issues.apache.org/jira/browse/FINERACT-372 > Project: Apache Fineract > Issue Type: Test >Reporter: Shaik Nazeer Hussain >Assignee: Markus Geiss > > We are including war file as part of binary artifacts. As part of > 0.5.0-incubating release IPMC members suggested to include maven repo in > place of war file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-374) Add Gradle wrapper download location in readme file
Shaik Nazeer Hussain created FINERACT-374: - Summary: Add Gradle wrapper download location in readme file Key: FINERACT-374 URL: https://issues.apache.org/jira/browse/FINERACT-374 Project: Apache Fineract Issue Type: Task Reporter: Shaik Nazeer Hussain Assignee: Markus Geiss Priority: Blocker Relevant e-mails: http://mail-archives.apache.org/mod_mbox/incubator-general/201701.mbox/%3CC8F9C232-D844-4920-BC9F-7DA536FAB6F5%40classsoftware.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FINERACT-380) S3 permission issue -- add system property
[ https://issues.apache.org/jira/browse/FINERACT-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-380: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > S3 permission issue -- add system property > -- > > Key: FINERACT-380 > URL: https://issues.apache.org/jira/browse/FINERACT-380 > Project: Apache Fineract > Issue Type: Improvement >Reporter: thynn win >Assignee: Shaik Nazeer Hussain >Priority: Critical > Labels: p1 > > Due to signature version 4 issue, I am unable to use S3 with Mifos. > Amazon suggested we add a system property and could you please help us add > this in the next version? > AWS Error Code: InvalidRequest, AWS Error Message: The authorization > mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256. > http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-380) S3 permission issue -- add system property
[ https://issues.apache.org/jira/browse/FINERACT-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15825482#comment-15825482 ] Shaik Nazeer Hussain commented on FINERACT-380: --- I don't find SDKGlobalConfiguration.ENABLE_S3_SIGV4_SYSTEM_PROPERTY in current version of S3 Java SDK. Looks like we need to migrate to newer version. i am trying to find some info in google on this. > S3 permission issue -- add system property > -- > > Key: FINERACT-380 > URL: https://issues.apache.org/jira/browse/FINERACT-380 > Project: Apache Fineract > Issue Type: Improvement >Reporter: thynn win >Assignee: Shaik Nazeer Hussain >Priority: Critical > Labels: p1 > > Due to signature version 4 issue, I am unable to use S3 with Mifos. > Amazon suggested we add a system property and could you please help us add > this in the next version? > AWS Error Code: InvalidRequest, AWS Error Message: The authorization > mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256. > http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-148) The sum of dividend to be posted does not match with total Dividend Amount
[ https://issues.apache.org/jira/browse/FINERACT-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-148: -- Priority: Minor (was: Major) > The sum of dividend to be posted does not match with total Dividend Amount > -- > > Key: FINERACT-148 > URL: https://issues.apache.org/jira/browse/FINERACT-148 > Project: Apache Fineract > Issue Type: Bug >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Minor > Attachments: clientsdiv.png, Dividend totals.png, totaldividen.png > > > Create a share product. > Create share accounts with varying number of shares > Initiate a dividend with a certain dividend amount > Click on this initiated dividend > The total amount allocated does not match with the dividend amount -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-329) The sum of dividend to be posted does not match with total Dividend Amount
[ https://issues.apache.org/jira/browse/FINERACT-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15825553#comment-15825553 ] Shaik Nazeer Hussain commented on FINERACT-329: --- Lowering the priority of https://issues.apache.org/jira/browse/FINERACT-148 > The sum of dividend to be posted does not match with total Dividend Amount > -- > > Key: FINERACT-329 > URL: https://issues.apache.org/jira/browse/FINERACT-329 > Project: Apache Fineract > Issue Type: Bug > Components: Dividends, Shares >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Critical > Labels: confirm, p1 > Attachments: Dividend totals.png > > > Reported by Ippez Robert at https://mifosforge.jira.com/browse/MIFOSX-2710 > Original Description: > Create a share product. > Create share accounts with varying number of shares > Initiate a dividend with a certain dividend amount > Click on this initiated dividend > The total amount allocated does not match with the dividend amount -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-150) After enabling maker checker tasks, Client awaiting for activation is not getting displayed under Pending approval in checker in box and tasks
[ https://issues.apache.org/jira/browse/FINERACT-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-150. - Resolution: Fixed Assignee: Shaik Nazeer Hussain (was: Markus Geiss) Santosh tested and working as expected. > After enabling maker checker tasks, Client awaiting for activation is not > getting displayed under Pending approval in checker in box and tasks > --- > > Key: FINERACT-150 > URL: https://issues.apache.org/jira/browse/FINERACT-150 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Shaik Nazeer Hussain >Priority: Minor > > 1. Click on Admin -> System -> Configuration -> Enable maker-checker task > 2. Create an client under pending approval state. > 3. Click on Checker inbox and tasks in which the client pending for activate > is displaying under checker inbox, it should be displayed under Client > approval. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-18) Unable to reschedule loan with fee attached
[
https://issues.apache.org/jira/browse/FINERACT-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaik Nazeer Hussain closed FINERACT-18.
Resolution: Fixed
Assignee: Shaik Nazeer Hussain (was: Markus Geiss)
Santosh tested and working as expected.
> Unable to reschedule loan with fee attached
> ---
>
> Key: FINERACT-18
> URL: https://issues.apache.org/jira/browse/FINERACT-18
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: Dayna Harp
>Assignee: Shaik Nazeer Hussain
>Priority: Critical
> Labels: confirm, p2
>
> https://mifosforge.jira.com/browse/MIFOSX-1593
> Whenever I try to reschedule loan installment, which has some fee or penalty
> assigned, the rescheduling request fails.
> Is this scenario supported?
> If so, how to overcome mentioned problem?
> The failing API call is this:
> POST https://xxx:8443/mifosng-provider/api/v1/rescheduleloans HTTP/1.1
> Host: xxx:8443
> Connection: keep-alive
> Accept: application/json, text/plain, */*
> Content-Type: application/json
> X-Mifos-Platform-TenantId: default
> Origin: http://localhost:9000
> Authorization: Basic xxx
> Accept-Encoding: gzip,deflate
> Accept-Language: en-GB,en-US;q=0.8,en;q=0.6
> Content-Length: 352
> {
> "loanId": 839,
> "graceOnPrincipal": 2,
> "rescheduleFromDate": "2014-10-31",
> "adjustedDueDate": "2014-11-20",
> "dateFormat": "-MM-dd",
> "locale": "en",
> "recalculateInterest": false,
> "submittedOnDate": "2014-09-27",
> "rescheduleReasonComment" : "Client has gone AWOL",
> "rescheduleReasonId": 1
> }
> Thanks in advance for any information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FINERACT-24) Getting internal server error when trying to post repayment for some loans
[ https://issues.apache.org/jira/browse/FINERACT-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-24: - Priority: Major (was: Critical) > Getting internal server error when trying to post repayment for some loans > -- > > Key: FINERACT-24 > URL: https://issues.apache.org/jira/browse/FINERACT-24 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss > Labels: confirm, p3 > > https://mifosforge.jira.com/browse/MIFOSX-2373 - see attachments and comments > When trying to post repayment for our loans (plain vanilla installment loans), > we get the following error. This happens in about 10% of cases: > "timestamp": 1449545515301 > "status": 500 > "error": "Internal Server Error" > "exception": "java.lang.ArithmeticException" > "message": "Non-terminating decimal expansion; no exact representable decimal > result." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-24) Getting internal server error when trying to post repayment for some loans
[ https://issues.apache.org/jira/browse/FINERACT-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15825558#comment-15825558 ] Shaik Nazeer Hussain commented on FINERACT-24: -- Lowering the priority as Santosh also couldn't reproduce it. > Getting internal server error when trying to post repayment for some loans > -- > > Key: FINERACT-24 > URL: https://issues.apache.org/jira/browse/FINERACT-24 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss > Labels: confirm, p3 > > https://mifosforge.jira.com/browse/MIFOSX-2373 - see attachments and comments > When trying to post repayment for our loans (plain vanilla installment loans), > we get the following error. This happens in about 10% of cases: > "timestamp": 1449545515301 > "status": 500 > "error": "Internal Server Error" > "exception": "java.lang.ArithmeticException" > "message": "Non-terminating decimal expansion; no exact representable decimal > result." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-380) S3 permission issue -- add system property
[ https://issues.apache.org/jira/browse/FINERACT-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15825605#comment-15825605 ] Shaik Nazeer Hussain commented on FINERACT-380: --- I tried with aws-java-sdk V1.11.79 and with user credentials provided by Thynn. I am getting 403. Amazon S3 issue Access Denied (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied; Request ID: 9EF03967A8174EA0) > S3 permission issue -- add system property > -- > > Key: FINERACT-380 > URL: https://issues.apache.org/jira/browse/FINERACT-380 > Project: Apache Fineract > Issue Type: Improvement >Reporter: thynn win >Assignee: Shaik Nazeer Hussain >Priority: Critical > Labels: p1 > > Due to signature version 4 issue, I am unable to use S3 with Mifos. > Amazon suggested we add a system property and could you please help us add > this in the next version? > AWS Error Code: InvalidRequest, AWS Error Message: The authorization > mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256. > http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-364) Submitting Collection Sheet through Maker Checker Throwing Error
[ https://issues.apache.org/jira/browse/FINERACT-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15825793#comment-15825793 ] Shaik Nazeer Hussain commented on FINERACT-364: --- Same issue with even group collection sheet. > Submitting Collection Sheet through Maker Checker Throwing Error > > > Key: FINERACT-364 > URL: https://issues.apache.org/jira/browse/FINERACT-364 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Blocker > Labels: p1 > Attachments: 1.png, 2.png, Screen Shot 2017-01-09 at 9.40.16 AM.png > > > 1. Enable Maker Checker in System>>Configuration. > 2. Go to System>>Configure Maker Checker Tasks and click on 'Edit', select > the center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot) > 3. Disburse JLG Loan to a client. > 4. Go to collection sheet and fill the details and select the center name but > don't select the group name. > 5. Click on Submit button, which goes to Checker Inbox. > 6. When you try to approve it , it throws the error, > "The parameter `loanTransactions` has been passed and is not supported for > this request. > The parameter `SavingsTransactions` has been passed and is not supported for > this request." > Check the attached file/screenshots. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FINERACT-364) Submitting Collection Sheet through Maker Checker Throwing Error
[ https://issues.apache.org/jira/browse/FINERACT-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-364: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > Submitting Collection Sheet through Maker Checker Throwing Error > > > Key: FINERACT-364 > URL: https://issues.apache.org/jira/browse/FINERACT-364 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Blocker > Labels: p1 > Attachments: 1.png, 2.png, Screen Shot 2017-01-09 at 9.40.16 AM.png > > > 1. Enable Maker Checker in System>>Configuration. > 2. Go to System>>Configure Maker Checker Tasks and click on 'Edit', select > the center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot) > 3. Disburse JLG Loan to a client. > 4. Go to collection sheet and fill the details and select the center name but > don't select the group name. > 5. Click on Submit button, which goes to Checker Inbox. > 6. When you try to approve it , it throws the error. > "The parameter `loanTransactions` has been passed and is not supported for > this request. > The parameter `SavingsTransactions` has been passed and is not supported for > this request." > Check the attached file/screenshots. > The above same error is thrown when, > > You select both center and group and submit collection sheet. > > We try to submit through 'productive collection sheet'. > > We try to submit 'Individual Collection Sheet'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-364) Submitting Collection Sheet through Maker Checker Throwing Error
[ https://issues.apache.org/jira/browse/FINERACT-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15825958#comment-15825958 ] Shaik Nazeer Hussain commented on FINERACT-364: --- Sent a PR https://github.com/apache/incubator-fineract/pull/276. > Submitting Collection Sheet through Maker Checker Throwing Error > > > Key: FINERACT-364 > URL: https://issues.apache.org/jira/browse/FINERACT-364 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Blocker > Labels: p1 > Attachments: 1.png, 2.png, Screen Shot 2017-01-09 at 9.40.16 AM.png > > > 1. Enable Maker Checker in System>>Configuration. > 2. Go to System>>Configure Maker Checker Tasks and click on 'Edit', select > the center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot) > 3. Disburse JLG Loan to a client. > 4. Go to collection sheet and fill the details and select the center name but > don't select the group name. > 5. Click on Submit button, which goes to Checker Inbox. > 6. When you try to approve it , it throws the error. > "The parameter `loanTransactions` has been passed and is not supported for > this request. > The parameter `SavingsTransactions` has been passed and is not supported for > this request." > Check the attached file/screenshots. > The above same error is thrown when, > > You select both center and group and submit collection sheet. > > We try to submit through 'productive collection sheet'. > > We try to submit 'Individual Collection Sheet'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-380) S3 permission issue -- add system property
[ https://issues.apache.org/jira/browse/FINERACT-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827534#comment-15827534 ] Shaik Nazeer Hussain commented on FINERACT-380: --- AWS support ticket is raised as we are getting the following exception for region Regions.AP_NORTHEAST_2 Java Exception: com.amazonaws.services.s3.model.AmazonS3Exception: Access Denied (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied; Request ID: x), S3 Extended Request ID: xx > S3 permission issue -- add system property > -- > > Key: FINERACT-380 > URL: https://issues.apache.org/jira/browse/FINERACT-380 > Project: Apache Fineract > Issue Type: Improvement >Reporter: thynn win >Assignee: Shaik Nazeer Hussain >Priority: Critical > Labels: p1 > > Due to signature version 4 issue, I am unable to use S3 with Mifos. > Amazon suggested we add a system property and could you please help us add > this in the next version? > AWS Error Code: InvalidRequest, AWS Error Message: The authorization > mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256. > http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-16) Cannot close Savings Account when linked to a loan even when loan status is closed
[ https://issues.apache.org/jira/browse/FINERACT-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827617#comment-15827617 ] Shaik Nazeer Hussain commented on FINERACT-16: -- Before approval, there is no option to close the loan. User has the option to delete the loan. While deleting the loan, we are not deleting the existing accountAssociations. This is causing DataIntegrityVoilation. > Cannot close Savings Account when linked to a loan even when loan status is > closed > -- > > Key: FINERACT-16 > URL: https://issues.apache.org/jira/browse/FINERACT-16 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Critical > Labels: p1 > > https://mifosforge.jira.com/browse/MIFOSX-2293 > 1. Create and activate a client > 2. Create and activated a savings account for the client, deposit some amount > in the account > 3. Link the above savings account to a new loan application and Submit the > loan application, Don't approve, it close the loan. > 4. Try to close the above savings account and check the Withdraw Balance > _Error > Closing savings account with id:11 is not allowed, since it is linked with > one of the active loans_ > The same error is got if even the loan account is paid all and closed. > I think the cause is, when a loan account is closed, withdrawn, or rejected > the linked savings account remains linked.to the loan account hence this > error. > This is very critical barrier -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FINERACT-16) Cannot close Savings Account when linked to a loan even when loan status is closed
[ https://issues.apache.org/jira/browse/FINERACT-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-16: Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > Cannot close Savings Account when linked to a loan even when loan status is > closed > -- > > Key: FINERACT-16 > URL: https://issues.apache.org/jira/browse/FINERACT-16 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Reporter: Dayna Harp >Assignee: Shaik Nazeer Hussain >Priority: Critical > Labels: p1 > > https://mifosforge.jira.com/browse/MIFOSX-2293 > 1. Create and activate a client > 2. Create and activated a savings account for the client, deposit some amount > in the account > 3. Link the above savings account to a new loan application and Submit the > loan application, Don't approve, it close the loan. > 4. Try to close the above savings account and check the Withdraw Balance > _Error > Closing savings account with id:11 is not allowed, since it is linked with > one of the active loans_ > The same error is got if even the loan account is paid all and closed. > I think the cause is, when a loan account is closed, withdrawn, or rejected > the linked savings account remains linked.to the loan account hence this > error. > This is very critical barrier -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-16) Cannot close Savings Account when linked to a loan even when loan status is closed
[ https://issues.apache.org/jira/browse/FINERACT-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-16. -- Resolution: Fixed With this PR https://github.com/apache/incubator-fineract/pull/277 this issue will be closed > Cannot close Savings Account when linked to a loan even when loan status is > closed > -- > > Key: FINERACT-16 > URL: https://issues.apache.org/jira/browse/FINERACT-16 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Reporter: Dayna Harp >Assignee: Shaik Nazeer Hussain >Priority: Critical > Labels: p1 > > https://mifosforge.jira.com/browse/MIFOSX-2293 > 1. Create and activate a client > 2. Create and activated a savings account for the client, deposit some amount > in the account > 3. Link the above savings account to a new loan application and Submit the > loan application, Don't approve, it close the loan. > 4. Try to close the above savings account and check the Withdraw Balance > _Error > Closing savings account with id:11 is not allowed, since it is linked with > one of the active loans_ > The same error is got if even the loan account is paid all and closed. > I think the cause is, when a loan account is closed, withdrawn, or rejected > the linked savings account remains linked.to the loan account hence this > error. > This is very critical barrier -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-364) Submitting Collection Sheet through Maker Checker Throwing Error
[ https://issues.apache.org/jira/browse/FINERACT-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-364. --- Resolution: Fixed With this PR https://github.com/apache/incubator-fineract/pull/276 issue will be resolved. > Submitting Collection Sheet through Maker Checker Throwing Error > > > Key: FINERACT-364 > URL: https://issues.apache.org/jira/browse/FINERACT-364 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Blocker > Labels: p1 > Attachments: 1.png, 2.png, Screen Shot 2017-01-09 at 9.40.16 AM.png > > > 1. Enable Maker Checker in System>>Configuration. > 2. Go to System>>Configure Maker Checker Tasks and click on 'Edit', select > the center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot) > 3. Disburse JLG Loan to a client. > 4. Go to collection sheet and fill the details and select the center name but > don't select the group name. > 5. Click on Submit button, which goes to Checker Inbox. > 6. When you try to approve it , it throws the error. > "The parameter `loanTransactions` has been passed and is not supported for > this request. > The parameter `SavingsTransactions` has been passed and is not supported for > this request." > Check the attached file/screenshots. > The above same error is thrown when, > > You select both center and group and submit collection sheet. > > We try to submit through 'productive collection sheet'. > > We try to submit 'Individual Collection Sheet'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-348) Issues when doing a "Close-As-Rescheduled" on a loan
[ https://issues.apache.org/jira/browse/FINERACT-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-348: -- Issue Type: Improvement (was: Bug) > Issues when doing a "Close-As-Rescheduled" on a loan > - > > Key: FINERACT-348 > URL: https://issues.apache.org/jira/browse/FINERACT-348 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Critical > Labels: p1 > > Reported by Binny at https://mifosforge.jira.com/browse/MIFOSX-1205 > Original Description: > When closing a loan using the "Close (as Rescheduled)" button, the loan > account is closed, but there are no transactions or accounting entries made > for this closure. This not correct. > The following should be done: > 1) A new transaction should be visible to user under transactions to show > that the loan was closed as rescheduled rather than leaving the loan as is > without any changes. This means that Mifos X should mkae a new entry > m_loan_transaction table - with transaction_type_enum = 7 and amount as the > total outstanding amount (principal + interest + fees). > 2) Ensure that the right accounting entries are made when closing the loan as > "closed (as rescheduled)". This involves: > For loan products: capturing another General Ledger account head under > “Rescheduled in Suspense” – for example: “Rescheduled Loans Suspense Account” > When closing as loan as rescheduled, passing the following entries: > a) For Cash Accounting: > Debit: Rescheduled Loan Suspense Account (with only principal outstanding > amount) > Credit: Loan portfolio > b) For Accrual (upfront): > Debit: Rescheduled Loan Suspense Account (sum of outstanding principal + > interest + fees + penalties) > Credit: Loan portfolio (with principal outstanding amount) > Credit: Interest Receivable (with interest outstanding amount) > Credit: Fees Receivable (with fees outstanding amount) > Credit: Penalties Receivable (with penalties outstanding amount) > c) For Accrual (periodic): > Debit: Rescheduled Loan Suspense Account (sum of outstanding principal + > interest receivable accounted + fees receivable accounted + penalties > receivable accounted) > Credit: Loan portfolio (with principal outstanding amount) > Credit: Interest Receivable (with interest receivable accounted) > Credit: Fees Receivable (with fees receivable accounted) > Credit: Penalties Receivable (with penalties receivable accounted) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-221) After submitting the modify application the currency is not getting updated as per the new product
[ https://issues.apache.org/jira/browse/FINERACT-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-221: -- Labels: p1 (was: confirm p1) > After submitting the modify application the currency is not getting updated > as per the new product > -- > > Key: FINERACT-221 > URL: https://issues.apache.org/jira/browse/FINERACT-221 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Markus Geiss > Labels: p1 > > 1. Create 2 loan products, one with Indian rupees as currency and another > with US Dollar > 2. Submit new loan application for a client with the loan prouduct1. > 3. Click on modify application and modify to product2. > 4. In the loan general page currency is not getting updated to US Dollar, > rather it is remaining as Indian Rupees only. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-221) After submitting the modify application the currency is not getting updated as per the new product
[ https://issues.apache.org/jira/browse/FINERACT-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827688#comment-15827688 ] Shaik Nazeer Hussain commented on FINERACT-221: --- This issue is still open. > After submitting the modify application the currency is not getting updated > as per the new product > -- > > Key: FINERACT-221 > URL: https://issues.apache.org/jira/browse/FINERACT-221 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Markus Geiss > Labels: p1 > > 1. Create 2 loan products, one with Indian rupees as currency and another > with US Dollar > 2. Submit new loan application for a client with the loan prouduct1. > 3. Click on modify application and modify to product2. > 4. In the loan general page currency is not getting updated to US Dollar, > rather it is remaining as Indian Rupees only. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-21) Waive overdue charge is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-21. Resolution: Fixed Assignee: Shaik Nazeer Hussain (was: Markus Geiss) Tested by Santosh and this issue is no more reproducible. > Waive overdue charge is not working as expected > --- > > Key: FINERACT-21 > URL: https://issues.apache.org/jira/browse/FINERACT-21 > Project: Apache Fineract > Issue Type: Bug > Components: Charges >Reporter: Dayna Harp >Assignee: Shaik Nazeer Hussain > Labels: confirm, p1 > > https://mifosforge.jira.com/browse/MIFOSX-2392 - see attachments > 1. Create overdue charge - 100 - Flat, Create a simple loan product and apply > the above created charge to it. > 2. Submit new loan application for a client on 01 October 2015 approve and > disburse on same date. > 3. Execute the scheduler job "Apply penalty for overdue loans", > 4. Navigate back to the same loan account page and click on the charges and > waive charge on 01 November 2015. > > Charge got waved, but in the repayment schedule wrong entries got created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-22) Adding Floating Interest Rate "Error" - cannot create floating rate
[ https://issues.apache.org/jira/browse/FINERACT-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-22. Resolution: Fixed Assignee: Shaik Nazeer Hussain (was: Markus Geiss) Tested by Santosh and working as expected. > Adding Floating Interest Rate "Error" - cannot create floating rate > --- > > Key: FINERACT-22 > URL: https://issues.apache.org/jira/browse/FINERACT-22 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Shaik Nazeer Hussain > Labels: confirm, p1 > > https://mifosforge.jira.com/browse/MIFOSX-2391 - see attachments > When a user tries to add a new Floating rate, non-descript "Error" is > returned. > 2nd MAJOR ISSUE: New Product cannot be created if Floating Rate not defined. > "Error > The parameter `isLinkedToFloatingInterestRates` has been passed and is not > supported for this request." returned. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-106) Not able to change week day in Center meeting with weekly meeting attached, displays Internal server error
[ https://issues.apache.org/jira/browse/FINERACT-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-106. - Resolution: Fixed Assignee: subramanyasn (was: Markus Geiss) Santosh tested on 16.12.01.RELEASE and working as expected. > Not able to change week day in Center meeting with weekly meeting attached, > displays Internal server error > -- > > Key: FINERACT-106 > URL: https://issues.apache.org/jira/browse/FINERACT-106 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: subramanyasn > Labels: confirm, p1 > Attachments: Edit Center meeting.png > > > 1. Create a Center with weekly meeting attached from 01 March 2016 and every > week on Friday. > 2. Click on edit meeting and change day in a week as Wednesday and click on > submit button. > > Not able to save the page displays internal server error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-137) Created parent GL account is not displaying properly in the dropdown while creating the GL Account
[ https://issues.apache.org/jira/browse/FINERACT-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-137. - Resolution: Fixed Assignee: subramanyasn (was: Markus Geiss) Santosh tested on 16.12.01.RELEASE and working as expected. > Created parent GL account is not displaying properly in the dropdown while > creating the GL Account > -- > > Key: FINERACT-137 > URL: https://issues.apache.org/jira/browse/FINERACT-137 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting >Reporter: subramanyasn >Assignee: subramanyasn > Labels: confirm, p1 > Attachments: Create GL Account page.png > > > 1. Create a GL account for Assets and Account usage as Header. > 2. Create a GL account for Assets, account usage as Detail and parent as > created above. > 3. It is allowing to create the GL account for assets with Account usage as > detail. > > If the Header is more than 12 in entities then it is not getting displayed > > in the drop down under Parent while creating the GL account. > > The Header accounts created is getting displayed under Parent dropdown for > > all account types. it should get filtered according to the account types. > > Eg. If the account type is Equity only equity related header accounts > > should get displayed under parent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-380) S3 permission issue -- add system property
[
https://issues.apache.org/jira/browse/FINERACT-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827972#comment-15827972
]
Shaik Nazeer Hussain commented on FINERACT-380:
---
Got the update from AWS and see the comments below
The current policy only allows actions on the bucket (like List), it does not
allow actions on objects in the bucket. If this is required, you will need to
update the IAM policy as follows:
{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"s3:*"
],
"Resource": [
"arn:aws:s3:::prd-prdbeta",
"arn:aws:s3:::prd-prdbeta/*"
],
"Effect": "Allow"
}
]
}
A similar example is shown here:
http://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_examples.html
> S3 permission issue -- add system property
> --
>
> Key: FINERACT-380
> URL: https://issues.apache.org/jira/browse/FINERACT-380
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: thynn win
>Assignee: Shaik Nazeer Hussain
>Priority: Critical
> Labels: p1
>
> Due to signature version 4 issue, I am unable to use S3 with Mifos.
> Amazon suggested we add a system property and could you please help us add
> this in the next version?
> AWS Error Code: InvalidRequest, AWS Error Message: The authorization
> mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.
> http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (FINERACT-380) S3 permission issue -- add system property
[
https://issues.apache.org/jira/browse/FINERACT-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827972#comment-15827972
]
Shaik Nazeer Hussain edited comment on FINERACT-380 at 1/18/17 12:37 PM:
-
Got the update from AWS and see the comments below
The current policy only allows actions on the bucket (like List), it does not
allow actions on objects in the bucket. If this is required, you will need to
update the IAM policy as follows:
{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"s3:*"
],
"Resource": [
"arn:aws:s3:::BUCKET_NAME",
"arn:aws:s3:::BUCKET_NAME/*"
],
"Effect": "Allow"
}
]
}
A similar example is shown here:
http://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_examples.html
was (Author: nazeer1100126):
Got the update from AWS and see the comments below
The current policy only allows actions on the bucket (like List), it does not
allow actions on objects in the bucket. If this is required, you will need to
update the IAM policy as follows:
{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"s3:*"
],
"Resource": [
"arn:aws:s3:::prd-prdbeta",
"arn:aws:s3:::prd-prdbeta/*"
],
"Effect": "Allow"
}
]
}
A similar example is shown here:
http://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_examples.html
> S3 permission issue -- add system property
> --
>
> Key: FINERACT-380
> URL: https://issues.apache.org/jira/browse/FINERACT-380
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: thynn win
>Assignee: Shaik Nazeer Hussain
>Priority: Critical
> Labels: p1
>
> Due to signature version 4 issue, I am unable to use S3 with Mifos.
> Amazon suggested we add a system property and could you please help us add
> this in the next version?
> AWS Error Code: InvalidRequest, AWS Error Message: The authorization
> mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.
> http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (FINERACT-142) In loan "Account Detail" page the maturity date is displayed is not proper
[ https://issues.apache.org/jira/browse/FINERACT-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-142. - Resolution: Fixed Assignee: subramanyasn (was: Markus Geiss) Santosh tested on 16.12.01.RELEASE and working as expected. > In loan "Account Detail" page the maturity date is displayed is not proper > -- > > Key: FINERACT-142 > URL: https://issues.apache.org/jira/browse/FINERACT-142 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: subramanyasn >Assignee: subramanyasn > Labels: confirm, p2 > Attachments: Maturity date.png > > > 1. Create a loan product with interest recalculation enabled (Interest > calculation - daily and recalculation -daily). monthly repayment. > 2. Submit new loan application for a client on 01 Jan 2015. Approve and > disburse loan on same date. > 3. Click on the repayment schedule in which the new row with the interest > accrued till current date is displayed. > 4. Click on the Account detail page in which the loan maturity date is > displayed as today's system date. > Expected: > The loan maturity date should not get modified due to the new row created > with the interest accrued till current system date. It should be as per > original schedule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-174) Can't select "Escheat Liability" account for deposit products
[ https://issues.apache.org/jira/browse/FINERACT-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-174. - Resolution: Fixed Santosh tested on 16.12.01.RELEASE and it is working as expected. > Can't select "Escheat Liability" account for deposit products > - > > Key: FINERACT-174 > URL: https://issues.apache.org/jira/browse/FINERACT-174 > Project: Apache Fineract > Issue Type: Bug > Components: Savings > Environment: Product Server (https://demo4.openmf.org) >Reporter: Edward Cable >Assignee: subramanyasn > Labels: confirm, p2 > Attachments: Screen Shot 2016-06-15 at 2.07.47 PM.png > > > Not sure if this is a bug within Fineract or the Community App (perhaps in > selection of the account). > While attempting to test out the dormant/inactive savings account feature and > the ability to escheat funds after a given number of days, I was unable to > configure the general ledger account mapping for the Escheat Liability > account for the savings product I was editing. > To repro, log in to https://demo4.openmf.org with credentials, > Mifos/MifosAdmin > Go to Products >> Savings Products >> Basic Savings Account >> Edit >> > Attempt to select an account for Escheat Liability (I newly created Escheated > Deposits). > Click Submit > See error message that gets displayed: > field is required > error.msg.productToAccountMapping.not.found -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-213) Not able to foreclose the loan on current system date moves to Overpaid state.
[ https://issues.apache.org/jira/browse/FINERACT-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-213. - Resolution: Fixed Santosh tested on 16.12.01.RELEASE and working as expected > Not able to foreclose the loan on current system date moves to Overpaid state. > -- > > Key: FINERACT-213 > URL: https://issues.apache.org/jira/browse/FINERACT-213 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: subramanyasn >Assignee: Markus Geiss > Labels: confirm, p1 > > 1. Create a loan product (without interest recalculation), Create a client. > 2. Disburse loan for a client on 01 August 2016. > 3. Fore close the loan on current system date. > > Loan should get closed but moving to overpaid state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-219) Edit Data table Entry for client, date format displayed is improper
[ https://issues.apache.org/jira/browse/FINERACT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-219. - Resolution: Fixed Santosh tested on 16.12.01.RELEASE and working as expected. > Edit Data table Entry for client, date format displayed is improper > --- > > Key: FINERACT-219 > URL: https://issues.apache.org/jira/browse/FINERACT-219 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Markus Geiss > Labels: Github > Attachments: Edit datable entry.png > > > 1. Create data table for a client. with the data sets as mentioned in the > attachment, > 2. Click on clients-> any created client -> Click on the data table created > -> enter the valid inputs and save the page. > 3. Click on the edit button in the same page. > > Date and time format displayed is not proper -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-380) S3 permission issue -- add system property
[ https://issues.apache.org/jira/browse/FINERACT-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829564#comment-15829564 ] Shaik Nazeer Hussain commented on FINERACT-380: --- I have tested by adding mentioned system property and updating aws java sdk to 1.11.80 and I don't see any issue. But the problem is, this dependency is adding 50 MB aws jars to war file. I have started analyzing how to exclude the unnecessary jars. > S3 permission issue -- add system property > -- > > Key: FINERACT-380 > URL: https://issues.apache.org/jira/browse/FINERACT-380 > Project: Apache Fineract > Issue Type: Improvement >Reporter: thynn win >Assignee: Shaik Nazeer Hussain >Priority: Critical > Labels: p1 > > Due to signature version 4 issue, I am unable to use S3 with Mifos. > Amazon suggested we add a system property and could you please help us add > this in the next version? > AWS Error Code: InvalidRequest, AWS Error Message: The authorization > mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256. > http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-278) The new deposit and withdraw buttons at the client detail screen are not affected when assigning user rules and permissions
[ https://issues.apache.org/jira/browse/FINERACT-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-278. - Resolution: Fixed Santosh tested on 16.12.01.RELEASE and works as expected. > The new deposit and withdraw buttons at the client detail screen are not > affected when assigning user rules and permissions > --- > > Key: FINERACT-278 > URL: https://issues.apache.org/jira/browse/FINERACT-278 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Reporter: Santosh Math >Assignee: Markus Geiss > Labels: confirm, p1 > > Reported by Ronnie at https://mifosforge.jira.com/browse/MIFOSX-1477 > Original Description: > The new deposit and withdraw buttons at the client detail screen are not > affected when assigning user rules and permissions. there is no way of > blocking users from accessing these buttons and a user with deposit, > withdraw, loan payment, disbursement etc can access these restricted area > through these buttons. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-207) Loan prepayment fails if Installation Fee charge set
[
https://issues.apache.org/jira/browse/FINERACT-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaik Nazeer Hussain closed FINERACT-207.
-
Resolution: Fixed
Santosh tested on 16.12.01.RELEASE and works as expected
> Loan prepayment fails if Installation Fee charge set
>
>
> Key: FINERACT-207
> URL: https://issues.apache.org/jira/browse/FINERACT-207
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: Terence Denzil Monteiro
>Assignee: Markus Geiss
> Labels: confirm, p1
>
> For Loan Product where Charge Time Type = Installation Fee,
> if a loan is created and modified before approval
> if I try to prepay the loan, it gives HTTP 500 response code with body:
> {"timestamp":1470637896498,"status":500,"error":"Internal Server
> Error","exception":"java.lang.NullPointerException","message":null}
> for example, see loan #819 on demo server:
> https://demo.openmf.org/#/loanaccount/819/prepayloan, for client #10: JAVA BOY
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (FINERACT-207) Loan prepayment fails if Installation Fee charge set
[
https://issues.apache.org/jira/browse/FINERACT-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaik Nazeer Hussain reopened FINERACT-207:
---
Assignee: Shaik Nazeer Hussain (was: Markus Geiss)
> Loan prepayment fails if Installation Fee charge set
>
>
> Key: FINERACT-207
> URL: https://issues.apache.org/jira/browse/FINERACT-207
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: Terence Denzil Monteiro
>Assignee: Shaik Nazeer Hussain
> Labels: confirm, p1
>
> For Loan Product where Charge Time Type = Installation Fee,
> if a loan is created and modified before approval
> if I try to prepay the loan, it gives HTTP 500 response code with body:
> {"timestamp":1470637896498,"status":500,"error":"Internal Server
> Error","exception":"java.lang.NullPointerException","message":null}
> for example, see loan #819 on demo server:
> https://demo.openmf.org/#/loanaccount/819/prepayloan, for client #10: JAVA BOY
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (FINERACT-5) Interest re-calculation setup for loan product but repayment doesn't occur
[ https://issues.apache.org/jira/browse/FINERACT-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-5. - Resolution: Fixed Assignee: Shaik Nazeer Hussain (was: Markus Geiss) Resolved with PR https://github.com/apache/incubator-fineract/pull/279 > Interest re-calculation setup for loan product but repayment doesn't occur > -- > > Key: FINERACT-5 > URL: https://issues.apache.org/jira/browse/FINERACT-5 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Shaik Nazeer Hussain >Priority: Blocker > Labels: confirm, p1 > Attachments: new 1 > > > Moved from Mifos X https://mifosforge.jira.com/browse/MIFOSX-2501. > Original Notes: Tested for the bug in 16.01.1, and 16.01.2 and confirm the > defect is present in both the versions > Created a loan product with interest re-calculation option enabled and the > necessary fields filled in. > Created a group and Loan. Disbursed the loan. Till this point no issue. On > trying to make payment the is no error display, the repayment entry is not > made. > Log file here: https://mifosforge.jira.com/browse/MIFOSX-2501 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
