[jira] [Updated] (FINERACT-317) Installment amount defined for flat type loans is not working properly for Amortization "Equal Installments"
[ https://issues.apache.org/jira/browse/FINERACT-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-317: -- Issue Type: Improvement (was: Bug) > Installment amount defined for flat type loans is not working properly for > Amortization "Equal Installments" > - > > Key: FINERACT-317 > URL: https://issues.apache.org/jira/browse/FINERACT-317 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss > Labels: p1 > Attachments: 115.png, 116.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2260 > Original Description: > 1. Create Loan product with Amortization -"Equal Installment" and Interest > type as "Flat", Select the check box "Allow fixing of the installment amount". > 2. Submit new loan application for a client with the above loan product on 01 > September 2015, Loan amount 1, no. of repayments 12, repaid every 1 > month, define installment amount as 950. > > Since installment amount is defined all installment amount should be 950, > > since flat interest method is defined interest calculated should be 100 > > throughout the loan and for last installment the repayment should get > > adjusted with the balance. > > Here it is displaying installment amount as 933.33 only. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FINERACT-344) Should not allow to add guarantor ,If savings account activation date is gretar than loan application submitted date
[ https://issues.apache.org/jira/browse/FINERACT-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-344. --- Resolution: Fixed Assignee: Santosh Math (was: Markus Geiss) Fix Version/s: 1.0.0 > Should not allow to add guarantor ,If savings account activation date is > gretar than loan application submitted date > > > Key: FINERACT-344 > URL: https://issues.apache.org/jira/browse/FINERACT-344 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Santosh Math > Labels: p1 > Fix For: 1.0.0 > > Attachments: create external guarantor.png, Creater self > guarantor.png, New loan application.png > > > Original Description: > 1. Create a Loan Product with the following credentials > -->principal amount as 1,Number of repayments 12,Nominal Interest rate 1% > p.a,Rapid every 1 month,Amortization as Equal installments ,Interest Method > as Declining Balance,Interest Calculation Period as Same as repayment > period,Repayment Strategy as Mifos style ,In Guarantee Requirements check > Place Guarantee Funds On-Hold? give Mandatory Guarantee: (%) as 100, Minimum > Guarantee from Own Funds: (%) as 50, Minimum from Guarantor Funds: (%) 50. > 2.Create 2 Clients and activate on 1 jan 2014, active 1 saving account for > each client with balance 5 on 1 may 2015 > 3. Submit new loan application for the same client on 1 jan 2015 > 4. Click on more in same loan account page ,click on create guarantor , > select self guarantor with 5000 and external guarantor as 5000 > 5.Now approve the loan > >Should not allow to approve the loan since saving account activation date is > >grater than loan submitted date. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FINERACT-345) Should not allow to add guarantor, If savings account transaction date is greater that loan application submitted date
[ https://issues.apache.org/jira/browse/FINERACT-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-345. --- Resolution: Fixed Assignee: Santosh Math (was: Markus Geiss) Fix Version/s: 1.0.0 > Should not allow to add guarantor, If savings account transaction date is > greater that loan application submitted date > -- > > Key: FINERACT-345 > URL: https://issues.apache.org/jira/browse/FINERACT-345 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Santosh Math > Labels: p1 > Fix For: 1.0.0 > > > Reported by Savita Pujar at https://mifosforge.jira.com/browse/MIFOSX-2128 > Original Description: > 1. Create a Loan Product with the following credentials > -->principal amount as 1,Number of repayments 12,Nominal Interest rate 1% > p.a,Rapid every 1 month,Amortization as Equal installments ,Interest Method > as Declining Balance,Interest Calculation Period as Same as repayment > period,Repayment Strategy as Mifos style ,In Guarantee Requirements check > Place Guarantee Funds On-Hold? give Mandatory Guarantee: (%) as 100, Minimum > Guarantee from Own Funds: (%) as 50, Minimum from Guarantor Funds: (%) 50. > 2.Create 2 Clients and activate on 1 jan 2014, active 1 saving account for > each client with balance 500 on 1 December 2014. > 3. Deposit 5 amount in each savings account on 1 Feb 2015 > 4. Submit new loan application for the same client on 1 jan 2015 > 5.Click on more in same loan account page ,click on create guarantor , select > self guarantor with 5000 and external guarantor as 5000 > 6.Now approve the loan > >Should not allow to approve the loan since saving account transaction date > >is grater than loan submitted date. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (FINERACT-330) No error message is getting displayed in productive collection sheet if meeting is not attached to center/group
[ https://issues.apache.org/jira/browse/FINERACT-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-330: - Assignee: Santosh Math (was: Shaik Nazeer Hussain) > No error message is getting displayed in productive collection sheet if > meeting is not attached to center/group > - > > Key: FINERACT-330 > URL: https://issues.apache.org/jira/browse/FINERACT-330 > Project: Apache Fineract > Issue Type: Bug > Components: Client, Groups >Reporter: Santosh Math >Assignee: Santosh Math >Priority: Minor > Labels: p2 > Fix For: 0.7.0-incubating > > Attachments: 1.png > > > Steps to reproduce: > 1. Create a center under Head Office and activate it on 01 Jan 2013.Attach > staff. Don't attach meeting. > 2. Create a group under this center and activate it on 01 Jan 2013. > 3. Create a client in this group with activation date 01 Jan 2013 > 4. Approve and Disburse JLG Loan(Frequeny weekly repayment) 02 Jan 2015. > 5. Go to collection sheet. and select: > Branch Office: Head Office > Meeting Calender: 09 Jan 2015 > Staff: *provide same staff name of the center > 6. Click on "Productive Collection Sheet". > In Productive Collection Sheet page, there is no error message is displayed > related to meeting not attached. > Expected Result: the error message should be displayed as "Collection can not > be generated without meeting attached to center" > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FINERACT-330) No error message is getting displayed in productive collection sheet if meeting is not attached to center/group
[ https://issues.apache.org/jira/browse/FINERACT-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-330. --- Resolution: Fixed Fix Version/s: 0.7.0-incubating > No error message is getting displayed in productive collection sheet if > meeting is not attached to center/group > - > > Key: FINERACT-330 > URL: https://issues.apache.org/jira/browse/FINERACT-330 > Project: Apache Fineract > Issue Type: Bug > Components: Client, Groups >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Minor > Labels: p2 > Fix For: 0.7.0-incubating > > Attachments: 1.png > > > Steps to reproduce: > 1. Create a center under Head Office and activate it on 01 Jan 2013.Attach > staff. Don't attach meeting. > 2. Create a group under this center and activate it on 01 Jan 2013. > 3. Create a client in this group with activation date 01 Jan 2013 > 4. Approve and Disburse JLG Loan(Frequeny weekly repayment) 02 Jan 2015. > 5. Go to collection sheet. and select: > Branch Office: Head Office > Meeting Calender: 09 Jan 2015 > Staff: *provide same staff name of the center > 6. Click on "Productive Collection Sheet". > In Productive Collection Sheet page, there is no error message is displayed > related to meeting not attached. > Expected Result: the error message should be displayed as "Collection can not > be generated without meeting attached to center" > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (FINERACT-330) No error message is getting displayed in productive collection sheet if meeting is not attached to center/group
[ https://issues.apache.org/jira/browse/FINERACT-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-330: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > No error message is getting displayed in productive collection sheet if > meeting is not attached to center/group > - > > Key: FINERACT-330 > URL: https://issues.apache.org/jira/browse/FINERACT-330 > Project: Apache Fineract > Issue Type: Bug > Components: Client, Groups >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Minor > Labels: p2 > Attachments: 1.png > > > Steps to reproduce: > 1. Create a center under Head Office and activate it on 01 Jan 2013.Attach > staff. Don't attach meeting. > 2. Create a group under this center and activate it on 01 Jan 2013. > 3. Create a client in this group with activation date 01 Jan 2013 > 4. Approve and Disburse JLG Loan(Frequeny weekly repayment) 02 Jan 2015. > 5. Go to collection sheet. and select: > Branch Office: Head Office > Meeting Calender: 09 Jan 2015 > Staff: *provide same staff name of the center > 6. Click on "Productive Collection Sheet". > In Productive Collection Sheet page, there is no error message is displayed > related to meeting not attached. > Expected Result: the error message should be displayed as "Collection can not > be generated without meeting attached to center" > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FINERACT-243) Constitution Type Required Field
[ https://issues.apache.org/jira/browse/FINERACT-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-243. --- Resolution: Fixed Assignee: Santosh Math (was: Shaik Nazeer Hussain) Fix Version/s: 0.7.0-incubating With PR https://github.com/apache/incubator-fineract/pull/313, this issue will be fixed. > Constitution Type Required Field > > > Key: FINERACT-243 > URL: https://issues.apache.org/jira/browse/FINERACT-243 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Dayna Harp >Assignee: Santosh Math >Priority: Critical > Labels: p2 > Fix For: 0.7.0-incubating > > > when creating a client with Legal Form "Entity", Constitution is a required > field. This does not need to be required. It is an optional field for those > financial institutions serving groups that have a constitution. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (FINERACT-243) Constitution Type Required Field
[ https://issues.apache.org/jira/browse/FINERACT-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-243: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > Constitution Type Required Field > > > Key: FINERACT-243 > URL: https://issues.apache.org/jira/browse/FINERACT-243 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Dayna Harp >Assignee: Shaik Nazeer Hussain >Priority: Critical > Labels: p2 > > when creating a client with Legal Form "Entity", Constitution is a required > field. This does not need to be required. It is an optional field for those > financial institutions serving groups that have a constitution. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FINERACT-379) Can not link a Saving account to during Group Loan Application
[ https://issues.apache.org/jira/browse/FINERACT-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-379. --- Resolution: Fixed Assignee: Santosh Math (was: Shaik Nazeer Hussain) Fix Version/s: 0.7.0-incubating > Can not link a Saving account to during Group Loan Application > -- > > Key: FINERACT-379 > URL: https://issues.apache.org/jira/browse/FINERACT-379 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Santosh Math > Labels: p1 > Fix For: 0.7.0-incubating > > > Reported by Lajeo at https://mifosforge.jira.com/browse/MIFOSX-1372 > and also: https://github.com/openMF/community-app/issues/1678 > You can not link a saving account during group loan application. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (FINERACT-379) Can not link a Saving account to during Group Loan Application
[ https://issues.apache.org/jira/browse/FINERACT-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-379: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > Can not link a Saving account to during Group Loan Application > -- > > Key: FINERACT-379 > URL: https://issues.apache.org/jira/browse/FINERACT-379 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain > Labels: p1 > Fix For: 0.7.0-incubating > > > Reported by Lajeo at https://mifosforge.jira.com/browse/MIFOSX-1372 > and also: https://github.com/openMF/community-app/issues/1678 > You can not link a saving account during group loan application. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (FINERACT-115) In Loan tranche details page if any tranche is added, "Tranche disbursement charge" is getting added twice"
[ https://issues.apache.org/jira/browse/FINERACT-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-115: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > In Loan tranche details page if any tranche is added, "Tranche disbursement > charge" is getting added twice" > --- > > Key: FINERACT-115 > URL: https://issues.apache.org/jira/browse/FINERACT-115 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Shaik Nazeer Hussain > Labels: p1 > Fix For: 0.7.0-incubating > > Attachments: Add trache details page.png > > > 1. Create a loan product with interest recalculation enabled, Tranche count > as 3 and Tranche disbursement charge attached as Flat-100. > 2. Submit new loan application for a client on 01 January 2016, with 2 > tranches attached as 5000 on 01 January 2016 and 2nd tranche 5000 on 01 March > 2016. > 3. Approve and disburse the first tranche. > 4. While disbursing the 2nd tranche change amount to 3000 and disburse the > 2nd tranche on 01 March 2016. > 5. Click on Loan tranche details page and add another tranche on 24 March > 2016 and amount as 2000. > 6. Click on repayment schedule in which the charge applied as 200. > > It should be 100. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FINERACT-115) In Loan tranche details page if any tranche is added, "Tranche disbursement charge" is getting added twice"
[ https://issues.apache.org/jira/browse/FINERACT-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-115: -- Fix Version/s: 0.7.0-incubating > In Loan tranche details page if any tranche is added, "Tranche disbursement > charge" is getting added twice" > --- > > Key: FINERACT-115 > URL: https://issues.apache.org/jira/browse/FINERACT-115 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Shaik Nazeer Hussain > Labels: p1 > Fix For: 0.7.0-incubating > > Attachments: Add trache details page.png > > > 1. Create a loan product with interest recalculation enabled, Tranche count > as 3 and Tranche disbursement charge attached as Flat-100. > 2. Submit new loan application for a client on 01 January 2016, with 2 > tranches attached as 5000 on 01 January 2016 and 2nd tranche 5000 on 01 March > 2016. > 3. Approve and disburse the first tranche. > 4. While disbursing the 2nd tranche change amount to 3000 and disburse the > 2nd tranche on 01 March 2016. > 5. Click on Loan tranche details page and add another tranche on 24 March > 2016 and amount as 2000. > 6. Click on repayment schedule in which the charge applied as 200. > > It should be 100. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (FINERACT-89) 1st tranche will appear twice in repayment schedule when disbursement date and first repayment date is on same date
[ https://issues.apache.org/jira/browse/FINERACT-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-89: Assignee: Shaik Nazeer Hussain (was: Satish S) > 1st tranche will appear twice in repayment schedule when disbursement date > and first repayment date is on same date > --- > > Key: FINERACT-89 > URL: https://issues.apache.org/jira/browse/FINERACT-89 > Project: Apache Fineract > Issue Type: Bug >Reporter: bharath c >Assignee: Shaik Nazeer Hussain > Labels: p1 > Attachments: issue.png > > > 1st tranche will appear twice in repayment schedule when disbursement date > and first repayment date is on same date > steps to produce:- > example > create a tranche loan > 1.expected disbursement date =04 January 2016 > 2. first repayment date = 04 January 2016 > see loan no- 308 in demo serveer -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FINERACT-406) Loan top up having same disbursement date of last transaction date of loan account is not allowing
[ https://issues.apache.org/jira/browse/FINERACT-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-406. --- Resolution: Fixed Assignee: Santosh Math (was: Shaik Nazeer Hussain) Fix Version/s: 0.7.0-incubating > Loan top up having same disbursement date of last transaction date of loan > account is not allowing > -- > > Key: FINERACT-406 > URL: https://issues.apache.org/jira/browse/FINERACT-406 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Santosh Math > Fix For: 0.7.0-incubating > > > Steps to reproduce: > 1. create two loan products one of which top up enabled. > 2. Disburse loan(non-top-up) on 01 January 2016. > 3. Make first repayment on schedule date(say, 01 February 2016) > 4. Create another loan account(top-up enabled) and check 'Is Topup Loan' and > select the previous account and set 'Disbursement on' date as 01 February > 2016(Last transaction date of previous loan account). > >Not allowing to submit and throwing the error: > "error.msg.loan.disbursal.date.should.be.after.last.transaction.date.of.loan.to.be.closed" > Loan topup should not be allowed for disbursement dates prior to the last > transaction date of the previous loan account but it should allow on same > date. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FINERACT-412) Add Share account in Global Search
[ https://issues.apache.org/jira/browse/FINERACT-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-412. --- Resolution: Fixed Assignee: Santosh Math (was: Markus Geiss) > Add Share account in Global Search > -- > > Key: FINERACT-412 > URL: https://issues.apache.org/jira/browse/FINERACT-412 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Reporter: Ippez Roberts >Assignee: Santosh Math > Labels: Volunteer, p3 > Fix For: 0.7.0-incubating > > > Currently its not possible to search for Share Account in community-app using > the global search -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FINERACT-399) Barebones and Sampledata sql files are broken
[ https://issues.apache.org/jira/browse/FINERACT-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-399. --- Resolution: Fixed Assignee: Santosh Math (was: Shaik Nazeer Hussain) > Barebones and Sampledata sql files are broken > - > > Key: FINERACT-399 > URL: https://issues.apache.org/jira/browse/FINERACT-399 > Project: Apache Fineract > Issue Type: Bug > Components: Migration Scripts >Reporter: Shaik Nazeer Hussain >Assignee: Santosh Math >Priority: Blocker > Labels: p1 > Fix For: 0.7.0-incubating > > > Barebones and Sampledata sql files are broken -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FINERACT-366) Issue With Creating RD account with 'Charge Time Type' Savings Activation
[ https://issues.apache.org/jira/browse/FINERACT-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-366. --- Resolution: Fixed Assignee: Santosh Math (was: Satish S) > Issue With Creating RD account with 'Charge Time Type' Savings Activation > -- > > Key: FINERACT-366 > URL: https://issues.apache.org/jira/browse/FINERACT-366 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Reporter: Santosh Math >Assignee: Santosh Math > Labels: p1 > Fix For: 0.7.0-incubating > > Attachments: activate.png, savact.png > > > Steps to reproduce: > > Create a Charge with following data set: >Charge Applies To: Savings & Deposits >Charge Time Type: Savings Activation >Charge Calculation: Flat >Amount: 50 > > Go to Client's page, Click on 'More' and click on 'New Recurring Deposit' > >select the RD product from drop-down menu and then enter the following > >data sets: > Recurring Deposit Amount: 5000 > Deposit Frequency: 1 month > Deposit period: 6 month > >Add the above created charge > >Submit it on 01 Jan 2015. > >Approve it and Activate it on 01 Feb 2015. > >In RD account page, go to Charges Tab and select the charge and click on > >'Pay Charge' > >Provide the date 01 January 2015 and 'Submit' it. > Then it throws the error, > "field is required > validation.msg.savingsaccount.transaction.not.valid.cannot.pay.activation.time.charge.is.automated" > Check the screenshot 'activate.png'. > Expected: When creating RD account with charge type 'Savings Activation', the > charge must be paid just after activation of RD account similar to Savings > Activation. check the screenshot savact.png -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (FINERACT-368) Make the release artifact into a maven artefact.
[ https://issues.apache.org/jira/browse/FINERACT-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-368. - Resolution: Later Assignee: Santosh Math (was: Markus Geiss) Currently there is no request from Fineract users to release binary artifacts as maven repo. So we can take it up later on requests. > Make the release artifact into a maven artefact. > > > Key: FINERACT-368 > URL: https://issues.apache.org/jira/browse/FINERACT-368 > Project: Apache Fineract > Issue Type: Wish >Reporter: Myrle Krantz >Assignee: Santosh Math >Priority: Minor > > Relevant e-mail: > 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.15#6346)
[jira] [Resolved] (FINERACT-402) Integrate PMD and Findbugs with Fineract
[ https://issues.apache.org/jira/browse/FINERACT-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-402. --- Resolution: Fixed Assignee: Santosh Math (was: Shaik Nazeer Hussain) > Integrate PMD and Findbugs with Fineract > > > Key: FINERACT-402 > URL: https://issues.apache.org/jira/browse/FINERACT-402 > Project: Apache Fineract > Issue Type: Improvement > Components: Build >Reporter: Shaik Nazeer Hussain >Assignee: Santosh Math > Fix For: 0.7.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (FINERACT-402) Integrate PMD and Findbugs with Fineract
Shaik Nazeer Hussain created FINERACT-402: - Summary: Integrate PMD and Findbugs with Fineract Key: FINERACT-402 URL: https://issues.apache.org/jira/browse/FINERACT-402 Project: Apache Fineract Issue Type: Improvement Components: Build Reporter: Shaik Nazeer Hussain Assignee: Shaik Nazeer Hussain Fix For: 0.7.0-incubating -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FINERACT-366) Issue With Creating RD account with 'Charge Time Type' Savings Activation
[ https://issues.apache.org/jira/browse/FINERACT-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-366: -- Fix Version/s: 0.7.0-incubating > Issue With Creating RD account with 'Charge Time Type' Savings Activation > -- > > Key: FINERACT-366 > URL: https://issues.apache.org/jira/browse/FINERACT-366 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Reporter: Santosh Math >Assignee: Satish S > Labels: p1 > Fix For: 0.7.0-incubating > > Attachments: activate.png, savact.png > > > Steps to reproduce: > > Create a Charge with following data set: >Charge Applies To: Savings & Deposits >Charge Time Type: Savings Activation >Charge Calculation: Flat >Amount: 50 > > Go to Client's page, Click on 'More' and click on 'New Recurring Deposit' > >select the RD product from drop-down menu and then enter the following > >data sets: > Recurring Deposit Amount: 5000 > Deposit Frequency: 1 month > Deposit period: 6 month > >Add the above created charge > >Submit it on 01 Jan 2015. > >Approve it and Activate it on 01 Feb 2015. > >In RD account page, go to Charges Tab and select the charge and click on > >'Pay Charge' > >Provide the date 01 January 2015 and 'Submit' it. > Then it throws the error, > "field is required > validation.msg.savingsaccount.transaction.not.valid.cannot.pay.activation.time.charge.is.automated" > Check the screenshot 'activate.png'. > Expected: When creating RD account with charge type 'Savings Activation', the > charge must be paid just after activation of RD account similar to Savings > Activation. check the screenshot savact.png -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FINERACT-365) The 'Transactions' tab showing wrong balance in RD account
[ https://issues.apache.org/jira/browse/FINERACT-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-365: -- Fix Version/s: 0.7.0-incubating > The 'Transactions' tab showing wrong balance in RD account > -- > > Key: FINERACT-365 > URL: https://issues.apache.org/jira/browse/FINERACT-365 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Reporter: Santosh Math >Assignee: Markus Geiss > Labels: p1 > Fix For: 0.7.0-incubating > > Attachments: transaction.png > > > "> Go to Client's page, Click on 'More' and click on 'New Recurring Deposit' > >select the RD product from drop-down menu and then enter the following > >data sets: > Recurring Deposit Amount: 5000 > Deposit Frequency: 1 month > Deposit Start Date: 01 January 2015 > Deposit Period: 6 months > >Submit , Approve and Activate it on 01 Jan 2015. > >Make deposits on 01 April 2015 > As first deposit is made on 01 April 2015, the balance in transaction should > show 5000. But the balance in transaction is showing 15000(Check the attached > file) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FINERACT-371) Make gradle callable from the top level directory.
[ https://issues.apache.org/jira/browse/FINERACT-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-371: -- Fix Version/s: 0.7.0-incubating > Make gradle callable from the top level directory. > -- > > Key: FINERACT-371 > URL: https://issues.apache.org/jira/browse/FINERACT-371 > Project: Apache Fineract > Issue Type: Wish >Reporter: Myrle Krantz >Assignee: Shaik Nazeer Hussain >Priority: Minor > Fix For: 0.7.0-incubating > > > Relevant e-mails: > 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.15#6346)
[jira] [Updated] (FINERACT-374) Add Gradle wrapper download location in readme file
[ https://issues.apache.org/jira/browse/FINERACT-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-374: -- Fix Version/s: 0.7.0-incubating > 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: Shaik Nazeer Hussain >Priority: Blocker > Fix For: 0.7.0-incubating > > > 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.15#6346)
[jira] [Assigned] (FINERACT-374) Add Gradle wrapper download location in readme file
[ https://issues.apache.org/jira/browse/FINERACT-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-374: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > 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: Shaik Nazeer Hussain >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.15#6346)
[jira] [Commented] (FINERACT-374) Add Gradle wrapper download location in readme file
[ https://issues.apache.org/jira/browse/FINERACT-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871242#comment-15871242 ] Shaik Nazeer Hussain commented on FINERACT-374: --- The gradle link mentioned in attached mail thread doesn't have cli package. So adding download location from Fineract github reposiory. - wget --no-check-certificate -P fineract-provider/gradle/wrapper https://github.com/apache/incubator-fineract/raw/develop/fineract-provider/gradle/wrapper/gradle-wrapper.jar (or) curl --insecure -L https://github.com/apache/incubator-fineract/raw/develop/fineract-provider/gradle/wrapper/gradle-wrapper.jar > fineract-provider/gradle/wrapper/gradle-wrapper.jar - > 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.15#6346)
[jira] [Resolved] (FINERACT-377) Reinvesting Recurring Deposit is taking present date in stead of maturity date
[ https://issues.apache.org/jira/browse/FINERACT-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-377. --- Resolution: Fixed Assignee: Santosh Math (was: Satish S) Fix Version/s: 0.7.0-incubating with PR https://github.com/apache/incubator-fineract/pull/289 issue is resolved. > Reinvesting Recurring Deposit is taking present date in stead of maturity date > -- > > Key: FINERACT-377 > URL: https://issues.apache.org/jira/browse/FINERACT-377 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Reporter: Santosh Math >Assignee: Santosh Math > Labels: p1 > Fix For: 0.7.0-incubating > > Attachments: reinv.png > > > 1. Create a Recurring deposit account for a client on 01 January 2016, term > is 3 months repaid every month -> Approve and disburse on same date. > 2. Make Deposits on 01 Jan, 01 Feb, and 01 March > 3. Also run the scheduler job "Update Deposit Accounts Maturity details" -> > Navigate back to the Recurring deposit account page -> Click on Close button. > 4. In Close account page, select the date as 01 April 2015(maturity date) and > in action drop-down select Reinvest as option -> Click on 'Submit' button. > After clicking 'Submit' button, the previous RD account gets closed and new > RD account gets created with deposit amount = closing amount of previous RD > account. The reinvesting date should be 01 April 2015, but the application is > taking present date as 'Reinvesting Date'. Check the screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (FINERACT-377) Reinvesting Recurring Deposit is taking present date in stead of maturity date
[ https://issues.apache.org/jira/browse/FINERACT-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-377: - Assignee: Satish S (was: Shaik Nazeer Hussain) > Reinvesting Recurring Deposit is taking present date in stead of maturity date > -- > > Key: FINERACT-377 > URL: https://issues.apache.org/jira/browse/FINERACT-377 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Reporter: Santosh Math >Assignee: Satish S > Labels: p1 > Attachments: reinv.png > > > 1. Create a Recurring deposit account for a client on 01 January 2016, term > is 3 months repaid every month -> Approve and disburse on same date. > 2. Make Deposits on 01 Jan, 01 Feb, and 01 March > 3. Also run the scheduler job "Update Deposit Accounts Maturity details" -> > Navigate back to the Recurring deposit account page -> Click on Close button. > 4. In Close account page, select the date as 01 April 2015(maturity date) and > in action drop-down select Reinvest as option -> Click on 'Submit' button. > After clicking 'Submit' button, the previous RD account gets closed and new > RD account gets created with deposit amount = closing amount of previous RD > account. The reinvesting date should be 01 April 2015, but the application is > taking present date as 'Reinvesting Date'. Check the screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FINERACT-312) For Loan with interest recalculation periodic accrual with respect to current date is not getting modified after repayment in Transaction page
[ https://issues.apache.org/jira/browse/FINERACT-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-312. --- Resolution: Fixed Fix Version/s: 0.7.0-incubating With Below PR issue is resolved. https://github.com/apache/incubator-fineract/pull/286 > For Loan with interest recalculation periodic accrual with respect to current > date is not getting modified after repayment in Transaction page > -- > > Key: FINERACT-312 > URL: https://issues.apache.org/jira/browse/FINERACT-312 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain > Labels: p1 > Fix For: 0.7.0-incubating > > Attachments: 35.png, 36.png, 37.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2119 > Original Description: > 1. Create a loan product with following datasets: > Principal: 1, no. of Installments: 12, repaid every 1 month, Nominal > interest rate: 1%pm,Amortization: Equal installments, Interest Method: > Declining Balance, Interest Calculation Period: Same as repayment > period,Repayment Strategy:RBI (India),Recalculate Interest: Yes,Advance > payments adjustment type: Reduce number of installments, Pre-closure interest > calculation rule: Calculate till pre closure date, Interest recalculation > compounding on:None, Frequency for recalculate Outstanding Principal: Same as > repayment period, with accounting enabled for periodic accrual. > 2. Submit new loan application for a client on 01 March 2015 approve and > disburse on same date. > 3. Click on Admin -> system -> Scheduler job - run scheduler job "Add > Periodic Accrual Transactions". > 4. Navigate back to Transactions page and verify the accrued interest as on > current date. > 5. Make first repayment on exact due date then verify the transaction page > the accrued interest as on current date is not modified. > > The accrued interest as on current date is not getting modified even after > > multiple repayments. > Please refer the screen shot attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (FINERACT-312) For Loan with interest recalculation periodic accrual with respect to current date is not getting modified after repayment in Transaction page
[ https://issues.apache.org/jira/browse/FINERACT-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-312: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > For Loan with interest recalculation periodic accrual with respect to current > date is not getting modified after repayment in Transaction page > -- > > Key: FINERACT-312 > URL: https://issues.apache.org/jira/browse/FINERACT-312 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain > Labels: p1 > Attachments: 35.png, 36.png, 37.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2119 > Original Description: > 1. Create a loan product with following datasets: > Principal: 1, no. of Installments: 12, repaid every 1 month, Nominal > interest rate: 1%pm,Amortization: Equal installments, Interest Method: > Declining Balance, Interest Calculation Period: Same as repayment > period,Repayment Strategy:RBI (India),Recalculate Interest: Yes,Advance > payments adjustment type: Reduce number of installments, Pre-closure interest > calculation rule: Calculate till pre closure date, Interest recalculation > compounding on:None, Frequency for recalculate Outstanding Principal: Same as > repayment period, with accounting enabled for periodic accrual. > 2. Submit new loan application for a client on 01 March 2015 approve and > disburse on same date. > 3. Click on Admin -> system -> Scheduler job - run scheduler job "Add > Periodic Accrual Transactions". > 4. Navigate back to Transactions page and verify the accrued interest as on > current date. > 5. Make first repayment on exact due date then verify the transaction page > the accrued interest as on current date is not modified. > > The accrued interest as on current date is not getting modified even after > > multiple repayments. > Please refer the screen shot attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (FINERACT-371) Make gradle callable from the top level directory.
[ https://issues.apache.org/jira/browse/FINERACT-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-371: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > Make gradle callable from the top level directory. > -- > > Key: FINERACT-371 > URL: https://issues.apache.org/jira/browse/FINERACT-371 > Project: Apache Fineract > Issue Type: Wish >Reporter: Myrle Krantz >Assignee: Shaik Nazeer Hussain >Priority: Minor > > Relevant e-mails: > 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.15#6346)
[jira] [Updated] (FINERACT-399) Barebones and Sampledata sql files are broken
[ https://issues.apache.org/jira/browse/FINERACT-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-399: -- Labels: p1 (was: ) > Barebones and Sampledata sql files are broken > - > > Key: FINERACT-399 > URL: https://issues.apache.org/jira/browse/FINERACT-399 > Project: Apache Fineract > Issue Type: Bug > Components: Migration Scripts >Reporter: Shaik Nazeer Hussain >Assignee: Shaik Nazeer Hussain >Priority: Blocker > Labels: p1 > Fix For: 0.7.0-incubating > > > Barebones and Sampledata sql files are broken -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FINERACT-234) Can't process bulk JLG loan application [MIFOSX-2137]
[ https://issues.apache.org/jira/browse/FINERACT-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-234. --- Resolution: Resolved Fix Version/s: 0.7.0-incubating With below PR(s), issue is resolved. https://github.com/openMF/community-app/pull/1832 https://github.com/apache/incubator-fineract/pull/285 > Can't process bulk JLG loan application [MIFOSX-2137] > - > > Key: FINERACT-234 > URL: https://issues.apache.org/jira/browse/FINERACT-234 > Project: Apache Fineract > Issue Type: Bug >Reporter: Edward Cable >Assignee: Shaik Nazeer Hussain > Labels: p1 > Fix For: 0.7.0-incubating > > > Moved over from https://mifosforge.jira.com/browse/MIFOSX-2137 > I still am unable to save new bulk JLG loan applications even when the > meeting frequency matches so it seems like this is still not working. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FINERACT-159) Not able to disburse the loan after deleting the first three installments in variable installments
[ https://issues.apache.org/jira/browse/FINERACT-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-159. --- Resolution: Fixed Assignee: Shaik Nazeer Hussain (was: Markus Geiss) Fix Version/s: 0.7.0-incubating > Not able to disburse the loan after deleting the first three installments in > variable installments > -- > > Key: FINERACT-159 > URL: https://issues.apache.org/jira/browse/FINERACT-159 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: subramanyasn >Assignee: Shaik Nazeer Hussain > Labels: confirm, p2 > Fix For: 0.7.0-incubating > > Attachments: After disbursement1.png > > > 1. Create loan product with following datasets > Repayment Strategy: Overdue/Due Fee/Int,Principal > Repayments: 12 every 1 Months on > Amortization: Equal installments > Interest: 12 per annum (1% Per month) - Declining Balance > Grace: On Principal Payment > Grace: On Interest Payment > Interest Calculation Period: Daily > Interest Type: Declining Balance > Recalculate Interest: Yes > Days in year: Actual > Days in month: Actual > Interest recalculation compounding on: None > Advance payments adjustment type: Reduce EMI amount > Frequency for recalculate Outstanding Principal: Daily. > 2. Submit new loan application for a client on 01 January 2016, and amount as > 1. > 3.Click on more and click on edit repayment schedule. and delete first 3 > repayments. > 4. Approve and click on disburse the loan, in loan disbursement page enter > valid inputs and click on submit button. > > Navigated page doesnot contain any loan information rather displays with > > out any entries. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (FINERACT-151) If the disbursement date is modified during loan disbursement the first repayment schedule generated is not proper
[ https://issues.apache.org/jira/browse/FINERACT-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-151. - Resolution: Fixed Fix Version/s: 0.7.0-incubating Tested by Santosh on 116.12.01.RELEASE and it is working as expected. > If the disbursement date is modified during loan disbursement the first > repayment schedule generated is not proper > -- > > Key: FINERACT-151 > URL: https://issues.apache.org/jira/browse/FINERACT-151 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: subramanyasn >Assignee: Shaik Nazeer Hussain >Priority: Critical > Labels: confirm, p1 > Fix For: 0.7.0-incubating > > Attachments: Mifos X Client 2016-05-06 09-26-49.png > > > 1. Create a loan product with interest recalculation enabled. > 2. Submit new loan application for a client on 01 January 2016, and expected > disbursement date as 01 January 2016. > 3. Approve on 01 January 2016. > 4. While disbursing the modify the date as 06 May 2016 > > The repayment schedule date generated is from 01 February 2016. > It should start from 06 June 2016. > > -ve amounts getting displayed in the repayment schedule under balance loan > > column. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (FINERACT-151) If the disbursement date is modified during loan disbursement the first repayment schedule generated is not proper
[ https://issues.apache.org/jira/browse/FINERACT-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-151: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > If the disbursement date is modified during loan disbursement the first > repayment schedule generated is not proper > -- > > Key: FINERACT-151 > URL: https://issues.apache.org/jira/browse/FINERACT-151 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: subramanyasn >Assignee: Shaik Nazeer Hussain >Priority: Critical > Labels: confirm, p1 > Attachments: Mifos X Client 2016-05-06 09-26-49.png > > > 1. Create a loan product with interest recalculation enabled. > 2. Submit new loan application for a client on 01 January 2016, and expected > disbursement date as 01 January 2016. > 3. Approve on 01 January 2016. > 4. While disbursing the modify the date as 06 May 2016 > > The repayment schedule date generated is from 01 February 2016. > It should start from 06 June 2016. > > -ve amounts getting displayed in the repayment schedule under balance loan > > column. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FINERACT-311) Issue With 'Payment Due On Non Working Days'
[ https://issues.apache.org/jira/browse/FINERACT-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-311: -- Affects Version/s: 0.7.0-incubating > Issue With 'Payment Due On Non Working Days' > - > > Key: FINERACT-311 > URL: https://issues.apache.org/jira/browse/FINERACT-311 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 0.7.0-incubating >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain > Labels: p1 > Attachments: paymentDueOnNonWorkingDay.png > > > 1. Go To Admin>>Organization and click on Working Days > 2. Un-check Sunday. > 3. Change 'Payment Due On Non Working Days' from 'same day' to 'Move to Next > Working Day' or any other parameters. > 4. Click on Submit button. > 5. Go Back to Admin>>Organization>>Working Days > You can observe that 'Payment Due On Non Working Days' remains as 'same > day' though we changed it to other parameters like 'Move to Next Working Day' > , etc. > Note: This issue doesn't appear every time but still exists. You can check it > by frequently changing 'Payment Due On Non Working Days' -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (FINERACT-316) Should allow to add loan transactions after Account Closure date
[ https://issues.apache.org/jira/browse/FINERACT-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain reassigned FINERACT-316: - Assignee: Shaik Nazeer Hussain (was: Markus Geiss) > Should allow to add loan transactions after Account Closure date > > > Key: FINERACT-316 > URL: https://issues.apache.org/jira/browse/FINERACT-316 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain > Labels: confirm, p1 > Attachments: 111.png, 112.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2241 > Original Description: > 1. Disburse the loan on 05 August 2014 and make repayment till 18 August 2015. > 2. Create Account Closing entries on 02 September 2015 and then make > repayment which is due on 01 September 2015. > > Not allowing to make repayment displayed error message as "Accounting has > > been closed for this branch as of `2015-09-02`." - Working as expected. > 3. Make repayment on 03 September 2015 - it should allow to make repayment > but it is not allowing there also. > 4. Make repayment on current system date - then it is allowing to make > repayment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FINERACT-310) Editing 'Product Mix' Not Working
[ https://issues.apache.org/jira/browse/FINERACT-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-310: -- Fix Version/s: 0.7.0-incubating > Editing 'Product Mix' Not Working > > > Key: FINERACT-310 > URL: https://issues.apache.org/jira/browse/FINERACT-310 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss > Fix For: 0.7.0-incubating > > Attachments: EditProductMix.png > > > 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. > Check the screenshot attached with this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (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 updated FINERACT-364: -- Fix Version/s: 0.7.0-incubating > 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 > Fix For: 0.7.0-incubating > > 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.15#6346)
[jira] [Updated] (FINERACT-126) Not able to Submit the loan application if multi tranche is added and the "Expected disbursement on" field is left blank displays internal server error
[ https://issues.apache.org/jira/browse/FINERACT-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain updated FINERACT-126: -- Fix Version/s: 0.7.0-incubating > Not able to Submit the loan application if multi tranche is added and the > "Expected disbursement on" field is left blank displays internal server error > --- > > Key: FINERACT-126 > URL: https://issues.apache.org/jira/browse/FINERACT-126 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Shaik Nazeer Hussain > Labels: p1 > Fix For: 0.7.0-incubating > > Attachments: null point exception2.png, null point exception..png > > > 1. Create a simple loan product with multi tranche. > 2. Click on Clients -> Client -> New Loan -> Select the above product -> > Enter submitted date as 01 March 2016 and Expected disbursement date as same. > Select 2 tranches and for the first tranche enter the valid inputs and for > the second tranche add only amount and click on submit button. > > Displayed Internal server error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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: -- Fix Version/s: 0.7.0-incubating > 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: Shaik Nazeer Hussain > Labels: p1 > Fix For: 0.7.0-incubating > > > 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.15#6346)
[jira] [Closed] (FINERACT-287) Unnecessary reversal of transactions when making 2 recovery payments on same day
[ https://issues.apache.org/jira/browse/FINERACT-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-287. - Resolution: Fixed PR has been sent and merged (According Sander comments). So resolving this issue. > Unnecessary reversal of transactions when making 2 recovery payments on same > day > > > Key: FINERACT-287 > URL: https://issues.apache.org/jira/browse/FINERACT-287 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss > Labels: confirm, p1 > > Reported by Sander at https://mifosforge.jira.com/browse/MIFOSX-1637 > Original Description: > When you make 2 recovery payments into the same (written-off) loan on the > same day, the second payment will (unnecessarily) reverse the first one and > then book it again. This is not necessary and clutters up the journal > entries. This might also apply to other actions, such as regular repayments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-301) Force password reset days is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-301. - Resolution: Fixed Assignee: Shaik Nazeer Hussain (was: Markus Geiss) Santosh tested on 16.12.01.RELEASE and it is working as expected. > Force password reset days is not working as expected > > > Key: FINERACT-301 > URL: https://issues.apache.org/jira/browse/FINERACT-301 > Project: Apache Fineract > Issue Type: Bug >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain > Labels: confirm, p2 > > Reported by Sangamesh at https://mifosforge.jira.com/browse/MIFOSX-2022 > Original Description: > Existing: > On enabling "force-password-reset-days" in configuration, it takes the > default value(days) which is 0(zero). If the user logs out and tries to > login, it wont allow user to login. This was raised by Frank from "Jambo > capital Initiative". > Expected: > Should not allow to change from enable to disable if the value is 0(zero). If > it should be allowed, then it should allow to change the password immediately > at the time of login. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FINERACT-313) For Multiple tranche Loans with Equal Principal Payments after submitting the loan application Principal due is not calculating properly
[ https://issues.apache.org/jira/browse/FINERACT-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain closed FINERACT-313. - Resolution: Cannot Reproduce Assignee: subramanyasn (was: Markus Geiss) Santosh tested on 16.12.01.RELEASE it is not reproducible. > For Multiple tranche Loans with Equal Principal Payments after submitting the > loan application Principal due is not calculating properly > > > Key: FINERACT-313 > URL: https://issues.apache.org/jira/browse/FINERACT-313 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: subramanyasn > Labels: confirm, p1 > Attachments: 42.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2130 > Original Description: > 1. Create a Loan product with following datasets > Repayment Strategy:RBI (India) > Repayments:12 every 1 Months > Amortization:Equal principal payments > Interest:12 per annum (1% Per month):Declining Balance > Interest Calculation Period:Daily > Interest Type:Declining Balance > Recalculate Interest Yes > Days in year: Actual > Days in month: Actual > Interest recalculation compounding on:None > Advance payments adjustment type:Reduce number of installments > Frequency for recalculate Outstanding Principal: Every -1 days > Max Tranche Count:2, > 2.Submit new loan application for a client on 01 January 2015 with first > tranche on same date and 2nd Tranche on 01 March 2015, each with 5000 amount. > > For 01 February 2015 and 01 March 2015 the principal due should be 416.67 > > (ie 5000/12). and From 01 April2015 to 01 January 2016 principal due should > > be 916.66 (ie 9166.6/10). > But here it is calculating differently as a result for the last installment > principal due is more. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-313) For Multiple tranche Loans with Equal Principal Payments after submitting the loan application Principal due is not calculating properly
[ https://issues.apache.org/jira/browse/FINERACT-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15834087#comment-15834087 ] Shaik Nazeer Hussain commented on FINERACT-313: --- [~santoshmath] Can you reproduce this issue > For Multiple tranche Loans with Equal Principal Payments after submitting the > loan application Principal due is not calculating properly > > > Key: FINERACT-313 > URL: https://issues.apache.org/jira/browse/FINERACT-313 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss > Labels: confirm, p1 > Attachments: 42.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2130 > Original Description: > 1. Create a Loan product with following datasets > Repayment Strategy:RBI (India) > Repayments:12 every 1 Months > Amortization:Equal principal payments > Interest:12 per annum (1% Per month):Declining Balance > Interest Calculation Period:Daily > Interest Type:Declining Balance > Recalculate Interest Yes > Days in year: Actual > Days in month: Actual > Interest recalculation compounding on:None > Advance payments adjustment type:Reduce number of installments > Frequency for recalculate Outstanding Principal: Every -1 days > Max Tranche Count:2, > 2.Submit new loan application for a client on 01 January 2015 with first > tranche on same date and 2nd Tranche on 01 March 2015, each with 5000 amount. > > For 01 February 2015 and 01 March 2015 the principal due should be 416.67 > > (ie 5000/12). and From 01 April2015 to 01 January 2016 principal due should > > be 916.66 (ie 9166.6/10). > But here it is calculating differently as a result for the last installment > principal due is more. -- 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)
[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] [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] [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] [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=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-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] [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-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] [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=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-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-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-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] [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=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] [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] [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] [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] [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=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] [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=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-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=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-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=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] [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=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] [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-380) S3 permission issue -- add system property
[ https://issues.apache.org/jira/browse/FINERACT-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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] [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] [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] [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] [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] [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=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] [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] [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] [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] [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] [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-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-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] [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] [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] [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] [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] [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-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] [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] [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-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-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-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-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-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-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-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] [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-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-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] [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=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)
