[jira] [Commented] (FINERACT-423) Compilation fails due to missing licence header in some files
[ https://issues.apache.org/jira/browse/FINERACT-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974388#comment-15974388 ] ASF GitHub Bot commented on FINERACT-423: - GitHub user raj140916 opened a pull request: https://github.com/apache/incubator-fineract/pull/334 FIX FINERACT-423: Compilation fails due to missing licence header in … …some files You can merge this pull request into a Git repository by running: $ git pull https://github.com/raj140916/incubator-fineract develop Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/334.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #334 commit 187faf5153d36af6ce2dbdfd441046f6de3c5754 Author: unknown Date: 2017-04-19T09:26:56Z FIX FINERACT-423: Compilation fails due to missing licence header in some files > Compilation fails due to missing licence header in some files > --- > > Key: FINERACT-423 > URL: https://issues.apache.org/jira/browse/FINERACT-423 > Project: Apache Fineract > Issue Type: Task >Reporter: Raju Metgiri >Assignee: Markus Geiss >Priority: Trivial > Labels: p3 > Attachments: Screen Shot 2017-04-09 at 15.59.00.png > > Original Estimate: 1h > Remaining Estimate: 1h > > if a developer does git clone of the current repo and starts a build, the > build will fail. This caused due to the task "licenseMain" as some of the > files are missing licence headers. I would like to correct this and submit > the changes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-389) Arrange the accounts that fall under one account type in order of their GL codes
[ https://issues.apache.org/jira/browse/FINERACT-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963303#comment-15963303 ] ASF GitHub Bot commented on FINERACT-389: - GitHub user ThisuraThejith opened a pull request: https://github.com/apache/incubator-fineract/pull/330 Fix FINERACT-389 ordere by gl_code added to sql query in retrieveAllGLAccounts You can merge this pull request into a Git repository by running: $ git pull https://github.com/ThisuraThejith/incubator-fineract FINERACT-389 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/330.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #330 commit 1b438021421f6f64414cc5889735987a622f1f3a Author: ThisuraThejith Date: 2017-04-10T18:32:02Z ordere by gl_code added to sql query in retrieveAllGLAccounts > Arrange the accounts that fall under one account type in order of their GL > codes > > > Key: FINERACT-389 > URL: https://issues.apache.org/jira/browse/FINERACT-389 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: p2 > > Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2825 > Original Description: > Accounts in chart of accounts are arranged by their account type but those > accounts in the specific account type are randomly arranged. > I was recommending for the accounts in the same account type to be arranged > by their GL code. Since the relating accounts will be under one header and so > their GL codes will be following each other and bring presentable > arrangement. (accounts in the same header, their GL codes should have > relation) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-243) Constitution Type Required Field
[ https://issues.apache.org/jira/browse/FINERACT-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961953#comment-15961953 ] ASF GitHub Bot commented on FINERACT-243: - Github user tonic889 commented on the issue: https://github.com/apache/incubator-fineract/pull/315 So what is the right way to avoid this duplication of effort again in the future? > 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: 1.0.0 > > > 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] [Commented] (FINERACT-78) Specified due date percentage charge calculation uses loan principal amount instead of installment principal amount
[ https://issues.apache.org/jira/browse/FINERACT-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948866#comment-15948866 ] ASF GitHub Bot commented on FINERACT-78: Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/324 > Specified due date percentage charge calculation uses loan principal amount > instead of installment principal amount > --- > > Key: FINERACT-78 > URL: https://issues.apache.org/jira/browse/FINERACT-78 > Project: Apache Fineract > Issue Type: Bug >Reporter: Emmanuel Nnaa >Assignee: Markus Geiss > Labels: p1 > Attachments: Sp. Charge 1.png, Sp. Charge 2.png, Sp. Charge 3.png, > Sp. Charge 4.png > > > Specified due date percentage charge calculation uses loan principal amount > instead of installment principal amount. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-249) PortfolioProductType.SAVING and PortfolioProductType.CLIENT have the same value
[
https://issues.apache.org/jira/browse/FINERACT-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945039#comment-15945039
]
ASF GitHub Bot commented on FINERACT-249:
-
GitHub user nazeer1100126 opened a pull request:
https://github.com/apache/incubator-fineract/pull/325
FINERACT-249 : PortfolioProductType.SAVING and PortfolioProductType.CLIENT
have the same value
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-249
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-fineract/pull/325.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #325
commit ffd4b6a37f529a8dc04de1e57cf9e6220d0f2ac6
Author: nazeer1100126
Date: 2017-03-28T12:19:24Z
FINERACT-249 : PortfolioProductType.SAVING and PortfolioProductType.CLIENT
have the same value
> PortfolioProductType.SAVING and PortfolioProductType.CLIENT have the same
> value
> ---
>
> Key: FINERACT-249
> URL: https://issues.apache.org/jira/browse/FINERACT-249
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Emmanuel Nnaa
>Assignee: Markus Geiss
> Labels: Volunteer, p1
>
> PortfolioProductType.SAVING and PortfolioProductType.CLIENT have the same
> value.
> {code}
> LOAN(1, "productType.loan"), SAVING(2, "productType.saving"), CLIENT(2,
> "productType.client"), PROVISIONING(3,
> "productType.provisioning"), SHARES(4, "productType.shares");
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FINERACT-78) Specified due date percentage charge calculation uses loan principal amount instead of installment principal amount
[ https://issues.apache.org/jira/browse/FINERACT-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944754#comment-15944754 ] ASF GitHub Bot commented on FINERACT-78: GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/324 FINERACT-78 : Specified due date percentage charge calculation uses loan principal amount instead of installment principal amount You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-78 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/324.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #324 commit 8baf9f4cd0de899ae015f1994e17b1b0e8b39641 Author: nazeer1100126 Date: 2017-03-27T12:04:20Z FINERACT-78 : Specified due date percentage charge calculation uses loan principal amount instead of installment principal amount > Specified due date percentage charge calculation uses loan principal amount > instead of installment principal amount > --- > > Key: FINERACT-78 > URL: https://issues.apache.org/jira/browse/FINERACT-78 > Project: Apache Fineract > Issue Type: Bug >Reporter: Emmanuel Nnaa >Assignee: Markus Geiss > Labels: p1 > Attachments: Sp. Charge 1.png, Sp. Charge 2.png, Sp. Charge 3.png, > Sp. Charge 4.png > > > Specified due date percentage charge calculation uses loan principal amount > instead of installment principal amount. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-360) Individual Collection Sheet is not considering 'Installment Fee' during payment
[ https://issues.apache.org/jira/browse/FINERACT-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943213#comment-15943213 ] ASF GitHub Bot commented on FINERACT-360: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/323 > Individual Collection Sheet is not considering 'Installment Fee' during > payment > --- > > Key: FINERACT-360 > URL: https://issues.apache.org/jira/browse/FINERACT-360 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss > Labels: p1 > Attachments: 1.png > > > 1. Create a client under Head Office. > 2. Create a loan account for a client(with Installment Fee and staff > attached) and weekly repayment. Disburse it on 02 January 2015. > 3. Go to Individual Collection Sheet and furnish following details: > Branch Office : Head Office > Repayment Date: 09 January 2015 > Staff: *Give the name of the staff assigned to loan account* > 4. Click on Collection Sheet. > >> When we observe collection sheet, the amount is reflecting > >> Principal+Interest but not installment fee. > >>If we submit it, in repayment schedule, the Installment Fee is shown as > >>'Outstanding' Balance. > If we consider 'Specified Due Date' Fee in stead of 'Installment Fee', the > individual sheet is working fine. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-360) Individual Collection Sheet is not considering 'Installment Fee' during payment
[ https://issues.apache.org/jira/browse/FINERACT-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942991#comment-15942991 ] ASF GitHub Bot commented on FINERACT-360: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/323 FINERACT-360 : Individual Collection Sheet is not considering Installment Fee during payment You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-360 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/323.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #323 commit 254d2597053bac316d89ab7e3e0f83dc1d39d7f0 Author: nazeer1100126 Date: 2017-03-27T10:00:11Z FINERACT-360 : Individual Collection Sheet is not considering Installment Fee during payment > Individual Collection Sheet is not considering 'Installment Fee' during > payment > --- > > Key: FINERACT-360 > URL: https://issues.apache.org/jira/browse/FINERACT-360 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss > Labels: p1 > Attachments: 1.png > > > 1. Create a client under Head Office. > 2. Create a loan account for a client(with Installment Fee and staff > attached) and weekly repayment. Disburse it on 02 January 2015. > 3. Go to Individual Collection Sheet and furnish following details: > Branch Office : Head Office > Repayment Date: 09 January 2015 > Staff: *Give the name of the staff assigned to loan account* > 4. Click on Collection Sheet. > >> When we observe collection sheet, the amount is reflecting > >> Principal+Interest but not installment fee. > >>If we submit it, in repayment schedule, the Installment Fee is shown as > >>'Outstanding' Balance. > If we consider 'Specified Due Date' Fee in stead of 'Installment Fee', the > individual sheet is working fine. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-303) "% Loan Amount + Interest or %Amount" if collected as disbursement fees it is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940218#comment-15940218 ] ASF GitHub Bot commented on FINERACT-303: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/322 > "% Loan Amount + Interest or %Amount" if collected as disbursement fees it is > not working as expected > - > > Key: FINERACT-303 > URL: https://issues.apache.org/jira/browse/FINERACT-303 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Santosh Math > Labels: p1 > Fix For: 0.7.0-incubating > > Attachments: Scr-689.png, Scr-690.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2056 > Original Description: > 1. Create a charge of 1% as Disbursement fees as "% Loan Amount + Interest or > % Approved Amount". > 2. Create a loan product with 2 tranche and amount as 1 and add above > mentioned charge to it. > 3. Create a client and submit new loan application with above mentioned loan > product on 01 May 2015 with 2 tranches added > first tranche on 01 May 2015 and amount as 5000. > Second tranche on 15 May 2015 and amount as 5000. > 4. Approve and disburse first tranche on 01 May 2015. > > Since charge applied on %loan amount total+interest, it should collect > > charge as 109.39, > but it is collecting 59.39. > 5. After making the second disbursement on 15 May 2015 it is getting > collected 109.39, > but in charges it is displaying as 50 outstanding. > 6. If the disbursement amount is modified during loan approval then in > repayment schedule the charge is not getting updated. (eg. submit loan > application with first tranch 5000 and second tranch 5000, during approval > change amount as 4000 and 4000 for first and second tranch. then %amount > charge is displaying with respect to first tranche amount only.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-303) "% Loan Amount + Interest or %Amount" if collected as disbursement fees it is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940209#comment-15940209 ] ASF GitHub Bot commented on FINERACT-303: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/322 FINERACT-303 - % Loan Amount + Interest or %Amount if collected as disbursement fees it is not working as expected You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-303 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/322.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #322 commit f59dacbfc8a04031cd9521ed1c23bc57245d2c26 Author: nazeer1100126 Date: 2017-03-24T11:50:40Z FINERACT-303 - % Loan Amount + Interest or %Amount if collected as disbursement fees it is not working as expected > "% Loan Amount + Interest or %Amount" if collected as disbursement fees it is > not working as expected > - > > Key: FINERACT-303 > URL: https://issues.apache.org/jira/browse/FINERACT-303 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss > Labels: p1 > Attachments: Scr-689.png, Scr-690.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2056 > Original Description: > 1. Create a charge of 1% as Disbursement fees as "% Loan Amount + Interest or > % Approved Amount". > 2. Create a loan product with 2 tranche and amount as 1 and add above > mentioned charge to it. > 3. Create a client and submit new loan application with above mentioned loan > product on 01 May 2015 with 2 tranches added > first tranche on 01 May 2015 and amount as 5000. > Second tranche on 15 May 2015 and amount as 5000. > 4. Approve and disburse first tranche on 01 May 2015. > > Since charge applied on %loan amount total+interest, it should collect > > charge as 109.39, > but it is collecting 59.39. > 5. After making the second disbursement on 15 May 2015 it is getting > collected 109.39, > but in charges it is displaying as 50 outstanding. > 6. If the disbursement amount is modified during loan approval then in > repayment schedule the charge is not getting updated. (eg. submit loan > application with first tranch 5000 and second tranch 5000, during approval > change amount as 4000 and 4000 for first and second tranch. then %amount > charge is displaying with respect to first tranche amount only.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-270) Unable to waive all Loan charges
[ https://issues.apache.org/jira/browse/FINERACT-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938279#comment-15938279 ] ASF GitHub Bot commented on FINERACT-270: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/321 > Unable to waive all Loan charges > > > Key: FINERACT-270 > URL: https://issues.apache.org/jira/browse/FINERACT-270 > Project: Apache Fineract > Issue Type: Bug > Components: Loan > Environment: Reproducible on demo.openmf.org. > Create new client Loan with FINERACT_7-MIFOS_2495 >Reporter: Abdul Aziz Ali >Assignee: Markus Geiss >Priority: Trivial > Labels: p1 > Attachments: pruned_catalina.log > > > Create Loan and Charge similar to FINERACT-7 > > (verbatim from FINERACT-7) > 1. Create Installment fee for a loan as 100-Flat-Regular. > 2. Create loan product with following datasets and attache above installment > fee to that. > Terms vary based on loan cycle : FALSE > Principal:10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max > Repay Every: 1 Months > Nominal Interest Rate:1 ( Min: , Max Per month > Minimum days between disbursal and first repayment date > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Repayment StrategyOverdue/Due Fee/Int,Principal > Account moves out of NPA only after all arrears have been cleared?No > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Allow fixing of the installment amountNo > Interest Recalculation > 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 Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01-Jan-15 > Is Arrears recognization based on original schedule:No. > 3. Submit new loan application on 01 October 2015. Approve and disburse loan > on same date. > 4. Click on waive charge and select for 1st repayment. > 5. Repayment schedule generated after waive charge is not proper > >Waive charge is happening not for first installment instead for other > >installment it is happening. > 6. For first repayment the due is getting displayed. > > 7. Keep waiving all charges until the last one > The last one does not get waived nor does the Exception get raised to the UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-270) Unable to waive all Loan charges
[ https://issues.apache.org/jira/browse/FINERACT-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938264#comment-15938264 ] ASF GitHub Bot commented on FINERACT-270: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/321 FINERACT-270 : Unable to waive all Loan charges You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-270 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/321.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #321 commit 935d6146c00e5f13cc53baf44ba78800c3b3796b Author: nazeer1100126 Date: 2017-03-21T12:20:32Z FINERACT-270 : Unable to waive all Loan charges > Unable to waive all Loan charges > > > Key: FINERACT-270 > URL: https://issues.apache.org/jira/browse/FINERACT-270 > Project: Apache Fineract > Issue Type: Bug > Components: Loan > Environment: Reproducible on demo.openmf.org. > Create new client Loan with FINERACT_7-MIFOS_2495 >Reporter: Abdul Aziz Ali >Assignee: Markus Geiss >Priority: Trivial > Labels: p1 > Attachments: pruned_catalina.log > > > Create Loan and Charge similar to FINERACT-7 > > (verbatim from FINERACT-7) > 1. Create Installment fee for a loan as 100-Flat-Regular. > 2. Create loan product with following datasets and attache above installment > fee to that. > Terms vary based on loan cycle : FALSE > Principal:10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max > Repay Every: 1 Months > Nominal Interest Rate:1 ( Min: , Max Per month > Minimum days between disbursal and first repayment date > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Repayment StrategyOverdue/Due Fee/Int,Principal > Account moves out of NPA only after all arrears have been cleared?No > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Allow fixing of the installment amountNo > Interest Recalculation > 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 Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01-Jan-15 > Is Arrears recognization based on original schedule:No. > 3. Submit new loan application on 01 October 2015. Approve and disburse loan > on same date. > 4. Click on waive charge and select for 1st repayment. > 5. Repayment schedule generated after waive charge is not proper > >Waive charge is happening not for first installment instead for other > >installment it is happening. > 6. For first repayment the due is getting displayed. > > 7. Keep waiving all charges until the last one > The last one does not get waived nor does the Exception get raised to the UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-418) Penalties should be calculated until yesterday
[ https://issues.apache.org/jira/browse/FINERACT-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935817#comment-15935817 ] ASF GitHub Bot commented on FINERACT-418: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/319 > Penalties should be calculated until yesterday > -- > > Key: FINERACT-418 > URL: https://issues.apache.org/jira/browse/FINERACT-418 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Lionel Raymundi >Assignee: Markus Geiss > Labels: p2 > Attachments: tests_with_modified_penalties_calculation_process.odt, > tests_with_monthly_penalties.ods > > > If the Apply Penalties to Overdued loans job is run on the N day, and > considering that system properties Grace on Penalty posting = 0 and > penalty-wait-period = 0, then charges should be generated until N-1 (the day > before N). But I see only charges generated until N-2 (Two days before). > We have noticed that penalty charges are being generated one day late for > some cases. For example: > .- Lets suppose the due date of an installment is on march the 5th. > .- Overdue penalty is configured as 1% of installment interest, charged daily. > .- System configuration has Grace on Penalty posting = 0 and > penalty-wait-period = 0 > .- Run the Apply penalties to Overdued Loans job. > .- Today is march the 7th, so I would expect to see penalties on that > installment on the repayment schedule considering the following: > a) Client didn't pay On march 5th. One penalty charge should be generated. > b) Client didn't pay On march 6th. Two penalty charges should be generated. > .- I would also expect to see the charge generated with due as of date 05 and > 06 March 2017 under "Charges" tab. But I only see one penalty, as of 05. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-321) Manual Journal entries should not allowed to reverse after accounting closure is done for that branch
[ https://issues.apache.org/jira/browse/FINERACT-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935807#comment-15935807 ] ASF GitHub Bot commented on FINERACT-321: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/318 > Manual Journal entries should not allowed to reverse after accounting closure > is done for that branch > - > > Key: FINERACT-321 > URL: https://issues.apache.org/jira/browse/FINERACT-321 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting >Reporter: Santosh Math >Assignee: Markus Geiss > Labels: p2 > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2519 > Original Description: > 1. Create 2 Chart of accounts with Asset1 and Asset 2. > 2. Click on accounting -> Add Journal entries -> Add one debit and Credit > entries with above entities on 31 January 2016. > 3. Click on Accounting and Click on Closing entries and close the accounting > entries for the organization on 01 February 2016. > 4. Navigate back to the journal entries created and click on reverse entries. > It is allowing to reverse. > > It should not allowed to reverse the entries once Accounting entry is > > closed for the branch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15935804#comment-15935804 ] ASF GitHub Bot commented on FINERACT-330: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/317 > 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] [Commented] (FINERACT-243) Constitution Type Required Field
[ https://issues.apache.org/jira/browse/FINERACT-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935801#comment-15935801 ] ASF GitHub Bot commented on FINERACT-243: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/313 > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15935796#comment-15935796 ] ASF GitHub Bot commented on FINERACT-345: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/312 > 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: Markus Geiss > Labels: p1 > > 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] [Commented] (FINERACT-418) Penalties should be calculated until yesterday
[ https://issues.apache.org/jira/browse/FINERACT-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932072#comment-15932072 ] ASF GitHub Bot commented on FINERACT-418: - GitHub user lionelraymundi opened a pull request: https://github.com/apache/incubator-fineract/pull/319 FINERACT-418 penalties should be applied until the day before running job changed diff condition to <1. Previous version made penalties to be calculated until the same day the job was running You can merge this pull request into a Git repository by running: $ git pull https://github.com/lionelraymundi/incubator-fineract FINERACT-418 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/319.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #319 commit a7b27d6d363198c6017408a768d90015b047ef0c Author: Lionel Raymundi - Poincenot Date: 2017-03-20T02:11:29Z FINERACT-418 penalties should be applied until the day before running job > Penalties should be calculated until yesterday > -- > > Key: FINERACT-418 > URL: https://issues.apache.org/jira/browse/FINERACT-418 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Lionel Raymundi >Assignee: Markus Geiss > Labels: p2 > Attachments: tests_with_modified_penalties_calculation_process.odt, > tests_with_monthly_penalties.ods > > > If the Apply Penalties to Overdued loans job is run on the N day, and > considering that system properties Grace on Penalty posting = 0 and > penalty-wait-period = 0, then charges should be generated until N-1 (the day > before N). But I see only charges generated until N-2 (Two days before). > We have noticed that penalty charges are being generated one day late for > some cases. For example: > .- Lets suppose the due date of an installment is on march the 5th. > .- Overdue penalty is configured as 1% of installment interest, charged daily. > .- System configuration has Grace on Penalty posting = 0 and > penalty-wait-period = 0 > .- Run the Apply penalties to Overdued Loans job. > .- Today is march the 7th, so I would expect to see penalties on that > installment on the repayment schedule considering the following: > a) Client didn't pay On march 5th. One penalty charge should be generated. > b) Client didn't pay On march 6th. Two penalty charges should be generated. > .- I would also expect to see the charge generated with due as of date 05 and > 06 March 2017 under "Charges" tab. But I only see one penalty, as of 05. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-321) Manual Journal entries should not allowed to reverse after accounting closure is done for that branch
[ https://issues.apache.org/jira/browse/FINERACT-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929849#comment-15929849 ] ASF GitHub Bot commented on FINERACT-321: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/318 FINERACT-321 - Manual Journal entries should not allowed to reverse after accounting closure is done for that branch. You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-321 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/318.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #318 commit 5f74453606db080ae96fafbd58b0a5df96b5362c Author: nazeer1100126 Date: 2017-03-17T12:19:05Z FINERACT-321 - Manual Journal entries should not allowed to reverse after accounting closure is done for that branch > Manual Journal entries should not allowed to reverse after accounting closure > is done for that branch > - > > Key: FINERACT-321 > URL: https://issues.apache.org/jira/browse/FINERACT-321 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting >Reporter: Santosh Math >Assignee: Markus Geiss > Labels: p2 > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2519 > Original Description: > 1. Create 2 Chart of accounts with Asset1 and Asset 2. > 2. Click on accounting -> Add Journal entries -> Add one debit and Credit > entries with above entities on 31 January 2016. > 3. Click on Accounting and Click on Closing entries and close the accounting > entries for the organization on 01 February 2016. > 4. Navigate back to the journal entries created and click on reverse entries. > It is allowing to reverse. > > It should not allowed to reverse the entries once Accounting entry is > > closed for the branch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15929715#comment-15929715 ] ASF GitHub Bot commented on FINERACT-330: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/317 FINERACT-330 : No error message is getting displayed in productive collection sheet if meeting is not attached to center/group You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-330 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/317.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #317 commit d6e70134107c65d627ae27b9e59f4f0ec886850d Author: nazeer1100126 Date: 2017-03-17T10:23:39Z FINERACT-330 : No error message is getting displayed in productive collection sheet if meeting is not attached to center/group > 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: Markus Geiss >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] [Commented] (FINERACT-243) Constitution Type Required Field
[ https://issues.apache.org/jira/browse/FINERACT-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929609#comment-15929609 ] ASF GitHub Bot commented on FINERACT-243: - Github user nazeer1100126 commented on the issue: https://github.com/apache/incubator-fineract/pull/315 @tonic889 I have already done the changes and sent a PR on the same. Please look at https://github.com/apache/incubator-fineract/pull/313 > 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: Markus Geiss >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] [Commented] (FINERACT-243) Constitution Type Required Field
[ https://issues.apache.org/jira/browse/FINERACT-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927315#comment-15927315 ] ASF GitHub Bot commented on FINERACT-243: - GitHub user tonic889 opened a pull request: https://github.com/apache/incubator-fineract/pull/315 fix for FINERACT-243 : Constitution type is not required field modified: fineract-provider/src/main/java/org/apache/fineract/portfolio/client/data/ClientDataValidator.java modified: fineract-provider/src/main/java/org/apache/fineract/portfolio/client/domain/ClientNonPerson.java new file: fineract-provider/src/main/resources/sql/migrations/core_db/V326__nonpersonclient_constitution_optional.sql fix for FINERACT-243 : Constitution type is not required field You can merge this pull request into a Git repository by running: $ git pull https://github.com/tonic889/incubator-fineract develop Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/315.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #315 commit cb87df0a56e905ff6d7bf8a5f42b6bc57f908b3e Author: tonic889 Date: 2017-03-16T01:54:51Z Changes to be committed: modified: fineract-provider/src/main/java/org/apache/fineract/portfolio/client/data/ClientDataValidator.java modified: fineract-provider/src/main/java/org/apache/fineract/portfolio/client/domain/ClientNonPerson.java new file: fineract-provider/src/main/resources/sql/migrations/core_db/V326__nonpersonclient_constitution_optional.sql fix for FINERACT-243 : Constitution type is not required field > 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: Markus Geiss >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] [Commented] (FINERACT-384) Product Mix - for Saving Accounts
[ https://issues.apache.org/jira/browse/FINERACT-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926121#comment-15926121 ] ASF GitHub Bot commented on FINERACT-384: - GitHub user Ippezrobert opened a pull request: https://github.com/apache/incubator-fineract/pull/314 FINERACT-384 - Product Mix - for Saving Accounts You can merge this pull request into a Git repository by running: $ git pull https://github.com/Ippezrobert/incubator-fineract product_mix_savings Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/314.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #314 commit ef715578665849b043df5ab141542325036b5948 Author: Ippez Robert Date: 2017-03-15T12:55:31Z FINERACT-384 - Product Mix - for Saving Accounts > Product Mix - for Saving Accounts > - > > Key: FINERACT-384 > URL: https://issues.apache.org/jira/browse/FINERACT-384 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Ippez Roberts >Assignee: Markus Geiss > Labels: p2 > > The Product mix for Loan Accounts needs to be added to cater for Savings > Products as some MFI have a policy to restrict a client from opening some > savings product together by the same client. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-243) Constitution Type Required Field
[ https://issues.apache.org/jira/browse/FINERACT-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925910#comment-15925910 ] ASF GitHub Bot commented on FINERACT-243: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/313 FINERACT-243 : Constitution type is not required field You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-243 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/313.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #313 commit 770b33cf69cc55d08e3d8359db38f6fe0317ecc5 Author: nazeer1100126 Date: 2017-03-15T10:59:06Z FINERACT-243 : Constitution Type Required Field > 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: Markus Geiss >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] [Commented] (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:comment-tabpanel&focusedCommentId=15924233#comment-15924233 ] ASF GitHub Bot commented on FINERACT-345: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/312 FINERACT-345 : Should not allow to add guarantor, If savings account transaction date is greter that loan application submitted date You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-345 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/312.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #312 commit e47f4dde8b33701d3c3a092abc9b4e54c747d913 Author: nazeer1100126 Date: 2017-03-14T12:58:08Z FINERACT-345 : Should not allow to add guarantor, If savings account transaction date is greter that loan application submitted date > 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: Markus Geiss > Labels: p1 > > 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] [Commented] (FINERACT-326) Edit datatable page not able to save if the single character is entered in New Name field
[ https://issues.apache.org/jira/browse/FINERACT-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907342#comment-15907342 ] ASF GitHub Bot commented on FINERACT-326: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/311 > Edit datatable page not able to save if the single character is entered in > New Name field > -- > > Key: FINERACT-326 > URL: https://issues.apache.org/jira/browse/FINERACT-326 > Project: Apache Fineract > Issue Type: Bug > Components: Data Tables >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: p1 > Attachments: Edit datatables.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2624 > Original Description: > 1. Create a datatable for a client with string and length as 25. > 2. Click on edit and enter value as S in New name field. > 3. Click on submit button > > Not able to submit the page displayed error message as "The parameter `new > > Name` has been passed and is not supported for this request." -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15907337#comment-15907337 ] ASF GitHub Bot commented on FINERACT-344: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/310 > 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: Markus Geiss > Labels: p1 > 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] [Commented] (FINERACT-331) In edit client if the Legal Form is modified from entity to person not getting updated as person after submission
[ https://issues.apache.org/jira/browse/FINERACT-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907336#comment-15907336 ] ASF GitHub Bot commented on FINERACT-331: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/309 > In edit client if the Legal Form is modified from entity to person not > getting updated as person after submission > - > > Key: FINERACT-331 > URL: https://issues.apache.org/jira/browse/FINERACT-331 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Reporter: Santosh Math >Assignee: Markus Geiss > Labels: p1 > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2742 > Original Description: > 1. Create a client under pending state with Legal Form as Entity. > 2. Click on edit client and change the Legal Form as Person and enter valid > inputs and click on submit button. > > The client is not getting saved with Legal Form Person, but it is remaining > > as Legal Form Entity only. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-378) Not able to link savings account in Bulk JLG Loan application page
[ https://issues.apache.org/jira/browse/FINERACT-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907330#comment-15907330 ] ASF GitHub Bot commented on FINERACT-378: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/308 > Not able to link savings account in Bulk JLG Loan application page > -- > > Key: FINERACT-378 > URL: https://issues.apache.org/jira/browse/FINERACT-378 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss > Labels: p1 > Attachments: 11.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1570 > And also: https://github.com/openMF/community-app/issues/1681 > Original Description: > Create a Center with meeting date, create Group under that Center and attach > 3 Clients under that Group, Create a Loan product > Click on the Center -> Groups -> Select a particular Group ->Click on Bulk > JLG Loan Application button -> Select the Loan product - In which Link > savings account drop-down is not displaying. > If any loan charges due is need to be collected from Linked savings account > then it is not possible in this case. Check the screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-117) Tranche disbursement charge % disbursed amount is displaying as -ve amount if the 2nd tranche disbursed is with lesser amount and charge was waived before 2nd disburs
[ https://issues.apache.org/jira/browse/FINERACT-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907327#comment-15907327 ] ASF GitHub Bot commented on FINERACT-117: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/306 > Tranche disbursement charge % disbursed amount is displaying as -ve amount if > the 2nd tranche disbursed is with lesser amount and charge was waived before > 2nd disbursement > --- > > Key: FINERACT-117 > URL: https://issues.apache.org/jira/browse/FINERACT-117 > Project: Apache Fineract > Issue Type: Bug > Components: Charges >Reporter: subramanyasn >Assignee: Markus Geiss > Labels: p1 > Attachments: Mifos X Client 2016-03-24 15-30-57.png > > > 1. Create a tranche disbursement charge with % disbursement amount. > 2. Create a tranche loan with 2 tranche count, attache the above charge to it. > 3. Submit new loan application for a client on 01 January 2016 with first > tranche of 5000 on same date and second tranche of 5000 on 01 March 2016. > 4. Approve and disburse the first tranche on 01 January 2016. > 5. Click on Charges and waive charge on 01 March 2016. > 6. Disburse the 2nd tranche on 01 March 2016 and while disbursement change > the amount to 2000. > 7. Click on Repayment schedule in which the tranche disbursement charge is > displaying as -30 (Suppose to disburse 5000 so 1%of 5000=50. Waived 50 and > Disbursed 2000. 1% of 2000=20.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15907320#comment-15907320 ] ASF GitHub Bot commented on FINERACT-115: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/305 > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15907319#comment-15907319 ] ASF GitHub Bot commented on FINERACT-89: Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/304 > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15907049#comment-15907049 ] ASF GitHub Bot commented on FINERACT-344: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/310 FINERACT-344 : Should not allow to add guarantor ,If savings account activation date is gretar than loan application submitted date You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-344 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/310.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #310 commit fb1a8909404afa11229da0c63ccc7c7e55a567a0 Author: nazeer1100126 Date: 2017-03-13T08:03:13Z FINERACT-344 : Should not allow to add guarantor ,If savings account activation date is gretar than loan application submitted date > 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: Markus Geiss > Labels: p1 > 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] [Commented] (FINERACT-331) In edit client if the Legal Form is modified from entity to person not getting updated as person after submission
[ https://issues.apache.org/jira/browse/FINERACT-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904956#comment-15904956 ] ASF GitHub Bot commented on FINERACT-331: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/309 FINERACT-331 : In edit client if the Legal Form is modified from entity to person not getting updated as person after submission You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-331 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/309.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #309 commit fffc8374ebcfcd5819f08de749f23a2a012c637f Author: nazeer1100126 Date: 2017-03-10T11:44:02Z FINERACT-331 : In edit client if the Legal Form is modified from entity to person not getting updated as person after submission > In edit client if the Legal Form is modified from entity to person not > getting updated as person after submission > - > > Key: FINERACT-331 > URL: https://issues.apache.org/jira/browse/FINERACT-331 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Reporter: Santosh Math >Assignee: Markus Geiss > Labels: p1 > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2742 > Original Description: > 1. Create a client under pending state with Legal Form as Entity. > 2. Click on edit client and change the Legal Form as Person and enter valid > inputs and click on submit button. > > The client is not getting saved with Legal Form Person, but it is remaining > > as Legal Form Entity only. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-378) Not able to link savings account in Bulk JLG Loan application page
[ https://issues.apache.org/jira/browse/FINERACT-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904772#comment-15904772 ] ASF GitHub Bot commented on FINERACT-378: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/308 FINERACT-378 and 379 : Can not link a Saving account to during Group Loan Application and Bluck JLG Loan application You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-379 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/308.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #308 commit 0296fd4351f78d3d7758167bdc58fa2ca3e4f2db Author: nazeer1100126 Date: 2017-03-10T08:15:54Z FINERACT-378 and 379 : Can not link a Saving account to during Group Loan Application and Bluck JLG Loan application > Not able to link savings account in Bulk JLG Loan application page > -- > > Key: FINERACT-378 > URL: https://issues.apache.org/jira/browse/FINERACT-378 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss > Labels: p1 > Attachments: 11.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1570 > And also: https://github.com/openMF/community-app/issues/1681 > Original Description: > Create a Center with meeting date, create Group under that Center and attach > 3 Clients under that Group, Create a Loan product > Click on the Center -> Groups -> Select a particular Group ->Click on Bulk > JLG Loan Application button -> Select the Loan product - In which Link > savings account drop-down is not displaying. > If any loan charges due is need to be collected from Linked savings account > then it is not possible in this case. Check the screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-117) Tranche disbursement charge % disbursed amount is displaying as -ve amount if the 2nd tranche disbursed is with lesser amount and charge was waived before 2nd disburs
[ https://issues.apache.org/jira/browse/FINERACT-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902808#comment-15902808 ] ASF GitHub Bot commented on FINERACT-117: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/306 FINERACT-117 : Tranche disbursement charge % disbursed amount is displaying as -ve amount if the 2nd tranche disbursed is with lesser amount and charge was waived before 2nd disbursement You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-117 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/306.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #306 commit d32aeabe66b2d4aec99afe74dae7b5ee1feca517 Author: nazeer1100126 Date: 2017-03-09T09:55:58Z FINERACT-117 : Tranche disbursement charge % disbursed amount is displaying as -ve amount if the 2nd tranche disbursed is with lesser amount and charge was waived before 2nd disbursement > Tranche disbursement charge % disbursed amount is displaying as -ve amount if > the 2nd tranche disbursed is with lesser amount and charge was waived before > 2nd disbursement > --- > > Key: FINERACT-117 > URL: https://issues.apache.org/jira/browse/FINERACT-117 > Project: Apache Fineract > Issue Type: Bug > Components: Charges >Reporter: subramanyasn >Assignee: Markus Geiss > Labels: p1 > Attachments: Mifos X Client 2016-03-24 15-30-57.png > > > 1. Create a tranche disbursement charge with % disbursement amount. > 2. Create a tranche loan with 2 tranche count, attache the above charge to it. > 3. Submit new loan application for a client on 01 January 2016 with first > tranche of 5000 on same date and second tranche of 5000 on 01 March 2016. > 4. Approve and disburse the first tranche on 01 January 2016. > 5. Click on Charges and waive charge on 01 March 2016. > 6. Disburse the 2nd tranche on 01 March 2016 and while disbursement change > the amount to 2000. > 7. Click on Repayment schedule in which the tranche disbursement charge is > displaying as -30 (Suppose to disburse 5000 so 1%of 5000=50. Waived 50 and > Disbursed 2000. 1% of 2000=20.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15901203#comment-15901203 ] ASF GitHub Bot commented on FINERACT-115: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/305 FINERACT-115 : In Loan tranche details page if any tranche is added, Tranche disbursement charge is getting added twice You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-115 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/305.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #305 commit df93ce64dbddfdeb6fe4f972705625f1baac5c1b Author: nazeer1100126 Date: 2017-03-08T12:47:17Z FINERACT-115 : In Loan tranche details page if any tranche is added, Tranche disbursement charge is getting added twice > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15899503#comment-15899503 ] ASF GitHub Bot commented on FINERACT-89: GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/304 FINERACT-89 : 1st tranche will appear twice in repayment schedule when disbursement date and first repayment date is on same date You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT_BUG_89 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/304.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #304 commit 069c8ada5688eda871246969fe1bf7d1f3c39f5a Author: nazeer1100126 Date: 2017-03-07T14:15:29Z FINERACT-89 : 1st tranche will appear twice in repayment schedule when disbursement date and first repayment date is on same date > 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: Markus Geiss > 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] [Commented] (FINERACT-228) As a manager, i want to get reports on "Deposits to Staff Account "
[ https://issues.apache.org/jira/browse/FINERACT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898974#comment-15898974 ] ASF GitHub Bot commented on FINERACT-228: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/301 > As a manager, i want to get reports on "Deposits to Staff Account " > --- > > Key: FINERACT-228 > URL: https://issues.apache.org/jira/browse/FINERACT-228 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Ippez Roberts >Assignee: Markus Geiss > > During Client creation, Include "Is Staff" as a Boolean so that i can filter > loan and savings accounts that belong to a staff and any deposit activities > associated with it. This is to avoid malicious staff from posting > transactions into their accounts. > Design a report to fetch "Deposit to Staff Account". This includes both Loan > Repayment, Disbursements and Savings Deposit to a staff client for a range or > period (FROM DATE TO DATE ...) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-412) Add Share account in Global Search
[ https://issues.apache.org/jira/browse/FINERACT-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898935#comment-15898935 ] ASF GitHub Bot commented on FINERACT-412: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/300 > 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: Markus Geiss > Labels: Volunteer, p3 > > 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] [Commented] (FINERACT-232) Ability to Post General Ledger Entries Directly to Customer Account
[
https://issues.apache.org/jira/browse/FINERACT-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898891#comment-15898891
]
ASF GitHub Bot commented on FINERACT-232:
-
Github user Ippezrobert commented on a diff in the pull request:
https://github.com/apache/incubator-fineract/pull/302#discussion_r104605492
--- Diff:
fineract-provider/src/main/java/org/apache/fineract/portfolio/savings/service/SavingsApplicationProcessWritePlatformServiceJpaRepositoryImpl.java
---
@@ -446,6 +446,72 @@ public CommandProcessingResult rejectApplication(final
Long savingsId, final Jso
.build();
}
+ @Transactional
+@Override
+public CommandProcessingResult undoApplicationRejection(final Long
savingsId, final JsonCommand command) {
+this.context.authenticatedUser();
+
+
this.savingsAccountApplicationTransitionApiJsonValidator.validateForUndo(command.json());
+
+final SavingsAccount savingsAccount =
this.savingAccountAssembler.assembleFrom(savingsId);
+checkClientOrGroupActive(savingsAccount);
+
+final Map changes =
savingsAccount.undoApplicationRejection();
+if (!changes.isEmpty()) {
+this.savingAccountRepository.save(savingsAccount);
+
+final String noteText =
command.stringValueOfParameterNamed("note");
+if (StringUtils.isNotBlank(noteText)) {
+final Note note = Note.savingNote(savingsAccount,
noteText);
+changes.put("note", noteText);
+this.noteRepository.save(note);
+}
+}
+
+return new CommandProcessingResultBuilder() //
+.withCommandId(command.commandId()) //
+.withEntityId(savingsId) //
+.withOfficeId(savingsAccount.officeId()) //
+.withClientId(savingsAccount.clientId()) //
+.withGroupId(savingsAccount.groupId()) //
+.withSavingsId(savingsId) //
+.with(changes) //
+.build();
+}
+
+@Transactional
+@Override
+public CommandProcessingResult reopen(final Long savingsId, final
JsonCommand command) {
--- End diff --
@nazeer1100126 , These changes will only be possible if the issues
https://issues.apache.org/jira/browse/FINERACT-232 and
https://issues.apache.org/jira/browse/FINERACT-408 are implemented and those
are more technical for me.
> Ability to Post General Ledger Entries Directly to Customer Account
> ---
>
> Key: FINERACT-232
> URL: https://issues.apache.org/jira/browse/FINERACT-232
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: Dayna Harp
>Assignee: Markus Geiss
> Attachments: Complete New UI Mock up for Journal Entry Screen.png,
> Enhancements for Journal Entry.pdf
>
>
> https://mifosforge.jira.com/browse/MIFOSX-2182
> From MIFOS X: As an accountant, i would like to be able to make a transfer
> from a client's account (Savings Account or Loan Account) to a GL Account and
> also be able to make transfer from a GL Account (e.g Cash at Hand) to
> Client's Account (e.g Savings Account or Loan Account)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15898879#comment-15898879 ] ASF GitHub Bot commented on FINERACT-406: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/298 > 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: Shaik Nazeer Hussain > > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15898874#comment-15898874 ] ASF GitHub Bot commented on FINERACT-365: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/297 > 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] [Commented] (FINERACT-228) As a manager, i want to get reports on "Deposits to Staff Account "
[ https://issues.apache.org/jira/browse/FINERACT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897006#comment-15897006 ] ASF GitHub Bot commented on FINERACT-228: - Github user nazeer1100126 commented on the issue: https://github.com/apache/incubator-fineract/pull/301 Changes Looks OK > As a manager, i want to get reports on "Deposits to Staff Account " > --- > > Key: FINERACT-228 > URL: https://issues.apache.org/jira/browse/FINERACT-228 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Ippez Roberts >Assignee: Markus Geiss > > During Client creation, Include "Is Staff" as a Boolean so that i can filter > loan and savings accounts that belong to a staff and any deposit activities > associated with it. This is to avoid malicious staff from posting > transactions into their accounts. > Design a report to fetch "Deposit to Staff Account". This includes both Loan > Repayment, Disbursements and Savings Deposit to a staff client for a range or > period (FROM DATE TO DATE ...) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-412) Add Share account in Global Search
[ https://issues.apache.org/jira/browse/FINERACT-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15896848#comment-15896848 ] ASF GitHub Bot commented on FINERACT-412: - Github user nazeer1100126 commented on the issue: https://github.com/apache/incubator-fineract/pull/300 Changes Looks OK. > 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: Markus Geiss > Labels: Volunteer, p3 > > 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] [Commented] (FINERACT-228) As a manager, i want to get reports on "Deposits to Staff Account "
[ https://issues.apache.org/jira/browse/FINERACT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895565#comment-15895565 ] ASF GitHub Bot commented on FINERACT-228: - GitHub user Ippezrobert opened a pull request: https://github.com/apache/incubator-fineract/pull/301 FINERACT-228 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Ippezrobert/incubator-fineract is_staff_client_api Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/301.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #301 commit 5a258bde90443fc95350bb2608b34e3a08975a40 Author: Ippez Robert Date: 2017-03-04T07:45:17Z FINERACT-228 > As a manager, i want to get reports on "Deposits to Staff Account " > --- > > Key: FINERACT-228 > URL: https://issues.apache.org/jira/browse/FINERACT-228 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Ippez Roberts >Assignee: Markus Geiss > > During Client creation, Include "Is Staff" as a Boolean so that i can filter > loan and savings accounts that belong to a staff and any deposit activities > associated with it. This is to avoid malicious staff from posting > transactions into their accounts. > Design a report to fetch "Deposit to Staff Account". This includes both Loan > Repayment, Disbursements and Savings Deposit to a staff client for a range or > period (FROM DATE TO DATE ...) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-412) Add Share account in Global Search
[ https://issues.apache.org/jira/browse/FINERACT-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894070#comment-15894070 ] ASF GitHub Bot commented on FINERACT-412: - GitHub user Ippezrobert opened a pull request: https://github.com/apache/incubator-fineract/pull/300 FINERACT-412 - Add Share account in Global Search You can merge this pull request into a Git repository by running: $ git pull https://github.com/Ippezrobert/incubator-fineract search_share_global Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/300.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #300 > 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: Markus Geiss > Labels: Volunteer, p3 > > 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] [Commented] (FINERACT-412) Add Share account in Global Search
[ https://issues.apache.org/jira/browse/FINERACT-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894051#comment-15894051 ] ASF GitHub Bot commented on FINERACT-412: - Github user Ippezrobert closed the pull request at: https://github.com/apache/incubator-fineract/pull/299 > 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: Markus Geiss > Labels: Volunteer, p3 > > 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] [Commented] (FINERACT-412) Add Share account in Global Search
[ https://issues.apache.org/jira/browse/FINERACT-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892300#comment-15892300 ] ASF GitHub Bot commented on FINERACT-412: - Github user Ippezrobert commented on a diff in the pull request: https://github.com/apache/incubator-fineract/pull/299#discussion_r103930777 --- Diff: fineract-provider/src/main/java/org/apache/fineract/portfolio/search/data/SearchConditions.java --- @@ -43,18 +44,21 @@ public SearchConditions(final String searchQueryParam, final String searchResour SEARCH_SUPPORTED_RESOURCES.LOANS.name().toLowerCase())) ? true : false; this.savingSeach = (null == searchResource || searchResource.toLowerCase().contains( SEARCH_SUPPORTED_RESOURCES.SAVINGS.name().toLowerCase())) ? true : false; + this.shareSeach = (null == searchResource || searchResource.toLowerCase().contains( +SEARCH_SUPPORTED_RESOURCES.SAVINGS.name().toLowerCase())) ? true : false; --- End diff -- I will fix that and send new PR > 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: Markus Geiss > Labels: Volunteer, p3 > > 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] [Commented] (FINERACT-412) Add Share account in Global Search
[ https://issues.apache.org/jira/browse/FINERACT-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892283#comment-15892283 ] ASF GitHub Bot commented on FINERACT-412: - Github user nazeer1100126 commented on a diff in the pull request: https://github.com/apache/incubator-fineract/pull/299#discussion_r103927862 --- Diff: fineract-provider/src/main/java/org/apache/fineract/portfolio/search/data/SearchConditions.java --- @@ -43,18 +44,21 @@ public SearchConditions(final String searchQueryParam, final String searchResour SEARCH_SUPPORTED_RESOURCES.LOANS.name().toLowerCase())) ? true : false; this.savingSeach = (null == searchResource || searchResource.toLowerCase().contains( SEARCH_SUPPORTED_RESOURCES.SAVINGS.name().toLowerCase())) ? true : false; + this.shareSeach = (null == searchResource || searchResource.toLowerCase().contains( +SEARCH_SUPPORTED_RESOURCES.SAVINGS.name().toLowerCase())) ? true : false; --- End diff -- shareSeach should look for SEARCH_SUPPORTED_RESOURCES.SHARES not SEARCH_SUPPORTED_RESOURCES.SAVINGS > 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: Markus Geiss > Labels: Volunteer, p3 > > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15892268#comment-15892268 ] ASF GitHub Bot commented on FINERACT-406: - Github user nazeer1100126 commented on the issue: https://github.com/apache/incubator-fineract/pull/298 Change looks good. > 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: Shaik Nazeer Hussain > > 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] [Commented] (FINERACT-412) Add Share account in Global Search
[ https://issues.apache.org/jira/browse/FINERACT-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890247#comment-15890247 ] ASF GitHub Bot commented on FINERACT-412: - GitHub user Ippezrobert opened a pull request: https://github.com/apache/incubator-fineract/pull/299 FINERACT-412 - Add Share account in Global Search Commit for FINERACT-412 - Add Share account in Global Search You can merge this pull request into a Git repository by running: $ git pull https://github.com/Ippezrobert/incubator-fineract include_share_globalsearch Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/299.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #299 commit 7306bf0b89d0e434d8b20c94572834fde04c122e Author: Ippez Robert Date: 2017-03-01T13:49:08Z Commit for FINERACT-412 > 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: Markus Geiss > Labels: Volunteer, p3 > > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15883629#comment-15883629 ] ASF GitHub Bot commented on FINERACT-406: - GitHub user lionelraymundi opened a pull request: https://github.com/apache/incubator-fineract/pull/298 FINERACT-406 allow disbursal of topup loan on same date of transaction of previous loan You can merge this pull request into a Git repository by running: $ git pull https://github.com/lionelraymundi/incubator-fineract FINERACT-406 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/298.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #298 commit c197614af6ce8c92f66078c5d229b69371f5153a Author: Lionel Raymundi - Poincenot Date: 2017-02-24T21:49:02Z FINERACT-406 allow disbursal of topup loan on same date of transaction of previous loan > 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 >Reporter: Santosh Math >Assignee: Markus Geiss > > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15882412#comment-15882412 ] ASF GitHub Bot commented on FINERACT-365: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/297 FINERACT-365 : The 'Transactions' tab showing wrong balance in RD account You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-365 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/297.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #297 commit 652059c24693f9c10ddcc025de49e45f4cf18fbc Author: satish-conflux Date: 2017-02-24T10:21:56Z FINERACT-365 : The 'Transactions' tab showing wrong balance in RD account > 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] [Commented] (FINERACT-399) Barebones and Sampledata sql files are broken
[ https://issues.apache.org/jira/browse/FINERACT-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15882251#comment-15882251 ] ASF GitHub Bot commented on FINERACT-399: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/296 > 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] [Commented] (FINERACT-399) Barebones and Sampledata sql files are broken
[ https://issues.apache.org/jira/browse/FINERACT-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15882250#comment-15882250 ] ASF GitHub Bot commented on FINERACT-399: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/296 FINERACT-399-Barebones and Sampledata sql files are broken You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-399 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/296.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #296 commit c1af6d66853e363a30ccd44864ed4a01248faa33 Author: Nazeer Hussain Shaik Date: 2017-02-24T08:54:57Z FINERACT-399-Barebones and Sampledata sql files are broken > 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] [Commented] (FINERACT-402) Integrate PMD and Findbugs with Fineract
[ https://issues.apache.org/jira/browse/FINERACT-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880182#comment-15880182 ] ASF GitHub Bot commented on FINERACT-402: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/295 FINERACT-402-Integrate PMD and Findbugs with Fineract You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-402 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/295.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #295 commit 8c5cf0667f3b978b2d19080318d7cfcf57a18290 Author: Nazeer Hussain Shaik Date: 2017-02-23T09:39:25Z FINERACT-402-Integrate PMD and Findbugs with Fineract > 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] [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&focusedCommentId=15879930#comment-15879930 ] ASF GitHub Bot commented on FINERACT-374: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/294 > 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] [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&focusedCommentId=15879926#comment-15879926 ] ASF GitHub Bot commented on FINERACT-374: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/294 FINERACT-374-Add Gradle wrapper download location in readme file You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-374 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/294.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #294 > 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] [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&focusedCommentId=15879903#comment-15879903 ] ASF GitHub Bot commented on FINERACT-374: - Github user nazeer1100126 commented on the issue: https://github.com/apache/incubator-fineract/pull/292 Closing this PR as there is conflict in the changed file. > 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] [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&focusedCommentId=15879904#comment-15879904 ] ASF GitHub Bot commented on FINERACT-374: - Github user nazeer1100126 closed the pull request at: https://github.com/apache/incubator-fineract/pull/292 > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15878133#comment-15878133 ] ASF GitHub Bot commented on FINERACT-371: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/291 > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15877384#comment-15877384 ] ASF GitHub Bot commented on FINERACT-371: - Github user nazeer1100126 commented on the issue: https://github.com/apache/incubator-fineract/pull/291 @myrle-krantz Thank you :-). I will merge these changes today. > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15876623#comment-15876623 ] ASF GitHub Bot commented on FINERACT-371: - Github user myrle-krantz commented on the issue: https://github.com/apache/incubator-fineract/pull/291 I pulled and ran the build. It works for me. The change is also simple. > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15875641#comment-15875641 ] ASF GitHub Bot commented on FINERACT-366: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/293 > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15874227#comment-15874227 ] ASF GitHub Bot commented on FINERACT-366: - GitHub user satish-conflux opened a pull request: https://github.com/apache/incubator-fineract/pull/293 FINERACT-366 : Issue With Creating RD account with 'Charge Time Type' Savings Activation You can merge this pull request into a Git repository by running: $ git pull https://github.com/satish-conflux/incubator-fineract FINERACT-366 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/293.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #293 commit 8e9674b4aaf9d4a493ba54dbda1d08dc8468aea4 Author: satish-conflux Date: 2017-02-20T07:55:55Z FINERACT-366 : Issue With Creating RD account with 'Charge Time Type' Savings Activation > 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 > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15871784#comment-15871784 ] ASF GitHub Bot commented on FINERACT-377: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/289 > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15871733#comment-15871733 ] ASF GitHub Bot commented on FINERACT-312: - Github user asfgit closed the pull request at: 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] [Commented] (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:comment-tabpanel&focusedCommentId=15871676#comment-15871676 ] ASF GitHub Bot commented on FINERACT-234: - Github user asfgit closed the pull request at: 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] [Commented] (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:comment-tabpanel&focusedCommentId=15871540#comment-15871540 ] ASF GitHub Bot commented on FINERACT-311: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/284 > 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 > Fix For: 0.7.0-incubating > > 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] [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&focusedCommentId=15871287#comment-15871287 ] ASF GitHub Bot commented on FINERACT-374: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/292 FINERACT-374-Add Gradle wrapper download location in readme file You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-374 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/292.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #292 commit fff5cef6a4bf6f7e094af6820b4b71d5cb6692d4 Author: Nazeer Hussain Shaik Date: 2017-02-17T06:44:23Z FINERACT-374-Add Gradle wrapper download location in readme file > 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-371) Make gradle callable from the top level directory.
[ https://issues.apache.org/jira/browse/FINERACT-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869981#comment-15869981 ] ASF GitHub Bot commented on FINERACT-371: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/291 FINERACT-371 - Make gradle callable from the top level directory. You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-371 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/291.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #291 commit 1dabd44b45662fc6c5104239bd7cda43f0b0258c Author: Nazeer Hussain Shaik Date: 2017-02-16T14:08:08Z FINERACT-371 - Make gradle callable from the top level directory. > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15869954#comment-15869954 ] ASF GitHub Bot commented on FINERACT-371: - Github user nazeer1100126 closed the pull request at: https://github.com/apache/incubator-fineract/pull/290 > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15869953#comment-15869953 ] ASF GitHub Bot commented on FINERACT-371: - Github user nazeer1100126 commented on the issue: https://github.com/apache/incubator-fineract/pull/290 Closing this as RAT is still generating the report file in fineract-provider/build/report/rat/ > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15869778#comment-15869778 ] ASF GitHub Bot commented on FINERACT-371: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/290 FINERACT-371 - Make gradle callable from the top level directory. You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-371 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/290.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #290 commit 739af7552b817b989ad3eed25152fda6a73bb1f3 Author: Nazeer Hussain Shaik Date: 2017-02-16T11:30:19Z FINERACT-371 - Make gradle callable from the top level directory. > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15869698#comment-15869698 ] ASF GitHub Bot commented on FINERACT-377: - GitHub user satish-conflux opened a pull request: https://github.com/apache/incubator-fineract/pull/289 FINERACT-377 : Reinvesting Recurring Deposit is taking present date in stead of maturity date. You can merge this pull request into a Git repository by running: $ git pull https://github.com/satish-conflux/incubator-fineract FINERACT-377 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/289.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #289 commit abeab28cd7269bb61e68ea6a31f00184511f3da1 Author: satish-conflux Date: 2017-02-16T10:31:39Z FINERACT-377 : Reinvesting Recurring Deposit is taking present date in stead of maturity date > 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: Markus Geiss > 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] [Commented] (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:comment-tabpanel&focusedCommentId=1586#comment-1586 ] ASF GitHub Bot commented on FINERACT-312: - GitHub user satish-conflux opened a pull request: https://github.com/apache/incubator-fineract/pull/286 FINERACT-312 : For Loan with interest recalculation periodic accrual with respect to current date is not getting modified after repayment in Transaction page. You can merge this pull request into a Git repository by running: $ git pull https://github.com/satish-conflux/incubator-fineract FINERACT-312 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/286.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #286 commit 7ceb68fec9adfbb58cb916a7077d01b21794172f Author: satish-conflux Date: 2017-02-15T12:52:09Z FINERACT-312 : For Loan with interest recalculation periodic accrual with respect to current date is not getting modified after repayment in Transaction page > 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: Markus Geiss > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15858074#comment-15858074 ] ASF GitHub Bot commented on FINERACT-234: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/285 FINERACT-234 - Can't process bulk JLG loan application [MIFOSX-2137] You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-234 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/285.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #285 commit dc3bf98c44fdd3603aad60179c457a20c4fadc48 Author: Nazeer Hussain Shaik Date: 2017-02-08T13:49:02Z FINERACT-234 - Can't process bulk JLG loan application [MIFOSX-2137] > 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 > > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15855656#comment-15855656 ] ASF GitHub Bot commented on FINERACT-311: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/284 FINERACT-311 - Issue With 'Payment Due On Non Working Days You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-311 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/284.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #284 commit c6da909d615df4c9c13f96c6bdd04f01c35b46bc Author: Nazeer Hussain Shaik Date: 2017-02-07T09:39:49Z FINERACT-311 - Issue With 'Payment Due On Non Working Days > 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 > Fix For: 0.7.0-incubating > > 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] [Commented] (FINERACT-221) After submitting the modify application the currency is not getting updated as per the new product
[ https://issues.apache.org/jira/browse/FINERACT-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834471#comment-15834471 ] ASF GitHub Bot commented on FINERACT-221: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/281 FINERACT-221-After submitting the modify application the currency is not getting updated as per the new product You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-221 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/281.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #281 commit e92b6b171218ff7113248583beedddf4ac43512d Author: Nazeer Hussain Shaik Date: 2017-01-23T13:18:28Z FINERACT-221-After submitting the modify application the currency is not getting updated as per the new product > After submitting the modify application the currency is not getting updated > as per the new product > -- > > Key: FINERACT-221 > URL: https://issues.apache.org/jira/browse/FINERACT-221 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Markus Geiss > Labels: p1 > > 1. Create 2 loan products, one with Indian rupees as currency and another > with US Dollar > 2. Submit new loan application for a client with the loan prouduct1. > 3. Click on modify application and modify to product2. > 4. In the loan general page currency is not getting updated to US Dollar, > rather it is remaining as Indian Rupees only. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-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:comment-tabpanel&focusedCommentId=15834264#comment-15834264 ] ASF GitHub Bot commented on FINERACT-126: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/280 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 You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-126 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/280.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #280 commit e1a0e3f1ea3d75f7f93189ec1cf47d3239311c86 Author: Nazeer Hussain Shaik Date: 2017-01-23T11:00:09Z 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 > 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: Markus Geiss > Labels: p1 > 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.4#6332)
[jira] [Commented] (FINERACT-364) Submitting Collection Sheet through Maker Checker Throwing Error
[ https://issues.apache.org/jira/browse/FINERACT-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831373#comment-15831373 ] ASF GitHub Bot commented on FINERACT-364: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/276 > Submitting Collection Sheet through Maker Checker Throwing Error > > > Key: FINERACT-364 > URL: https://issues.apache.org/jira/browse/FINERACT-364 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Blocker > Labels: p1 > Attachments: 1.png, 2.png, Screen Shot 2017-01-09 at 9.40.16 AM.png > > > 1. Enable Maker Checker in System>>Configuration. > 2. Go to System>>Configure Maker Checker Tasks and click on 'Edit', select > the center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot) > 3. Disburse JLG Loan to a client. > 4. Go to collection sheet and fill the details and select the center name but > don't select the group name. > 5. Click on Submit button, which goes to Checker Inbox. > 6. When you try to approve it , it throws the error. > "The parameter `loanTransactions` has been passed and is not supported for > this request. > The parameter `SavingsTransactions` has been passed and is not supported for > this request." > Check the attached file/screenshots. > The above same error is thrown when, > > You select both center and group and submit collection sheet. > > We try to submit through 'productive collection sheet'. > > We try to submit 'Individual Collection Sheet'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-380) S3 permission issue -- add system property
[ https://issues.apache.org/jira/browse/FINERACT-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831370#comment-15831370 ] ASF GitHub Bot commented on FINERACT-380: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/278 > S3 permission issue -- add system property > -- > > Key: FINERACT-380 > URL: https://issues.apache.org/jira/browse/FINERACT-380 > Project: Apache Fineract > Issue Type: Improvement >Reporter: thynn win >Assignee: Shaik Nazeer Hussain >Priority: Critical > Labels: p1 > > Due to signature version 4 issue, I am unable to use S3 with Mifos. > Amazon suggested we add a system property and could you please help us add > this in the next version? > AWS Error Code: InvalidRequest, AWS Error Message: The authorization > mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256. > http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-16) Cannot close Savings Account when linked to a loan even when loan status is closed
[ https://issues.apache.org/jira/browse/FINERACT-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831367#comment-15831367 ] ASF GitHub Bot commented on FINERACT-16: Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/277 > 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-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:comment-tabpanel&focusedCommentId=15831300#comment-15831300 ] ASF GitHub Bot commented on FINERACT-5: --- Github user asfgit closed the pull request at: 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: Markus Geiss >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] [Commented] (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:comment-tabpanel&focusedCommentId=15829756#comment-15829756 ] ASF GitHub Bot commented on FINERACT-5: --- GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/279 FINERACT-5 Interest re-calculation setup for loan product but repayment doesn't occur You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-5 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/279.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #279 commit 77f9d5cb9565c0694bfd716a4546a5abab7caa2a Author: Nazeer Hussain Shaik Date: 2017-01-19T11:27:37Z FINERACT-5 Interest re-calculation setup for loan product but repayment doesn't occur > 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: Markus Geiss >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] [Commented] (FINERACT-380) S3 permission issue -- add system property
[ https://issues.apache.org/jira/browse/FINERACT-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829691#comment-15829691 ] ASF GitHub Bot commented on FINERACT-380: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/278 FINERACT-380 S3 permission issue -- add system property You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-380 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/278.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #278 commit b4156ed1ef703b29777005fbec673ab7f1e9c5ad Author: Nazeer Hussain Shaik Date: 2017-01-19T10:30:34Z FINERACT-380 S3 permission issue -- add system property > S3 permission issue -- add system property > -- > > Key: FINERACT-380 > URL: https://issues.apache.org/jira/browse/FINERACT-380 > Project: Apache Fineract > Issue Type: Improvement >Reporter: thynn win >Assignee: Shaik Nazeer Hussain >Priority: Critical > Labels: p1 > > Due to signature version 4 issue, I am unable to use S3 with Mifos. > Amazon suggested we add a system property and could you please help us add > this in the next version? > AWS Error Code: InvalidRequest, AWS Error Message: The authorization > mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256. > http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-16) Cannot close Savings Account when linked to a loan even when loan status is closed
[ https://issues.apache.org/jira/browse/FINERACT-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827650#comment-15827650 ] ASF GitHub Bot commented on FINERACT-16: GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/277 FINERACT-16-Cannot close Savings Account when linked to a loan even when loan status is closed You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-16 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/277.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #277 > 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-364) Submitting Collection Sheet through Maker Checker Throwing Error
[ https://issues.apache.org/jira/browse/FINERACT-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15825956#comment-15825956 ] ASF GitHub Bot commented on FINERACT-364: - GitHub user nazeer1100126 opened a pull request: https://github.com/apache/incubator-fineract/pull/276 FINERACT-364 - Submitting Collection Sheet through Maker Checker Throwing Error You can merge this pull request into a Git repository by running: $ git pull https://github.com/nazeer1100126/incubator-fineract develop_FINERACT-364 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/276.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #276 commit 0173c8d05fd33a7ac59358beb4321edcca6f9b68 Author: Nazeer Hussain Shaik Date: 2017-01-17T12:08:01Z FINERACT-364 > 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-352) Penalties for last loan installment are not shown on summary
[ https://issues.apache.org/jira/browse/FINERACT-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821089#comment-15821089 ] ASF GitHub Bot commented on FINERACT-352: - GitHub user lionelraymundi opened a pull request: https://github.com/apache/incubator-fineract/pull/274 FINERACT-352 fix showing penalties after last loan's installment The new installment created in which penalties should be applied after loan's maturity date, was created twice. This messed up with the charges recalculation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/lionelraymundi/incubator-fineract FINERACT-352 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/274.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #274 commit 392dff0cd1408632cf994063f1a0901c331b35d9 Author: lionel Date: 2017-01-12T14:11:50Z FINERACT-352 fix showing penalties after last loan's installment > Penalties for last loan installment are not shown on summary > > > Key: FINERACT-352 > URL: https://issues.apache.org/jira/browse/FINERACT-352 > Project: Apache Fineract > Issue Type: Bug >Reporter: Lionel Raymundi >Assignee: Markus Geiss > > When penalties are configured for a loan, if the last installment is not paid > on term a new installment is created, where penalties should be applied. > It seems that the penalties are being correctly created, but on installment > summary they are not properly shown. > There is an example of this on https://demo.openmf.org/#/viewloanaccount/399 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-7) Repayment Schedule after waive fee not correct
[ https://issues.apache.org/jira/browse/FINERACT-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15795343#comment-15795343 ] ASF GitHub Bot commented on FINERACT-7: --- Github user abdulazizali77 commented on the issue: https://github.com/apache/incubator-fineract/pull/256 @nazeer1100126 Hi, sorry i didnt run the integration test before. I did give the integration tests a run with and without the changes and it seems i get identical failures on ClientLoanIntegrationTest (and other tests). I will ascertain whether the two modified methods in the PR are called during any of the integration tests. From first glance however testLoanScheduleWithInterestRecalculation_WITH_REST_SAME_AS_REPAYMENT_INTEREST_COMPOUND_NONE_STRATEGY_REDUCE_EMI_WITH_INSTALLMENT_CHARGE doesnt seem to be calling Loan.generateInstallmentLoanCharges nor LoanCharge.updateInstallmentCharges. (possibly i am wrong) > Repayment Schedule after waive fee not correct > -- > > Key: FINERACT-7 > URL: https://issues.apache.org/jira/browse/FINERACT-7 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss > Attachments: 1.jpg, 2.jpg, 3.jpg > > > https://mifosforge.jira.com/browse/MIFOSX-2495 > After waive installment fee the repayment schedule generated is not proper > 1. Create Installment fee for a loan as 100-Flat-Regular. > 2. Create loan product with following datasets and attache above installment > fee to that. > Terms vary based on loan cycle : FALSE > Principal:10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max > Repay Every: 1 Months > Nominal Interest Rate:1 ( Min: , Max Per month > Minimum days between disbursal and first repayment date > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Repayment StrategyOverdue/Due Fee/Int,Principal > Account moves out of NPA only after all arrears have been cleared?No > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Allow fixing of the installment amountNo > Interest Recalculation > 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 Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01-Jan-15 > Is Arrears recognization based on original schedule:No. > 3. Submit new loan application on 01 October 2015. Approve and disburse loan > on same date. > 4. Click on waive charge and select for 1st repayment. > 5. Repayment schedule generated after waive charge is not proper > >Waive charge is happening not for first installment instead for other > >installment it is happening. > 6. For first repayment the due is getting displayed. > Attachments here: https://mifosforge.jira.com/browse/MIFOSX-2495 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-7) Repayment Schedule after waive fee not correct
[ https://issues.apache.org/jira/browse/FINERACT-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15772367#comment-15772367 ] ASF GitHub Bot commented on FINERACT-7: --- Github user nazeer1100126 commented on the issue: https://github.com/apache/incubator-fineract/pull/256 @abdulazizali77 I am seeing following integration test failure with these changes ClientLoanIntegrationTest.testLoanScheduleWithInterestRecalculation_WITH_REST_SAME_AS_REPAYMENT_INTEREST_COMPOUND_NONE_STRATEGY_REDUCE_EMI_WITH_INSTALLMENT_CHARGE() Have you run integration tests before sending this PR? > Repayment Schedule after waive fee not correct > -- > > Key: FINERACT-7 > URL: https://issues.apache.org/jira/browse/FINERACT-7 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss > Attachments: 1.jpg, 2.jpg, 3.jpg > > > https://mifosforge.jira.com/browse/MIFOSX-2495 > After waive installment fee the repayment schedule generated is not proper > 1. Create Installment fee for a loan as 100-Flat-Regular. > 2. Create loan product with following datasets and attache above installment > fee to that. > Terms vary based on loan cycle : FALSE > Principal:10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max > Repay Every: 1 Months > Nominal Interest Rate:1 ( Min: , Max Per month > Minimum days between disbursal and first repayment date > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Repayment StrategyOverdue/Due Fee/Int,Principal > Account moves out of NPA only after all arrears have been cleared?No > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Allow fixing of the installment amountNo > Interest Recalculation > 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 Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01-Jan-15 > Is Arrears recognization based on original schedule:No. > 3. Submit new loan application on 01 October 2015. Approve and disburse loan > on same date. > 4. Click on waive charge and select for 1st repayment. > 5. Repayment schedule generated after waive charge is not proper > >Waive charge is happening not for first installment instead for other > >installment it is happening. > 6. For first repayment the due is getting displayed. > Attachments here: https://mifosforge.jira.com/browse/MIFOSX-2495 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-7) Repayment Schedule after waive fee not correct
[ https://issues.apache.org/jira/browse/FINERACT-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15753695#comment-15753695 ] ASF GitHub Bot commented on FINERACT-7: --- Github user abdulazizali77 commented on the issue: https://github.com/apache/incubator-fineract/pull/256 Squashed > Repayment Schedule after waive fee not correct > -- > > Key: FINERACT-7 > URL: https://issues.apache.org/jira/browse/FINERACT-7 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss > Attachments: 1.jpg, 2.jpg, 3.jpg > > > https://mifosforge.jira.com/browse/MIFOSX-2495 > After waive installment fee the repayment schedule generated is not proper > 1. Create Installment fee for a loan as 100-Flat-Regular. > 2. Create loan product with following datasets and attache above installment > fee to that. > Terms vary based on loan cycle : FALSE > Principal:10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max > Repay Every: 1 Months > Nominal Interest Rate:1 ( Min: , Max Per month > Minimum days between disbursal and first repayment date > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Repayment StrategyOverdue/Due Fee/Int,Principal > Account moves out of NPA only after all arrears have been cleared?No > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Allow fixing of the installment amountNo > Interest Recalculation > 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 Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01-Jan-15 > Is Arrears recognization based on original schedule:No. > 3. Submit new loan application on 01 October 2015. Approve and disburse loan > on same date. > 4. Click on waive charge and select for 1st repayment. > 5. Repayment schedule generated after waive charge is not proper > >Waive charge is happening not for first installment instead for other > >installment it is happening. > 6. For first repayment the due is getting displayed. > Attachments here: https://mifosforge.jira.com/browse/MIFOSX-2495 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-7) Repayment Schedule after waive fee not correct
[ https://issues.apache.org/jira/browse/FINERACT-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15753549#comment-15753549 ] ASF GitHub Bot commented on FINERACT-7: --- Github user nazeer1100126 commented on the issue: https://github.com/apache/incubator-fineract/pull/256 @abdulazizali77 we will accept PR(s) with a single commit to maintain cleaner history. Can you please send PR with a single commit. > Repayment Schedule after waive fee not correct > -- > > Key: FINERACT-7 > URL: https://issues.apache.org/jira/browse/FINERACT-7 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss > Attachments: 1.jpg, 2.jpg, 3.jpg > > > https://mifosforge.jira.com/browse/MIFOSX-2495 > After waive installment fee the repayment schedule generated is not proper > 1. Create Installment fee for a loan as 100-Flat-Regular. > 2. Create loan product with following datasets and attache above installment > fee to that. > Terms vary based on loan cycle : FALSE > Principal:10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max > Repay Every: 1 Months > Nominal Interest Rate:1 ( Min: , Max Per month > Minimum days between disbursal and first repayment date > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Repayment StrategyOverdue/Due Fee/Int,Principal > Account moves out of NPA only after all arrears have been cleared?No > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Allow fixing of the installment amountNo > Interest Recalculation > 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 Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01-Jan-15 > Is Arrears recognization based on original schedule:No. > 3. Submit new loan application on 01 October 2015. Approve and disburse loan > on same date. > 4. Click on waive charge and select for 1st repayment. > 5. Repayment schedule generated after waive charge is not proper > >Waive charge is happening not for first installment instead for other > >installment it is happening. > 6. For first repayment the due is getting displayed. > Attachments here: https://mifosforge.jira.com/browse/MIFOSX-2495 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-7) Repayment Schedule after waive fee not correct
[
https://issues.apache.org/jira/browse/FINERACT-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15751133#comment-15751133
]
ASF GitHub Bot commented on FINERACT-7:
---
Github user abdulazizali77 commented on a diff in the pull request:
https://github.com/apache/incubator-fineract/pull/256#discussion_r92592186
--- Diff:
fineract-provider/src/main/java/org/apache/fineract/portfolio/loanaccount/domain/LoanCharge.java
---
@@ -494,17 +494,29 @@ private void updateInstallmentCharges() {
this.loanInstallmentCharge.addAll(chargePerInstallments);
} else {
int index = 0;
-final LoanInstallmentCharge[] loanChargePerInstallments = new
LoanInstallmentCharge[chargePerInstallments.size()];
-final LoanInstallmentCharge[] loanChargePerInstallmentArray =
chargePerInstallments.toArray(loanChargePerInstallments);
-for (final LoanInstallmentCharge chargePerInstallment :
this.loanInstallmentCharge) {
+//FINERACT-7: NB: this is really overkill and slow, without
changing the Sets and or Entities this is the most
+//locally safe way to fix this issue
+ArrayList oldChargeInstallments = new
ArrayList();
+ArrayList newChargeInstallments = new
ArrayList();
+
+oldChargeInstallments.addAll(this.loanInstallmentCharge);
+newChargeInstallments.addAll(chargePerInstallments);
+Collections.sort(oldChargeInstallments);
+Collections.sort(newChargeInstallments);
+final LoanInstallmentCharge[] loanChargePerInstallmentArray =
chargePerInstallments.toArray(new
LoanInstallmentCharge[chargePerInstallments.size()]);
--- End diff --
Youre right, have modified the interface accordingly
> Repayment Schedule after waive fee not correct
> --
>
> Key: FINERACT-7
> URL: https://issues.apache.org/jira/browse/FINERACT-7
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: Dayna Harp
>Assignee: Markus Geiss
> Attachments: 1.jpg, 2.jpg, 3.jpg
>
>
> https://mifosforge.jira.com/browse/MIFOSX-2495
> After waive installment fee the repayment schedule generated is not proper
> 1. Create Installment fee for a loan as 100-Flat-Regular.
> 2. Create loan product with following datasets and attache above installment
> fee to that.
> Terms vary based on loan cycle : FALSE
> Principal:10,000 ( Min: , Max : )
> Number of Repayments: 12 ( Min: , Max
> Repay Every: 1 Months
> Nominal Interest Rate:1 ( Min: , Max Per month
> Minimum days between disbursal and first repayment date
> Amortization Equal installments
> Interest Method Declining Balance
> Interest Calculation Period Daily
> Repayment StrategyOverdue/Due Fee/Int,Principal
> Account moves out of NPA only after all arrears have been cleared?No
> Days in year Actual
> Days in month Actual
> Principal Threshold (%) for Last Instalment 0
> Allow fixing of the installment amountNo
> Interest Recalculation
> 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 Daily
> Frequency Interval for recalculation 1
> Frequency Date for recalculation 01-Jan-15
> Is Arrears recognization based on original schedule:No.
> 3. Submit new loan application on 01 October 2015. Approve and disburse loan
> on same date.
> 4. Click on waive charge and select for 1st repayment.
> 5. Repayment schedule generated after waive charge is not proper
> >Waive charge is happening not for first installment instead for other
> >installment it is happening.
> 6. For first repayment the due is getting displayed.
> Attachments here: https://mifosforge.jira.com/browse/MIFOSX-2495
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FINERACT-7) Repayment Schedule after waive fee not correct
[
https://issues.apache.org/jira/browse/FINERACT-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15751132#comment-15751132
]
ASF GitHub Bot commented on FINERACT-7:
---
Github user abdulazizali77 commented on a diff in the pull request:
https://github.com/apache/incubator-fineract/pull/256#discussion_r92592164
--- Diff:
fineract-provider/src/main/java/org/apache/fineract/portfolio/loanaccount/domain/LoanCharge.java
---
@@ -494,17 +494,29 @@ private void updateInstallmentCharges() {
this.loanInstallmentCharge.addAll(chargePerInstallments);
} else {
int index = 0;
-final LoanInstallmentCharge[] loanChargePerInstallments = new
LoanInstallmentCharge[chargePerInstallments.size()];
-final LoanInstallmentCharge[] loanChargePerInstallmentArray =
chargePerInstallments.toArray(loanChargePerInstallments);
-for (final LoanInstallmentCharge chargePerInstallment :
this.loanInstallmentCharge) {
+//FINERACT-7: NB: this is really overkill and slow, without
changing the Sets and or Entities this is the most
+//locally safe way to fix this issue
+ArrayList oldChargeInstallments = new
ArrayList();
+ArrayList newChargeInstallments = new
ArrayList();
+
+oldChargeInstallments.addAll(this.loanInstallmentCharge);
+newChargeInstallments.addAll(chargePerInstallments);
+Collections.sort(oldChargeInstallments);
+Collections.sort(newChargeInstallments);
--- End diff --
fixed. (was a mistake in patch cleaning)
> Repayment Schedule after waive fee not correct
> --
>
> Key: FINERACT-7
> URL: https://issues.apache.org/jira/browse/FINERACT-7
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: Dayna Harp
>Assignee: Markus Geiss
> Attachments: 1.jpg, 2.jpg, 3.jpg
>
>
> https://mifosforge.jira.com/browse/MIFOSX-2495
> After waive installment fee the repayment schedule generated is not proper
> 1. Create Installment fee for a loan as 100-Flat-Regular.
> 2. Create loan product with following datasets and attache above installment
> fee to that.
> Terms vary based on loan cycle : FALSE
> Principal:10,000 ( Min: , Max : )
> Number of Repayments: 12 ( Min: , Max
> Repay Every: 1 Months
> Nominal Interest Rate:1 ( Min: , Max Per month
> Minimum days between disbursal and first repayment date
> Amortization Equal installments
> Interest Method Declining Balance
> Interest Calculation Period Daily
> Repayment StrategyOverdue/Due Fee/Int,Principal
> Account moves out of NPA only after all arrears have been cleared?No
> Days in year Actual
> Days in month Actual
> Principal Threshold (%) for Last Instalment 0
> Allow fixing of the installment amountNo
> Interest Recalculation
> 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 Daily
> Frequency Interval for recalculation 1
> Frequency Date for recalculation 01-Jan-15
> Is Arrears recognization based on original schedule:No.
> 3. Submit new loan application on 01 October 2015. Approve and disburse loan
> on same date.
> 4. Click on waive charge and select for 1st repayment.
> 5. Repayment schedule generated after waive charge is not proper
> >Waive charge is happening not for first installment instead for other
> >installment it is happening.
> 6. For first repayment the due is getting displayed.
> Attachments here: https://mifosforge.jira.com/browse/MIFOSX-2495
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FINERACT-7) Repayment Schedule after waive fee not correct
[
https://issues.apache.org/jira/browse/FINERACT-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15747856#comment-15747856
]
ASF GitHub Bot commented on FINERACT-7:
---
Github user nazeer1100126 commented on a diff in the pull request:
https://github.com/apache/incubator-fineract/pull/256#discussion_r92356268
--- Diff:
fineract-provider/src/main/java/org/apache/fineract/portfolio/loanaccount/domain/LoanCharge.java
---
@@ -494,17 +494,29 @@ private void updateInstallmentCharges() {
this.loanInstallmentCharge.addAll(chargePerInstallments);
} else {
int index = 0;
-final LoanInstallmentCharge[] loanChargePerInstallments = new
LoanInstallmentCharge[chargePerInstallments.size()];
-final LoanInstallmentCharge[] loanChargePerInstallmentArray =
chargePerInstallments.toArray(loanChargePerInstallments);
-for (final LoanInstallmentCharge chargePerInstallment :
this.loanInstallmentCharge) {
+//FINERACT-7: NB: this is really overkill and slow, without
changing the Sets and or Entities this is the most
+//locally safe way to fix this issue
+ArrayList oldChargeInstallments = new
ArrayList();
+ArrayList newChargeInstallments = new
ArrayList();
+
+oldChargeInstallments.addAll(this.loanInstallmentCharge);
+newChargeInstallments.addAll(chargePerInstallments);
+Collections.sort(oldChargeInstallments);
+Collections.sort(newChargeInstallments);
--- End diff --
After sorting newChargeInstallments, it is never used
> Repayment Schedule after waive fee not correct
> --
>
> Key: FINERACT-7
> URL: https://issues.apache.org/jira/browse/FINERACT-7
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: Dayna Harp
>Assignee: Markus Geiss
> Attachments: 1.jpg, 2.jpg, 3.jpg
>
>
> https://mifosforge.jira.com/browse/MIFOSX-2495
> After waive installment fee the repayment schedule generated is not proper
> 1. Create Installment fee for a loan as 100-Flat-Regular.
> 2. Create loan product with following datasets and attache above installment
> fee to that.
> Terms vary based on loan cycle : FALSE
> Principal:10,000 ( Min: , Max : )
> Number of Repayments: 12 ( Min: , Max
> Repay Every: 1 Months
> Nominal Interest Rate:1 ( Min: , Max Per month
> Minimum days between disbursal and first repayment date
> Amortization Equal installments
> Interest Method Declining Balance
> Interest Calculation Period Daily
> Repayment StrategyOverdue/Due Fee/Int,Principal
> Account moves out of NPA only after all arrears have been cleared?No
> Days in year Actual
> Days in month Actual
> Principal Threshold (%) for Last Instalment 0
> Allow fixing of the installment amountNo
> Interest Recalculation
> 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 Daily
> Frequency Interval for recalculation 1
> Frequency Date for recalculation 01-Jan-15
> Is Arrears recognization based on original schedule:No.
> 3. Submit new loan application on 01 October 2015. Approve and disburse loan
> on same date.
> 4. Click on waive charge and select for 1st repayment.
> 5. Repayment schedule generated after waive charge is not proper
> >Waive charge is happening not for first installment instead for other
> >installment it is happening.
> 6. For first repayment the due is getting displayed.
> Attachments here: https://mifosforge.jira.com/browse/MIFOSX-2495
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FINERACT-7) Repayment Schedule after waive fee not correct
[
https://issues.apache.org/jira/browse/FINERACT-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15747857#comment-15747857
]
ASF GitHub Bot commented on FINERACT-7:
---
Github user nazeer1100126 commented on a diff in the pull request:
https://github.com/apache/incubator-fineract/pull/256#discussion_r92356785
--- Diff:
fineract-provider/src/main/java/org/apache/fineract/portfolio/loanaccount/domain/LoanCharge.java
---
@@ -494,17 +494,29 @@ private void updateInstallmentCharges() {
this.loanInstallmentCharge.addAll(chargePerInstallments);
} else {
int index = 0;
-final LoanInstallmentCharge[] loanChargePerInstallments = new
LoanInstallmentCharge[chargePerInstallments.size()];
-final LoanInstallmentCharge[] loanChargePerInstallmentArray =
chargePerInstallments.toArray(loanChargePerInstallments);
-for (final LoanInstallmentCharge chargePerInstallment :
this.loanInstallmentCharge) {
+//FINERACT-7: NB: this is really overkill and slow, without
changing the Sets and or Entities this is the most
+//locally safe way to fix this issue
+ArrayList oldChargeInstallments = new
ArrayList();
+ArrayList newChargeInstallments = new
ArrayList();
+
+oldChargeInstallments.addAll(this.loanInstallmentCharge);
+newChargeInstallments.addAll(chargePerInstallments);
+Collections.sort(oldChargeInstallments);
+Collections.sort(newChargeInstallments);
+final LoanInstallmentCharge[] loanChargePerInstallmentArray =
chargePerInstallments.toArray(new
LoanInstallmentCharge[chargePerInstallments.size()]);
--- End diff --
I believe this array object is unnecessary. You can modify
Loan.generateInstallmentLoanCharges(final LoanCharge loanCharge) method to
return List object. Please use this list object
> Repayment Schedule after waive fee not correct
> --
>
> Key: FINERACT-7
> URL: https://issues.apache.org/jira/browse/FINERACT-7
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: Dayna Harp
>Assignee: Markus Geiss
> Attachments: 1.jpg, 2.jpg, 3.jpg
>
>
> https://mifosforge.jira.com/browse/MIFOSX-2495
> After waive installment fee the repayment schedule generated is not proper
> 1. Create Installment fee for a loan as 100-Flat-Regular.
> 2. Create loan product with following datasets and attache above installment
> fee to that.
> Terms vary based on loan cycle : FALSE
> Principal:10,000 ( Min: , Max : )
> Number of Repayments: 12 ( Min: , Max
> Repay Every: 1 Months
> Nominal Interest Rate:1 ( Min: , Max Per month
> Minimum days between disbursal and first repayment date
> Amortization Equal installments
> Interest Method Declining Balance
> Interest Calculation Period Daily
> Repayment StrategyOverdue/Due Fee/Int,Principal
> Account moves out of NPA only after all arrears have been cleared?No
> Days in year Actual
> Days in month Actual
> Principal Threshold (%) for Last Instalment 0
> Allow fixing of the installment amountNo
> Interest Recalculation
> 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 Daily
> Frequency Interval for recalculation 1
> Frequency Date for recalculation 01-Jan-15
> Is Arrears recognization based on original schedule:No.
> 3. Submit new loan application on 01 October 2015. Approve and disburse loan
> on same date.
> 4. Click on waive charge and select for 1st repayment.
> 5. Repayment schedule generated after waive charge is not proper
> >Waive charge is happening not for first installment instead for other
> >installment it is happening.
> 6. For first repayment the due is getting displayed.
> Attachments here: https://mifosforge.jira.com/browse/MIFOSX-2495
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15744941#comment-15744941 ] ASF GitHub Bot commented on FINERACT-267: - Github user nazeer1100126 commented on the issue: https://github.com/apache/incubator-fineract/pull/251 FINERACT-267 > 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: Markus Geiss > > 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] [Commented] (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:comment-tabpanel&focusedCommentId=15744926#comment-15744926 ] ASF GitHub Bot commented on FINERACT-260: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/250 > 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: Markus Geiss >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)
