[jira] [Created] (FINERACT-48) Collection Sheet Extensibility
Edward Cable created FINERACT-48: Summary: Collection Sheet Extensibility Key: FINERACT-48 URL: https://issues.apache.org/jira/browse/FINERACT-48 Project: Apache Fineract Issue Type: Improvement Components: Savings Reporter: Edward Cable Assignee: Markus Geiss https://mifosforge.jira.com/browse/MIFOSX-2316 As reported by Zayyad of Intrasoft Technologies: The collection sheet module currently supports Loan Repayments and Recurring Deposits only. Some MFIs collects fees and charges periodically and since these payments are done for every center it is time consuming posting them one by one. In view of this, I request the collection sheet module to be extended to include Client Charges Due as was the case in Mifos 2.x. Could also be ideal if we had the collection sheet to have an option to input normal savings for groups (not recurring) for those paying voluntary savings in their centers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-58) Improvements to User Generated Documents (Templates) Module
Edward Cable created FINERACT-58: Summary: Improvements to User Generated Documents (Templates) Module Key: FINERACT-58 URL: https://issues.apache.org/jira/browse/FINERACT-58 Project: Apache Fineract Issue Type: Improvement Components: Client Reporter: Edward Cable Assignee: Markus Geiss The user-generated documents module was developed during the 2013 Google Summer of Code program to provide a WYSIWYG editor/mail-merge functionality for easily generating customer-facing documents (letters, account statements) that dynamically pull in data stored in Fineract. These UGDs/Templates were also heavily utilized for our SMS bridge module. We need to stabilize and extend the module by doing the following: * Improvements to the UI - to provide Logical names for pre-defined fields * Extend it for Deposit Accounts too * For Loans and Deposits accounts, we should be able to access Client Details * For loans - allow Loan Summary and Tranche details tabs to be accessible in the template * Allow data table fields to be accessible for Clients and Loans and Deposits * For Loans and Deposits - allow transaction tab to be accessible in template - need a way to specify a specific transaction type and/or a date or a date-range as inputs for these at the time of invoking the report * Allow basic filters like date-range for transactions related templates * Allow totals for amount fields for transactions related templates Skills needed: SQL, Java, Javascript, Git -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-91) Add Support for Multi-Currency/Cross-Currency Transactions/Currency Exchange into Fineract
Edward Cable created FINERACT-91: Summary: Add Support for Multi-Currency/Cross-Currency Transactions/Currency Exchange into Fineract Key: FINERACT-91 URL: https://issues.apache.org/jira/browse/FINERACT-91 Project: Apache Fineract Issue Type: New Feature Reporter: Edward Cable Assignee: Markus Geiss Many Fineract users operate in multiple currencies either within one country or across multiple countries. Fineract has basic multi-currency support in tersm of the ability to support multiple currencies across the organization and define loan products in specific currencies. Support is needed to actually track and manage the foreign exchange rate of these currencies. A couple specs are in place at: https://mifosforge.jira.com/wiki/display/MIFOSX/Cross-Currency+Transactions and https://mifosforge.jira.com/wiki/display/MIFOSX/Currency+Exchange If you watch this video of a demo Robert did of the FINEM system he built, you can see the work a partner has done in implementing this feature: https://www.youtube.com/watch?v=kQXiwDcbqrk -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-109) Bank Reconciliation Module
[ https://issues.apache.org/jira/browse/FINERACT-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215078#comment-15215078 ] Edward Cable commented on FINERACT-109: --- [~emmanueln...@musoni.eu] [~sheyden] Will this be a feature that Musoni will be contributing into Fineract? Will the functionality be like as described and shipped as part of the Musoni System 1.26 release? http://musonisystem.com/wp-content/uploads/2016/01/Musoni-System-Release-1.261.pdf > Bank Reconciliation Module > -- > > Key: FINERACT-109 > URL: https://issues.apache.org/jira/browse/FINERACT-109 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Emmanuel Nnaa >Assignee: Markus Geiss >Priority: Minor > > A number of MFIs have requested the addition of a bank reconciliation module, > making it easier for them to reconcile any journal entries made against their > Bank Account GL(s) in Fineract, with the actual transactions in their bank > account. First thoughts on how this would work below: > * User will need the ability to select a specific GL Account to reconcile. > Perhaps a checkbox should be added when creating / editing a GL to specify if > it should be made available in the reconciliation module > * Reconciliation module should show all GL accounts that were previously made > available, along with the reconciled balance and unreconciled balance > * User should then be able to select the GL account, and pull out either all > journal entries between a start and end date, or all unreconciled entries, or > all reconciled entries > * User should have the ability to tick a checkbox for any entry that they > wish to reconcile and then to save at the end once they have ticked multiple > checkboxes they can save > * The act of reconciliation should be tracked and shown in the audit module > The more complex, but key, addition, will be the option to group (or if > possible to sum) all transactions with the same reference together. This will > be useful when reconciling group postings which appear as multiple GLs in > Fineract, but only one transaction in the bank account. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-128) Add support for recurring journal entries
Edward Cable created FINERACT-128: - Summary: Add support for recurring journal entries Key: FINERACT-128 URL: https://issues.apache.org/jira/browse/FINERACT-128 Project: Apache Fineract Issue Type: New Feature Reporter: Edward Cable Assignee: Markus Geiss Copied over from https://mifosforge.jira.com/browse/MIFOSX-2331 Mifos X already supports the ability to set up pre-defined general ledger journal entries via the accounting rules and frequent postings - https://mifosforge.jira.com/wiki/pages/viewpage.action?pageId=67895308 This feature has been requested by Musoni and Digital Oasis. My assumption is that we would extend off the existing frequent posting functionality, allowing the user define the frequency or recurrence of the journal entry and then a corresponding cron job to execute the entires according to the recurring schedule. Comments from Sander: Hi Ed Cable, looks like the link you referred to is no longer there. But I agree that the frequent postings are a decent jumping board. In this case we would mainly need around that: The actual amount needs to be added and stored Recurrence type implementation to trigger posting on a predefined date, as well as edit etc functionality for adjusting those. It would be good to pick up the old spec and make the modifications in there, and highlight it, as I completely agree that the 2 are closely linked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-129) Loan Approval/Disbursal by Amount (Data-Driven Authorization)
Edward Cable created FINERACT-129: - Summary: Loan Approval/Disbursal by Amount (Data-Driven Authorization) Key: FINERACT-129 URL: https://issues.apache.org/jira/browse/FINERACT-129 Project: Apache Fineract Issue Type: Improvement Reporter: Edward Cable Assignee: Markus Geiss As reported at https://mifosforge.jira.com/browse/MIFOSX-2649 In the last three RFPs I have worked on in March 2016, each had a requirement to define level of authority by amount. For Example: * New loan officer may approve and/or disburse loans up to 10,000 * A seasoned loan officer may approve and/or disburse loans up to 30,000 * A management level loan officer may approve and/or disburse loans up to 75,000 This should be configurable at the user level within the Loan Officer Role. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-130) Abillity to place a client's savings balance on hold
Edward Cable created FINERACT-130: - Summary: Abillity to place a client's savings balance on hold Key: FINERACT-130 URL: https://issues.apache.org/jira/browse/FINERACT-130 Project: Apache Fineract Issue Type: Improvement Reporter: Edward Cable Assignee: Markus Geiss As reported by Robert Ippez at https://mifosforge.jira.com/browse/MIFOSX-2509 This fits into the more broader support of flagging/holding/freezing accounts for whatever configurable purpose described at: https://goo.gl/AJfSGL In case a client has died and there are no proper documents to support transfer of ownership, such accounts should be placed on Hold - no transactions especially withdrawals should be permitted. *Hold Reason - (Code & Code values maybe):-* * Passbook loss * Illegal entries (Fraud) * Guarantying a loan * Compulsory Savings (e.g 20% of Loan Amount) * Hold for Fixed Deposit etc *Assumptions* When Account is on hold, closing of the account should not be permitted. Available Balance i.e withdraw-able amount should be less than the (Hold Amount + Min Balance required) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-134) Add support for Revolving Line of Credit products
Edward Cable created FINERACT-134: - Summary: Add support for Revolving Line of Credit products Key: FINERACT-134 URL: https://issues.apache.org/jira/browse/FINERACT-134 Project: Apache Fineract Issue Type: New Feature Reporter: Edward Cable Assignee: Markus Geiss As part of the Q2 work on Flexible Loan Schedules phase 3, we should explore supporting a new product for a revolving line of credit. We have had requests from customer like the Paradigm Project for revolving lines of credit to purchase non-durable goods like solar cook stoves etc: http://www.theparadigmproject.org/ The primary difference between a revolving and non-revolving line of credit is that repayments on RLOC replenish the available credit balance, becoming available for borrowing again. See http://goo.gl/0itVoh -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-174) Can't select "Escheat Liability" account for deposit products
Edward Cable created FINERACT-174: - Summary: Can't select "Escheat Liability" account for deposit products Key: FINERACT-174 URL: https://issues.apache.org/jira/browse/FINERACT-174 Project: Apache Fineract Issue Type: Bug Components: Savings Environment: Product Server (https://demo4.openmf.org) Reporter: Edward Cable Assignee: subramanyasn Not sure if this is a bug within Fineract or the Community App (perhaps in selection of the account). While attempting to test out the dormant/inactive savings account feature and the ability to escheat funds after a given number of days, I was unable to configure the general ledger account mapping for the Escheat Liability account for the savings product I was editing. To repro, log in to https://demo4.openmf.org with credentials, Mifos/MifosAdmin Go to Products >> Savings Products >> Basic Savings Account >> Edit >> Attempt to select an account for Escheat Liability (I newly created Escheated Deposits). Click Submit See error message that gets displayed: field is required error.msg.productToAccountMapping.not.found -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-174) Can't select "Escheat Liability" account for deposit products
[ https://issues.apache.org/jira/browse/FINERACT-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-174: -- Attachment: Screen Shot 2016-06-15 at 2.07.47 PM.png > Can't select "Escheat Liability" account for deposit products > - > > Key: FINERACT-174 > URL: https://issues.apache.org/jira/browse/FINERACT-174 > Project: Apache Fineract > Issue Type: Bug > Components: Savings > Environment: Product Server (https://demo4.openmf.org) >Reporter: Edward Cable >Assignee: subramanyasn > Attachments: Screen Shot 2016-06-15 at 2.07.47 PM.png > > > Not sure if this is a bug within Fineract or the Community App (perhaps in > selection of the account). > While attempting to test out the dormant/inactive savings account feature and > the ability to escheat funds after a given number of days, I was unable to > configure the general ledger account mapping for the Escheat Liability > account for the savings product I was editing. > To repro, log in to https://demo4.openmf.org with credentials, > Mifos/MifosAdmin > Go to Products >> Savings Products >> Basic Savings Account >> Edit >> > Attempt to select an account for Escheat Liability (I newly created Escheated > Deposits). > Click Submit > See error message that gets displayed: > field is required > error.msg.productToAccountMapping.not.found -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-201) Manage Codes Mifos X
[ https://issues.apache.org/jira/browse/FINERACT-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable resolved FINERACT-201. --- Resolution: Invalid Payment Type was made a separately configurable setting accessible under Organization during the 15.03 release. See http://mifos.org/blog/announcing-mifos-x-15-03/ for more. > Manage Codes Mifos X > > > Key: FINERACT-201 > URL: https://issues.apache.org/jira/browse/FINERACT-201 > Project: Apache Fineract > Issue Type: Bug >Reporter: Dayna Harp >Assignee: Markus Geiss > > Mifos X v 16.06.01 introduced new fields in the Admin/System/Manage Codes and > removed commonly used codes such as Payment Type. > Was this an intentional change or did the Payment Type drop down > configuration move? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-200) Separate Current Accounts from Savings Accounts
[ https://issues.apache.org/jira/browse/FINERACT-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15433284#comment-15433284 ] Edward Cable commented on FINERACT-200: --- # How do we migrate the existing data? Also this will be a big effort to provide completely new set of APIs and UI screens for Current account. Refactoring of existing code would be required as overdraft is no more allowed on savings accounts. I feel it is unnecessary effort at this moment, could this differentiation can be done with simple naming conventions at product/fee level? # Currently Savings/FD/RD are differentiated based on a account type flag. But they all share the same charge definitions. Is the requirement here only to differentiate between Savings and Current Accounts or there should be different definitions for Savings/FD/RD as well. On the face of it, this change looks difficult. Again the same question of how do we mange existing data. # There aren't many savings reports. Is there any specific report that we are concerned about? > Separate Current Accounts from Savings Accounts > --- > > Key: FINERACT-200 > URL: https://issues.apache.org/jira/browse/FINERACT-200 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Minor > > https://mifosforge.jira.com/browse/MIFOSX-1361 > Current Accounts and Savings accounts are two different category of deposit > products. At least at the User Interface, these should be treated as two > different products. At the platform level, we should have a field that > differentiate these (perhaps m_savings.product.deposit_type_enum and > m_savings_account.account_type_enum) > Savings accounts should not allow overdraft and hence the parameters > associated to overdraft can be defaulted to null. > Current accounts allow overdraft and overdraft limits and charges/interest > for overdrafts. Also they usually have zero interest rate, but we should > retain the interest rate fields for current account. > Fees - should be separated out for current accounts and savings accounts. > Also, need to be evaluated how this will impact savings reports. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (FINERACT-200) Separate Current Accounts from Savings Accounts
[ https://issues.apache.org/jira/browse/FINERACT-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15433284#comment-15433284 ] Edward Cable edited comment on FINERACT-200 at 8/23/16 5:52 PM: Comments from [~rajuan] # How do we migrate the existing data? Also this will be a big effort to provide completely new set of APIs and UI screens for Current account. Refactoring of existing code would be required as overdraft is no more allowed on savings accounts. I feel it is unnecessary effort at this moment, could this differentiation can be done with simple naming conventions at product/fee level? # Currently Savings/FD/RD are differentiated based on a account type flag. But they all share the same charge definitions. Is the requirement here only to differentiate between Savings and Current Accounts or there should be different definitions for Savings/FD/RD as well. On the face of it, this change looks difficult. Again the same question of how do we mange existing data. # There aren't many savings reports. Is there any specific report that we are concerned about? was (Author: edcable): # How do we migrate the existing data? Also this will be a big effort to provide completely new set of APIs and UI screens for Current account. Refactoring of existing code would be required as overdraft is no more allowed on savings accounts. I feel it is unnecessary effort at this moment, could this differentiation can be done with simple naming conventions at product/fee level? # Currently Savings/FD/RD are differentiated based on a account type flag. But they all share the same charge definitions. Is the requirement here only to differentiate between Savings and Current Accounts or there should be different definitions for Savings/FD/RD as well. On the face of it, this change looks difficult. Again the same question of how do we mange existing data. # There aren't many savings reports. Is there any specific report that we are concerned about? > Separate Current Accounts from Savings Accounts > --- > > Key: FINERACT-200 > URL: https://issues.apache.org/jira/browse/FINERACT-200 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Minor > > https://mifosforge.jira.com/browse/MIFOSX-1361 > Current Accounts and Savings accounts are two different category of deposit > products. At least at the User Interface, these should be treated as two > different products. At the platform level, we should have a field that > differentiate these (perhaps m_savings.product.deposit_type_enum and > m_savings_account.account_type_enum) > Savings accounts should not allow overdraft and hence the parameters > associated to overdraft can be defaulted to null. > Current accounts allow overdraft and overdraft limits and charges/interest > for overdrafts. Also they usually have zero interest rate, but we should > retain the interest rate fields for current account. > Fees - should be separated out for current accounts and savings accounts. > Also, need to be evaluated how this will impact savings reports. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-234) Can't process bulk JLG loan application [MIFOSX-2137]
Edward Cable created FINERACT-234: - Summary: 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: Markus Geiss 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.4#6332)
[jira] [Created] (FINERACT-247) Not able to save collection sheet if payment details is added (Payment type nothing is selected from dropdown)
Edward Cable created FINERACT-247: - Summary: Not able to save collection sheet if payment details is added (Payment type nothing is selected from dropdown) Key: FINERACT-247 URL: https://issues.apache.org/jira/browse/FINERACT-247 Project: Apache Fineract Issue Type: Bug Reporter: Edward Cable Assignee: Markus Geiss Priority: Minor Imported from https://mifosforge.jira.com/browse/MIFOSX-2548 1. Create a Center and attach a meeting to it. Create a group under that center and create a Client under that Group. 2. Create a loan product and submit new loan application for a client with the same loan product, sync disbursement and repayments with meeting, approve and disburse the loan. 3. Click on the collection sheet and enter valid inputs so that the above loan first repayment displayed. 4. Click on payment type and submit the collection sheet. Not able to submit -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-255) Customer Complaint Handling
[ https://issues.apache.org/jira/browse/FINERACT-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-255: -- External issue URL: https://cwiki.apache.org/confluence/display/FINERACT/Customer+Complaint+Management (was: https://mifosforge.jira.com/browse/MIFOSX-2299) > Customer Complaint Handling > --- > > Key: FINERACT-255 > URL: https://issues.apache.org/jira/browse/FINERACT-255 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Edward Cable >Assignee: Markus Geiss > > Moved over from https://mifosforge.jira.com/browse/MIFOSX-2299 > This is an oft-requested feature and the specification needs to be developed > based on community requirements. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-255) Customer Complaint Handling
Edward Cable created FINERACT-255: - Summary: Customer Complaint Handling Key: FINERACT-255 URL: https://issues.apache.org/jira/browse/FINERACT-255 Project: Apache Fineract Issue Type: Improvement Reporter: Edward Cable Assignee: Markus Geiss Moved over from https://mifosforge.jira.com/browse/MIFOSX-2299 This is an oft-requested feature and the specification needs to be developed based on community requirements. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-256) Fixed Asset Register
Edward Cable created FINERACT-256: - Summary: Fixed Asset Register Key: FINERACT-256 URL: https://issues.apache.org/jira/browse/FINERACT-256 Project: Apache Fineract Issue Type: Improvement Reporter: Edward Cable Assignee: Markus Geiss Migrated over from https://mifosforge.jira.com/browse/MIFOSX-2330 Need requirements from the community to drive forward. Please contribute to specification at linked URL. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-256) Fixed Asset Register
[ https://issues.apache.org/jira/browse/FINERACT-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-256: -- External issue URL: https://cwiki.apache.org/confluence/display/FINERACT/Fixed+Asset+Register > Fixed Asset Register > > > Key: FINERACT-256 > URL: https://issues.apache.org/jira/browse/FINERACT-256 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Edward Cable >Assignee: Markus Geiss > > Migrated over from https://mifosforge.jira.com/browse/MIFOSX-2330 > Need requirements from the community to drive forward. Please contribute to > specification at linked URL. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-259) Repaid every setting can't be edited without restarting loan application
Edward Cable created FINERACT-259: - Summary: Repaid every setting can't be edited without restarting loan application Key: FINERACT-259 URL: https://issues.apache.org/jira/browse/FINERACT-259 Project: Apache Fineract Issue Type: Bug Environment: https://demo3.openmf.org Reporter: Edward Cable Assignee: Markus Geiss When attempting to create a new loan account (an instance of a loan product), when you modify the repaid every setting from monthly to weekly and then switch back to weekly, it still retains monthly setting and can't be submitted. Steps to Reproduce 1. Navigate to Allen E Client 2. Add new Loan Account 3. Fill out parameters 4. Modify Repaid every by changing it from weeks to months and then specify fourth Wednesday of the month. 5. Revert this change by switching repaid every back to 1 weeks 6. Click Submit Error message gets displayed saying frequency day of week type must be provided when frequency nth day type is fourth. See attached screenshot. The loan form seems to think repaid monthly is still selected even though it's repaid weekly. The only way to submit the loan would be to start over the loan application from scratch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-259) Repaid every setting can't be edited without restarting loan application
[ https://issues.apache.org/jira/browse/FINERACT-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-259: -- Attachment: Screen Shot 2016-11-22 at 9.08.28 AM.png > Repaid every setting can't be edited without restarting loan application > > > Key: FINERACT-259 > URL: https://issues.apache.org/jira/browse/FINERACT-259 > Project: Apache Fineract > Issue Type: Bug > Environment: https://demo3.openmf.org >Reporter: Edward Cable >Assignee: Markus Geiss > Attachments: Screen Shot 2016-11-22 at 9.08.28 AM.png > > > When attempting to create a new loan account (an instance of a loan product), > when you modify the repaid every setting from monthly to weekly and then > switch back to weekly, it still retains monthly setting and can't be > submitted. > Steps to Reproduce > 1. Navigate to Allen E Client > 2. Add new Loan Account > 3. Fill out parameters > 4. Modify Repaid every by changing it from weeks to months and then specify > fourth Wednesday of the month. > 5. Revert this change by switching repaid every back to 1 weeks > 6. Click Submit > Error message gets displayed saying frequency day of week type must be > provided when frequency nth day type is fourth. > See attached screenshot. > The loan form seems to think repaid monthly is still selected even though > it's repaid weekly. The only way to submit the loan would be to start over > the loan application from scratch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-260) Validation need to be added if the client charge is applied before client activation date
Edward Cable created FINERACT-260: - Summary: 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 Migrated over from MifosForge. Original Description: If the client activation date is on 01 June 2016 and the charge for a client is getting applied before that date then validation need to be added, and proper error message should get displayed Steps to Reproduce 1. Add a client charge, select a due date prior to client activation date. 2. Submit and it successfully goes through. Expected Behavior 1. Upon submission of charge with a due date prior to activation date of the client, a proper error message should be displayed stating that the the charge due date is before the client activation date. See https://demo3.openmf.org/#/viewclient/10 for an example. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-260) Validation need to be added if the client charge is applied before client activation date
[ https://issues.apache.org/jira/browse/FINERACT-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-260: -- Attachment: Screen Shot 2016-11-22 at 3.21.31 PM.png > 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)
[jira] [Created] (FINERACT-261) Validate that a GL account isn't attached to a product before setting to disabled
Edward Cable created FINERACT-261: - Summary: Validate that a GL account isn't attached to a product before setting to disabled Key: FINERACT-261 URL: https://issues.apache.org/jira/browse/FINERACT-261 Project: Apache Fineract Issue Type: Bug Reporter: Edward Cable Assignee: Markus Geiss Priority: Minor As reported by [~andrew.dzak] at https://mifosforge.jira.com/browse/MIFOSX-1045 Original description: "when editing gl accounts to "disabled" there should be a validation, to check if the gl account been edited is attached to a product". Steps to reproduce: 1. Create a loan or savings product and attach a GL account to that product. 2. Go into chart of accounts and edit the GL account you added to the product and set it to disabled. 3. Try and disburse a loan from that product. The loan is still able to disbursed even though the attached GL account is disabled. Validation should be in place to prevent a user from disabling a GL account that is attached to a product and providing the proper error message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-261) Validate that a GL account isn't attached to a product before setting to disabled
[ https://issues.apache.org/jira/browse/FINERACT-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-261: -- Labels: fineract-gci (was: ) > Validate that a GL account isn't attached to a product before setting to > disabled > -- > > Key: FINERACT-261 > URL: https://issues.apache.org/jira/browse/FINERACT-261 > Project: Apache Fineract > Issue Type: Bug >Reporter: Edward Cable >Assignee: Markus Geiss >Priority: Minor > Labels: fineract-gci > > As reported by [~andrew.dzak] at > https://mifosforge.jira.com/browse/MIFOSX-1045 > Original description: > "when editing gl accounts to "disabled" there should be a validation, to > check if the gl account been edited is attached to a product". > Steps to reproduce: > 1. Create a loan or savings product and attach a GL account to that product. > 2. Go into chart of accounts and edit the GL account you added to the product > and set it to disabled. > 3. Try and disburse a loan from that product. > The loan is still able to disbursed even though the attached GL account is > disabled. > Validation should be in place to prevent a user from disabling a GL account > that is attached to a product and providing the proper error message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-262) MIFOSX-1060: Holidays declared for organization is not getting applied to the newly attached child offices.
Edward Cable created FINERACT-262: - Summary: MIFOSX-1060: Holidays declared for organization is not getting applied to the newly attached child offices. Key: FINERACT-262 URL: https://issues.apache.org/jira/browse/FINERACT-262 Project: Apache Fineract Issue Type: Bug Reporter: Edward Cable Assignee: Markus Geiss Priority: Minor Migrated over from MifosForge at https://mifosforge.jira.com/browse/MIFOSX-1060 Original description: 1.Create holiday under Head office and activate it. 2. Create a child office under that head office. 3. Click on the Administration -> Organization -> Manage Holidays - in which select the above created child office from the dropdown, - no holidays are displaying under that office. Ideally if in the organization level (or head office) any holiday is declared then it should affect the child offices which are attached newly even after declaring the holiday. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-261) Validate that a GL account isn't attached to a product before setting to disabled
[ https://issues.apache.org/jira/browse/FINERACT-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-261: -- Attachment: Screen Shot 2016-11-22 at 4.23.15 PM.png Screen Shot 2016-11-22 at 4.23.07 PM.png Screen Shot 2016-11-22 at 4.22.56 PM.png > Validate that a GL account isn't attached to a product before setting to > disabled > -- > > Key: FINERACT-261 > URL: https://issues.apache.org/jira/browse/FINERACT-261 > Project: Apache Fineract > Issue Type: Bug >Reporter: Edward Cable >Assignee: Markus Geiss >Priority: Minor > Labels: fineract-gci > Attachments: Screen Shot 2016-11-22 at 4.22.56 PM.png, Screen Shot > 2016-11-22 at 4.23.07 PM.png, Screen Shot 2016-11-22 at 4.23.15 PM.png > > > As reported by [~andrew.dzak] at > https://mifosforge.jira.com/browse/MIFOSX-1045 > Original description: > "when editing gl accounts to "disabled" there should be a validation, to > check if the gl account been edited is attached to a product". > Steps to reproduce: > 1. Create a loan or savings product and attach a GL account to that product. > 2. Go into chart of accounts and edit the GL account you added to the product > and set it to disabled. > 3. Try and disburse a loan from that product. > The loan is still able to disbursed even though the attached GL account is > disabled. > Validation should be in place to prevent a user from disabling a GL account > that is attached to a product and providing the proper error message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-262) MIFOSX-1060: Holidays declared for head office is not getting applied to the newly attached child offices
[ https://issues.apache.org/jira/browse/FINERACT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-262: -- Summary: MIFOSX-1060: Holidays declared for head office is not getting applied to the newly attached child offices (was: MIFOSX-1060: Holidays declared for organization is not getting applied to the newly attached child offices.) > MIFOSX-1060: Holidays declared for head office is not getting applied to the > newly attached child offices > - > > Key: FINERACT-262 > URL: https://issues.apache.org/jira/browse/FINERACT-262 > Project: Apache Fineract > Issue Type: Bug >Reporter: Edward Cable >Assignee: Markus Geiss >Priority: Minor > Labels: fineract-gci > > Migrated over from MifosForge at > https://mifosforge.jira.com/browse/MIFOSX-1060 > Original description: > 1.Create holiday under Head office and activate it. > 2. Create a child office under that head office. > 3. Click on the Administration -> Organization -> Manage Holidays - in which > select the above created child office from the dropdown, - no holidays are > displaying under that office. > Ideally if in the organization level (or head office) any holiday is declared > then it should affect the child offices which are attached newly even after > declaring the holiday. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-263) "Add Notes" for Centers permission is missing
Edward Cable created FINERACT-263:
-
Summary: "Add Notes" for Centers permission is missing
Key: FINERACT-263
URL: https://issues.apache.org/jira/browse/FINERACT-263
Project: Apache Fineract
Issue Type: Bug
Reporter: Edward Cable
Assignee: Markus Geiss
Priority: Minor
Migrated over from https://mifosforge.jira.com/browse/MIFOSX-1080
Original Description:
Now user can add notes to centers with out permissions. Permission should be
assigned separately for Read, Create, Edit and Delete options. See permissions
for group for example.
Comments
Shashvat Tripathi Documentation for the notes API can be found at
https://demo.openmf.org/api-docs/apiLive.htm#notes
>From a microfinance perspective, clients can be aggregated for applying Joint
>liability principles. Such a collection of clients is called a Group. Some
>organizations would want to further extend this aggregation, so you have
>collections of Groups which are called Centers etc.
In Mifosx, Centers were originally modeled as specializations of Groups
(centers are also stored in m_group table with level_id set to 1, the level_id
for groups is 2), for easier use through the API though, separate API's were
created for Centers https://demo.openmf.org/api-docs/apiLive.htm#centers, which
are mostly abstraction over the Group API with new center specific permissions.
subramanya Talks about now extending notes API to have a center specific
abstractions (with its own permissions), so we need a new notes api which would
look like
centers/{centerId}/notes/{noteId}
, also the existing group notes API i.e
groups/{groupId}/notes
should no longer work for centers
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FINERACT-263) "Add Notes" for Centers permission is missing
[
https://issues.apache.org/jira/browse/FINERACT-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Cable updated FINERACT-263:
--
Attachment: Screen Shot 2016-12-09 at 2.33.15 AM.png
Screen Shot 2016-12-09 at 2.32.35 AM.png
> "Add Notes" for Centers permission is missing
> -
>
> Key: FINERACT-263
> URL: https://issues.apache.org/jira/browse/FINERACT-263
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Edward Cable
>Assignee: Markus Geiss
>Priority: Minor
> Labels: fineract-gci
> Attachments: Screen Shot 2016-12-09 at 2.32.35 AM.png, Screen Shot
> 2016-12-09 at 2.33.15 AM.png
>
>
> Migrated over from https://mifosforge.jira.com/browse/MIFOSX-1080
> Original Description:
> Now user can add notes to centers with out permissions. Permission should be
> assigned separately for Read, Create, Edit and Delete options. See
> permissions for group for example.
> Comments
> Shashvat Tripathi Documentation for the notes API can be found at
> https://demo.openmf.org/api-docs/apiLive.htm#notes
> From a microfinance perspective, clients can be aggregated for applying Joint
> liability principles. Such a collection of clients is called a Group. Some
> organizations would want to further extend this aggregation, so you have
> collections of Groups which are called Centers etc.
> In Mifosx, Centers were originally modeled as specializations of Groups
> (centers are also stored in m_group table with level_id set to 1, the
> level_id for groups is 2), for easier use through the API though, separate
> API's were created for Centers
> https://demo.openmf.org/api-docs/apiLive.htm#centers, which are mostly
> abstraction over the Group API with new center specific permissions.
> subramanya Talks about now extending notes API to have a center specific
> abstractions (with its own permissions), so we need a new notes api which
> would look like
> centers/{centerId}/notes/{noteId}
> , also the existing group notes API i.e
> groups/{groupId}/notes
> should no longer work for centers
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FINERACT-289) Unable to view general ledger report even with correct permissions
Edward Cable created FINERACT-289: - Summary: Unable to view general ledger report even with correct permissions Key: FINERACT-289 URL: https://issues.apache.org/jira/browse/FINERACT-289 Project: Apache Fineract Issue Type: Bug Reporter: Edward Cable Assignee: Markus Geiss There is a permission code mismatch regarding the General Ledger report as reported by Upendo and discussed on the lists. Expected Behavior Accountant with necessary permissions to view general ledger report should be able to view it. On the Demo Server (https://demo3.openmf.org) with credentials mifos/password, the following has been done. 1) Navigated to System >> Roles and Permissions >> Created new role called accountant with permissions to "view general ledger report" under "report" and "read report" under "configuration" 2) Created New user with user id - accountant and password nonsecure has been created and given 3) Logged in as accountant 4) Clicked reports and accounting to view general ledger report. I should see General Ledger Report, be able to click and then input parameters to be able to run and view general ledger report. Actual Behavior * Nothing is displayed when clicking Accounting under Reports tab so don't have proper permissions to view GL report. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-289) Unable to view general ledger report even with correct permissions
[ https://issues.apache.org/jira/browse/FINERACT-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-289: -- Attachment: Screen Shot 2016-12-09 at 2.33.15 AM.png Screen Shot 2016-12-09 at 2.32.35 AM.png > Unable to view general ledger report even with correct permissions > -- > > Key: FINERACT-289 > URL: https://issues.apache.org/jira/browse/FINERACT-289 > Project: Apache Fineract > Issue Type: Bug >Reporter: Edward Cable >Assignee: Markus Geiss > Labels: fineract-gci > Attachments: Screen Shot 2016-12-09 at 2.32.35 AM.png, Screen Shot > 2016-12-09 at 2.33.15 AM.png > > > There is a permission code mismatch regarding the General Ledger report as > reported by Upendo and discussed on the lists. > Expected Behavior > Accountant with necessary permissions to view general ledger report should be > able to view it. > On the Demo Server (https://demo3.openmf.org) with credentials > mifos/password, the following has been done. > 1) Navigated to System >> Roles and Permissions >> Created new role called > accountant with permissions to "view general ledger report" under "report" > and "read report" under "configuration" > 2) Created New user with user id - accountant and password nonsecure has been > created and given > 3) Logged in as accountant > 4) Clicked reports and accounting to view general ledger report. I should see > General Ledger Report, be able to click and then input parameters to be able > to run and view general ledger report. > Actual Behavior > * Nothing is displayed when clicking Accounting under Reports tab so don't > have proper permissions to view GL report. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-263) "Add Notes" for Centers permission is missing
[
https://issues.apache.org/jira/browse/FINERACT-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Cable updated FINERACT-263:
--
Attachment: (was: Screen Shot 2016-12-09 at 2.32.35 AM.png)
> "Add Notes" for Centers permission is missing
> -
>
> Key: FINERACT-263
> URL: https://issues.apache.org/jira/browse/FINERACT-263
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Edward Cable
>Assignee: Markus Geiss
>Priority: Minor
> Labels: fineract-gci
>
> Migrated over from https://mifosforge.jira.com/browse/MIFOSX-1080
> Original Description:
> Now user can add notes to centers with out permissions. Permission should be
> assigned separately for Read, Create, Edit and Delete options. See
> permissions for group for example.
> Comments
> Shashvat Tripathi Documentation for the notes API can be found at
> https://demo.openmf.org/api-docs/apiLive.htm#notes
> From a microfinance perspective, clients can be aggregated for applying Joint
> liability principles. Such a collection of clients is called a Group. Some
> organizations would want to further extend this aggregation, so you have
> collections of Groups which are called Centers etc.
> In Mifosx, Centers were originally modeled as specializations of Groups
> (centers are also stored in m_group table with level_id set to 1, the
> level_id for groups is 2), for easier use through the API though, separate
> API's were created for Centers
> https://demo.openmf.org/api-docs/apiLive.htm#centers, which are mostly
> abstraction over the Group API with new center specific permissions.
> subramanya Talks about now extending notes API to have a center specific
> abstractions (with its own permissions), so we need a new notes api which
> would look like
> centers/{centerId}/notes/{noteId}
> , also the existing group notes API i.e
> groups/{groupId}/notes
> should no longer work for centers
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FINERACT-263) "Add Notes" for Centers permission is missing
[
https://issues.apache.org/jira/browse/FINERACT-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Cable updated FINERACT-263:
--
Attachment: (was: Screen Shot 2016-12-09 at 2.33.15 AM.png)
> "Add Notes" for Centers permission is missing
> -
>
> Key: FINERACT-263
> URL: https://issues.apache.org/jira/browse/FINERACT-263
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Edward Cable
>Assignee: Markus Geiss
>Priority: Minor
> Labels: fineract-gci
>
> Migrated over from https://mifosforge.jira.com/browse/MIFOSX-1080
> Original Description:
> Now user can add notes to centers with out permissions. Permission should be
> assigned separately for Read, Create, Edit and Delete options. See
> permissions for group for example.
> Comments
> Shashvat Tripathi Documentation for the notes API can be found at
> https://demo.openmf.org/api-docs/apiLive.htm#notes
> From a microfinance perspective, clients can be aggregated for applying Joint
> liability principles. Such a collection of clients is called a Group. Some
> organizations would want to further extend this aggregation, so you have
> collections of Groups which are called Centers etc.
> In Mifosx, Centers were originally modeled as specializations of Groups
> (centers are also stored in m_group table with level_id set to 1, the
> level_id for groups is 2), for easier use through the API though, separate
> API's were created for Centers
> https://demo.openmf.org/api-docs/apiLive.htm#centers, which are mostly
> abstraction over the Group API with new center specific permissions.
> subramanya Talks about now extending notes API to have a center specific
> abstractions (with its own permissions), so we need a new notes api which
> would look like
> centers/{centerId}/notes/{noteId}
> , also the existing group notes API i.e
> groups/{groupId}/notes
> should no longer work for centers
--
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=15812355#comment-15812355 ] Edward Cable commented on FINERACT-364: --- [~intrasofttechKE] has also encountered issues with maker/checker approval in the following tasks: https://demo.openmf.org/#/viewcheckerinbox/6755 https://demo.openmf.org/#/viewcheckerinbox/4776 https://demo.openmf.org/#/viewcheckerinbox/6152 > Submitting Collection Sheet through Maker Checker Throwing Error > > > Key: FINERACT-364 > URL: https://issues.apache.org/jira/browse/FINERACT-364 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Blocker > Attachments: 1.png, 2.png > > > 1. Enable Maker Checker in System>>Configuration. > 2. Go to System>>Configure Maker Checker Tasks and click on 'Edit', select > the center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot) > 3. Disburse JLG Loan to a client. > 4. Go to collection sheet and fill the details and select the center name but > don't select the group name. > 5. Click on Submit button, which goes to Checker Inbox. > 6. When you try to approve it , it throws the error, > "The parameter `loanTransactions` has been passed and is not supported for > this request. > The parameter `SavingsTransactions` has been passed and is not supported for > this request." > Check the attached file/screenshots. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-364) Submitting Collection Sheet through Maker Checker Throwing Error
[ https://issues.apache.org/jira/browse/FINERACT-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-364: -- Attachment: Screen Shot 2017-01-09 at 9.40.16 AM.png Error messaged received by Zayyad at https://demo.openmf.org/#/viewcheckerinbox/6755 > Submitting Collection Sheet through Maker Checker Throwing Error > > > Key: FINERACT-364 > URL: https://issues.apache.org/jira/browse/FINERACT-364 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Blocker > Attachments: 1.png, 2.png, Screen Shot 2017-01-09 at 9.40.16 AM.png > > > 1. Enable Maker Checker in System>>Configuration. > 2. Go to System>>Configure Maker Checker Tasks and click on 'Edit', select > the center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot) > 3. Disburse JLG Loan to a client. > 4. Go to collection sheet and fill the details and select the center name but > don't select the group name. > 5. Click on Submit button, which goes to Checker Inbox. > 6. When you try to approve it , it throws the error, > "The parameter `loanTransactions` has been passed and is not supported for > this request. > The parameter `SavingsTransactions` has been passed and is not supported for > this request." > Check the attached file/screenshots. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-18) Unable to reschedule loan with fee attached
[
https://issues.apache.org/jira/browse/FINERACT-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Cable updated FINERACT-18:
-
Priority: Critical (was: Blocker)
> Unable to reschedule loan with fee attached
> ---
>
> Key: FINERACT-18
> URL: https://issues.apache.org/jira/browse/FINERACT-18
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>Priority: Critical
>
> https://mifosforge.jira.com/browse/MIFOSX-1593
> Whenever I try to reschedule loan installment, which has some fee or penalty
> assigned, the rescheduling request fails.
> Is this scenario supported?
> If so, how to overcome mentioned problem?
> The failing API call is this:
> POST https://xxx:8443/mifosng-provider/api/v1/rescheduleloans HTTP/1.1
> Host: xxx:8443
> Connection: keep-alive
> Accept: application/json, text/plain, */*
> Content-Type: application/json
> X-Mifos-Platform-TenantId: default
> Origin: http://localhost:9000
> Authorization: Basic xxx
> Accept-Encoding: gzip,deflate
> Accept-Language: en-GB,en-US;q=0.8,en;q=0.6
> Content-Length: 352
> {
> "loanId": 839,
> "graceOnPrincipal": 2,
> "rescheduleFromDate": "2014-10-31",
> "adjustedDueDate": "2014-11-20",
> "dateFormat": "-MM-dd",
> "locale": "en",
> "recalculateInterest": false,
> "submittedOnDate": "2014-09-27",
> "rescheduleReasonComment" : "Client has gone AWOL",
> "rescheduleReasonId": 1
> }
> Thanks in advance for any information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FINERACT-18) Unable to reschedule loan with fee attached
[
https://issues.apache.org/jira/browse/FINERACT-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15818309#comment-15818309
]
Edward Cable commented on FINERACT-18:
--
Refer to discussion at
https://groups.google.com/forum/#!topic/mifosdeveloper/mbg8n9QZ9Iw
Reproduce and confirm that this is an issue.
> Unable to reschedule loan with fee attached
> ---
>
> Key: FINERACT-18
> URL: https://issues.apache.org/jira/browse/FINERACT-18
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>Priority: Critical
> Labels: p2
>
> https://mifosforge.jira.com/browse/MIFOSX-1593
> Whenever I try to reschedule loan installment, which has some fee or penalty
> assigned, the rescheduling request fails.
> Is this scenario supported?
> If so, how to overcome mentioned problem?
> The failing API call is this:
> POST https://xxx:8443/mifosng-provider/api/v1/rescheduleloans HTTP/1.1
> Host: xxx:8443
> Connection: keep-alive
> Accept: application/json, text/plain, */*
> Content-Type: application/json
> X-Mifos-Platform-TenantId: default
> Origin: http://localhost:9000
> Authorization: Basic xxx
> Accept-Encoding: gzip,deflate
> Accept-Language: en-GB,en-US;q=0.8,en;q=0.6
> Content-Length: 352
> {
> "loanId": 839,
> "graceOnPrincipal": 2,
> "rescheduleFromDate": "2014-10-31",
> "adjustedDueDate": "2014-11-20",
> "dateFormat": "-MM-dd",
> "locale": "en",
> "recalculateInterest": false,
> "submittedOnDate": "2014-09-27",
> "rescheduleReasonComment" : "Client has gone AWOL",
> "rescheduleReasonId": 1
> }
> Thanks in advance for any information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FINERACT-18) Unable to reschedule loan with fee attached
[
https://issues.apache.org/jira/browse/FINERACT-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Cable updated FINERACT-18:
-
Labels: p2 (was: )
> Unable to reschedule loan with fee attached
> ---
>
> Key: FINERACT-18
> URL: https://issues.apache.org/jira/browse/FINERACT-18
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>Priority: Critical
> Labels: p2
>
> https://mifosforge.jira.com/browse/MIFOSX-1593
> Whenever I try to reschedule loan installment, which has some fee or penalty
> assigned, the rescheduling request fails.
> Is this scenario supported?
> If so, how to overcome mentioned problem?
> The failing API call is this:
> POST https://xxx:8443/mifosng-provider/api/v1/rescheduleloans HTTP/1.1
> Host: xxx:8443
> Connection: keep-alive
> Accept: application/json, text/plain, */*
> Content-Type: application/json
> X-Mifos-Platform-TenantId: default
> Origin: http://localhost:9000
> Authorization: Basic xxx
> Accept-Encoding: gzip,deflate
> Accept-Language: en-GB,en-US;q=0.8,en;q=0.6
> Content-Length: 352
> {
> "loanId": 839,
> "graceOnPrincipal": 2,
> "rescheduleFromDate": "2014-10-31",
> "adjustedDueDate": "2014-11-20",
> "dateFormat": "-MM-dd",
> "locale": "en",
> "recalculateInterest": false,
> "submittedOnDate": "2014-09-27",
> "rescheduleReasonComment" : "Client has gone AWOL",
> "rescheduleReasonId": 1
> }
> Thanks in advance for any information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FINERACT-18) Unable to reschedule loan with fee attached
[
https://issues.apache.org/jira/browse/FINERACT-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Cable updated FINERACT-18:
-
Labels: confirm p2 (was: p2)
> Unable to reschedule loan with fee attached
> ---
>
> Key: FINERACT-18
> URL: https://issues.apache.org/jira/browse/FINERACT-18
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>Priority: Critical
> Labels: confirm, p2
>
> https://mifosforge.jira.com/browse/MIFOSX-1593
> Whenever I try to reschedule loan installment, which has some fee or penalty
> assigned, the rescheduling request fails.
> Is this scenario supported?
> If so, how to overcome mentioned problem?
> The failing API call is this:
> POST https://xxx:8443/mifosng-provider/api/v1/rescheduleloans HTTP/1.1
> Host: xxx:8443
> Connection: keep-alive
> Accept: application/json, text/plain, */*
> Content-Type: application/json
> X-Mifos-Platform-TenantId: default
> Origin: http://localhost:9000
> Authorization: Basic xxx
> Accept-Encoding: gzip,deflate
> Accept-Language: en-GB,en-US;q=0.8,en;q=0.6
> Content-Length: 352
> {
> "loanId": 839,
> "graceOnPrincipal": 2,
> "rescheduleFromDate": "2014-10-31",
> "adjustedDueDate": "2014-11-20",
> "dateFormat": "-MM-dd",
> "locale": "en",
> "recalculateInterest": false,
> "submittedOnDate": "2014-09-27",
> "rescheduleReasonComment" : "Client has gone AWOL",
> "rescheduleReasonId": 1
> }
> Thanks in advance for any information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FINERACT-17) Community App does not load on very slow 2g internet connections
[ https://issues.apache.org/jira/browse/FINERACT-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-17: - Issue Type: Improvement (was: Bug) > Community App does not load on very slow 2g internet connections > > > Key: FINERACT-17 > URL: https://issues.apache.org/jira/browse/FINERACT-17 > Project: Apache Fineract > Issue Type: Improvement > Components: System >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Blocker > > https://mifosforge.jira.com/browse/MIFOSX-2164 > The community app does not load on very slow 2g internet connections. > You should be able to reproduce the same by using a tool like > http://www.netlimiter.com/ and throttling the speed to less than 40 kb/ps . > You would need to do this after clearing your cache or on a private tab to > ensure that the community app is not already cached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-17) Community App does not load on very slow 2g internet connections
[ https://issues.apache.org/jira/browse/FINERACT-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-17: - Labels: p3 (was: ) > Community App does not load on very slow 2g internet connections > > > Key: FINERACT-17 > URL: https://issues.apache.org/jira/browse/FINERACT-17 > Project: Apache Fineract > Issue Type: Improvement > Components: System >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Blocker > Labels: p3 > > https://mifosforge.jira.com/browse/MIFOSX-2164 > The community app does not load on very slow 2g internet connections. > You should be able to reproduce the same by using a tool like > http://www.netlimiter.com/ and throttling the speed to less than 40 kb/ps . > You would need to do this after clearing your cache or on a private tab to > ensure that the community app is not already cached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-5) Interest re-calculation setup for loan product but repayment doesn't occur
[ https://issues.apache.org/jira/browse/FINERACT-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-5: Attachment: new 1 > 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 > 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] [Updated] (FINERACT-5) Interest re-calculation setup for loan product but repayment doesn't occur
[ https://issues.apache.org/jira/browse/FINERACT-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-5: Labels: confirm p1 (was: ) > 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=15818322#comment-15818322 ] Edward Cable commented on FINERACT-5: - Triaged on on 1/11/2017 - need to reproduce and confirm. > 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] [Resolved] (FINERACT-11) Certain loans crash entire server
[ https://issues.apache.org/jira/browse/FINERACT-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable resolved FINERACT-11. -- Resolution: Cannot Reproduce Refer to May 2016 comment thread from original issue. > Certain loans crash entire server > - > > Key: FINERACT-11 > URL: https://issues.apache.org/jira/browse/FINERACT-11 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Blocker > > https://mifosforge.jira.com/browse/MIFOSX-2409 > For some of our loans, when we try to repay, tomcat starts to use 100% of > server resources. > It can be resolved only by restarting tomcat, then undo disburse loan and > create a new loan. > When we create exact same loan again to replace the broken one, it work fine. > So it does not seem to be triggered by any of the parameters of the loan. > We had this happen in about 5% of our loans. > See for attachments and comments: > https://mifosforge.jira.com/browse/MIFOSX-2409 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-16) Cannot close Savings Account when linked to a loan even when loan status is closed
[ https://issues.apache.org/jira/browse/FINERACT-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-16: - Labels: p1 (was: ) > 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] [Updated] (FINERACT-16) Cannot close Savings Account when linked to a loan even when loan status is closed
[ https://issues.apache.org/jira/browse/FINERACT-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-16: - Priority: Critical (was: Blocker) > 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] [Resolved] (FINERACT-358) Downloaded MIfosX Android Client but unable to log in, Throwing SSL Certificate Error
[ https://issues.apache.org/jira/browse/FINERACT-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable resolved FINERACT-358. --- Resolution: Fixed Fix is included in latest release of Android client - soon to be released in Google Play store. > Downloaded MIfosX Android Client but unable to log in, Throwing SSL > Certificate Error > - > > Key: FINERACT-358 > URL: https://issues.apache.org/jira/browse/FINERACT-358 > Project: Apache Fineract > Issue Type: Bug > Components: System, User Management >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Blocker > Attachments: Screenshot_2017-01-05-09-45-09.png > > > I have downloaded Mifos X android client from play store in my smartphone, > today. My android version is 4.4. > I am unable to login using > username:mifos > password:password > It is throwing SSL Certificate Error. > I have attached the screenshot with this issue. Please resolve it as soon as > possible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-364) Submitting Collection Sheet through Maker Checker Throwing Error
[ https://issues.apache.org/jira/browse/FINERACT-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-364: -- Labels: p1 (was: ) > Submitting Collection Sheet through Maker Checker Throwing Error > > > Key: FINERACT-364 > URL: https://issues.apache.org/jira/browse/FINERACT-364 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Blocker > Labels: p1 > Attachments: 1.png, 2.png, Screen Shot 2017-01-09 at 9.40.16 AM.png > > > 1. Enable Maker Checker in System>>Configuration. > 2. Go to System>>Configure Maker Checker Tasks and click on 'Edit', select > the center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot) > 3. Disburse JLG Loan to a client. > 4. Go to collection sheet and fill the details and select the center name but > don't select the group name. > 5. Click on Submit button, which goes to Checker Inbox. > 6. When you try to approve it , it throws the error, > "The parameter `loanTransactions` has been passed and is not supported for > this request. > The parameter `SavingsTransactions` has been passed and is not supported for > this request." > Check the attached file/screenshots. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-9) Repayment Transactions allocated to FINANCIAL_ACTIVITY.LIABILITY_TRANSFER
[
https://issues.apache.org/jira/browse/FINERACT-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Cable updated FINERACT-9:
Labels: p2 (was: )
> Repayment Transactions allocated to FINANCIAL_ACTIVITY.LIABILITY_TRANSFER
> -
>
> Key: FINERACT-9
> URL: https://issues.apache.org/jira/browse/FINERACT-9
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>Priority: Critical
> Labels: p2
>
> https://mifosforge.jira.com/browse/MIFOSX-2438
> All repayment transactions after an account transfer transaction are
> allocated to FINANCIAL_ACTIVITY.LIABILITY_TRANSFER accountAll repayment
> transactions after an account transfer transaction are allocated to
> FINANCIAL_ACTIVITY.LIABILITY_TRANSFER account.
> This is cause by the "isAccountTransfer" boolean outside the for loop on line
> 108 in
> "https://github.com/openMF/mifosx/blob/develop/mifosng-provider/src/main/java/org/mifosplatform/accounting/journalentry/service/AccountingProcessorHelper.java";
> The boolean should be in the for loop.
> boolean isAccountTransfer = (Boolean)
> accountingBridgeData.get("isAccountTransfer");
> @SuppressWarnings("unchecked")
> final List> newTransactionsMap =
> (List>) accountingBridgeData.get("newLoanTransactions");
> for (final Map map : newTransactionsMap) {
> final Long transactionOfficeId = (Long) map.get("officeId");
> final String transactionId = ((Long) map.get("id")).toString();
> final Date transactionDate = ((LocalDate)
> map.get("date")).toDate();
> final LoanTransactionEnumData transactionType =
> (LoanTransactionEnumData) map.get("type");
> final BigDecimal amount = (BigDecimal) map.get("amount");
> final BigDecimal principal = (BigDecimal)
> map.get("principalPortion");
> final BigDecimal interest = (BigDecimal)
> map.get("interestPortion");
> final BigDecimal fees = (BigDecimal) map.get("feeChargesPortion");
> final BigDecimal penalties = (BigDecimal)
> map.get("penaltyChargesPortion");
> final BigDecimal overPayments = (BigDecimal)
> map.get("overPaymentPortion");
> final boolean reversed = (Boolean) map.get("reversed");
> final Long paymentTypeId = (Long) map.get("paymentTypeId");
> final List feePaymentDetails = new
> ArrayList<>();
> final List penaltyPaymentDetails = new
> ArrayList<>();
> // extract charge payment details (if exists)
> if (map.containsKey("loanChargesPaid")) {
> @SuppressWarnings("unchecked")
> final List> loanChargesPaidData =
> (List>) map.get("loanChargesPaid");
> for (final Map loanChargePaid :
> loanChargesPaidData) {
> final Long chargeId = (Long)
> loanChargePaid.get("chargeId");
> final Long loanChargeId = (Long)
> loanChargePaid.get("loanChargeId");
> final boolean isPenalty = (Boolean)
> loanChargePaid.get("isPenalty");
> final BigDecimal chargeAmountPaid = (BigDecimal)
> loanChargePaid.get("amount");
> final ChargePaymentDTO chargePaymentDTO = new
> ChargePaymentDTO(chargeId, loanChargeId, chargeAmountPaid);
> if (isPenalty) {
> penaltyPaymentDetails.add(chargePaymentDTO);
> } else {
> feePaymentDetails.add(chargePaymentDTO);
> }
> }
> }
> if (!isAccountTransfer) {
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FINERACT-9) Repayment Transactions allocated to FINANCIAL_ACTIVITY.LIABILITY_TRANSFER
[
https://issues.apache.org/jira/browse/FINERACT-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Cable updated FINERACT-9:
Priority: Major (was: Critical)
> Repayment Transactions allocated to FINANCIAL_ACTIVITY.LIABILITY_TRANSFER
> -
>
> Key: FINERACT-9
> URL: https://issues.apache.org/jira/browse/FINERACT-9
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: Dayna Harp
>Assignee: Markus Geiss
> Labels: p2
>
> https://mifosforge.jira.com/browse/MIFOSX-2438
> All repayment transactions after an account transfer transaction are
> allocated to FINANCIAL_ACTIVITY.LIABILITY_TRANSFER accountAll repayment
> transactions after an account transfer transaction are allocated to
> FINANCIAL_ACTIVITY.LIABILITY_TRANSFER account.
> This is cause by the "isAccountTransfer" boolean outside the for loop on line
> 108 in
> "https://github.com/openMF/mifosx/blob/develop/mifosng-provider/src/main/java/org/mifosplatform/accounting/journalentry/service/AccountingProcessorHelper.java";
> The boolean should be in the for loop.
> boolean isAccountTransfer = (Boolean)
> accountingBridgeData.get("isAccountTransfer");
> @SuppressWarnings("unchecked")
> final List> newTransactionsMap =
> (List>) accountingBridgeData.get("newLoanTransactions");
> for (final Map map : newTransactionsMap) {
> final Long transactionOfficeId = (Long) map.get("officeId");
> final String transactionId = ((Long) map.get("id")).toString();
> final Date transactionDate = ((LocalDate)
> map.get("date")).toDate();
> final LoanTransactionEnumData transactionType =
> (LoanTransactionEnumData) map.get("type");
> final BigDecimal amount = (BigDecimal) map.get("amount");
> final BigDecimal principal = (BigDecimal)
> map.get("principalPortion");
> final BigDecimal interest = (BigDecimal)
> map.get("interestPortion");
> final BigDecimal fees = (BigDecimal) map.get("feeChargesPortion");
> final BigDecimal penalties = (BigDecimal)
> map.get("penaltyChargesPortion");
> final BigDecimal overPayments = (BigDecimal)
> map.get("overPaymentPortion");
> final boolean reversed = (Boolean) map.get("reversed");
> final Long paymentTypeId = (Long) map.get("paymentTypeId");
> final List feePaymentDetails = new
> ArrayList<>();
> final List penaltyPaymentDetails = new
> ArrayList<>();
> // extract charge payment details (if exists)
> if (map.containsKey("loanChargesPaid")) {
> @SuppressWarnings("unchecked")
> final List> loanChargesPaidData =
> (List>) map.get("loanChargesPaid");
> for (final Map loanChargePaid :
> loanChargesPaidData) {
> final Long chargeId = (Long)
> loanChargePaid.get("chargeId");
> final Long loanChargeId = (Long)
> loanChargePaid.get("loanChargeId");
> final boolean isPenalty = (Boolean)
> loanChargePaid.get("isPenalty");
> final BigDecimal chargeAmountPaid = (BigDecimal)
> loanChargePaid.get("amount");
> final ChargePaymentDTO chargePaymentDTO = new
> ChargePaymentDTO(chargeId, loanChargeId, chargeAmountPaid);
> if (isPenalty) {
> penaltyPaymentDetails.add(chargePaymentDTO);
> } else {
> feePaymentDetails.add(chargePaymentDTO);
> }
> }
> }
> if (!isAccountTransfer) {
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FINERACT-14) Improper Repayment Strategy in Overdue/Fee/Int/Principal Strategy
[ https://issues.apache.org/jira/browse/FINERACT-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-14: - Labels: p3 (was: ) > Improper Repayment Strategy in Overdue/Fee/Int/Principal Strategy > - > > Key: FINERACT-14 > URL: https://issues.apache.org/jira/browse/FINERACT-14 > Project: Apache Fineract > Issue Type: Bug >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Critical > Labels: p3 > > https://mifosforge.jira.com/browse/MIFOSX-2397 - See for attachments > In "Overdue/Due Fee/Int,Principal" repayment strategy for loans with interest > recalculation enabled, early repayment interest computation is not proper if > interest calculation period is Daily and rest frequency as Daily > 1. Create loan product with following datasets, > Repayment Strategy:Overdue/Due Fee/Int Principal, > Repayments:12 every 1 Months, > Amortization:Equal installments > Interest:12 per annum (1% Per month), > Interest Calculation Period as Daily, > Interest Type:Declining Balance > Recalculate Interest:Yes > Days in year:Actual > Days in month:Actual > Interest recalculation compounding on:None > Advance payments adjustment type:Reduce number of installments > Frequency for recalculate Outstanding Principal:Daily, every 1 day from 01 > September 2015. > 2. Create a client and submit new loan application on 01 September 2015, > approve and disburse on same date. > 3. Make early repayment on 15 September 2015. > >Interest calculated for 01 October 2015 is not proper, > > Since repayment is done on 15 September interest should get computed for 14 > > days for 1, and for 01 October interest should get computed for 16 days > > for principal balance only. > ie Interest for 15 September 2015 > 1*(12%/365)*14 = 46.03, > Principal due > 887.72-46.03 = 841.69, > Balance of Loan > 1 - 841.69 = 9158.31. > Interest for 16 days should get calculated for 9158.31 only. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-14) Improper Repayment Strategy in Overdue/Fee/Int/Principal Strategy
[ https://issues.apache.org/jira/browse/FINERACT-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-14: - Priority: Minor (was: Critical) > Improper Repayment Strategy in Overdue/Fee/Int/Principal Strategy > - > > Key: FINERACT-14 > URL: https://issues.apache.org/jira/browse/FINERACT-14 > Project: Apache Fineract > Issue Type: Bug >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Minor > Labels: p3 > > https://mifosforge.jira.com/browse/MIFOSX-2397 - See for attachments > In "Overdue/Due Fee/Int,Principal" repayment strategy for loans with interest > recalculation enabled, early repayment interest computation is not proper if > interest calculation period is Daily and rest frequency as Daily > 1. Create loan product with following datasets, > Repayment Strategy:Overdue/Due Fee/Int Principal, > Repayments:12 every 1 Months, > Amortization:Equal installments > Interest:12 per annum (1% Per month), > Interest Calculation Period as Daily, > Interest Type:Declining Balance > Recalculate Interest:Yes > Days in year:Actual > Days in month:Actual > Interest recalculation compounding on:None > Advance payments adjustment type:Reduce number of installments > Frequency for recalculate Outstanding Principal:Daily, every 1 day from 01 > September 2015. > 2. Create a client and submit new loan application on 01 September 2015, > approve and disburse on same date. > 3. Make early repayment on 15 September 2015. > >Interest calculated for 01 October 2015 is not proper, > > Since repayment is done on 15 September interest should get computed for 14 > > days for 1, and for 01 October interest should get computed for 16 days > > for principal balance only. > ie Interest for 15 September 2015 > 1*(12%/365)*14 = 46.03, > Principal due > 887.72-46.03 = 841.69, > Balance of Loan > 1 - 841.69 = 9158.31. > Interest for 16 days should get calculated for 9158.31 only. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-14) Improper Repayment Strategy in Overdue/Fee/Int/Principal Strategy
[ https://issues.apache.org/jira/browse/FINERACT-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-14: - Labels: confirm p3 (was: p3) > Improper Repayment Strategy in Overdue/Fee/Int/Principal Strategy > - > > Key: FINERACT-14 > URL: https://issues.apache.org/jira/browse/FINERACT-14 > Project: Apache Fineract > Issue Type: Bug >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Minor > Labels: confirm, p3 > > https://mifosforge.jira.com/browse/MIFOSX-2397 - See for attachments > In "Overdue/Due Fee/Int,Principal" repayment strategy for loans with interest > recalculation enabled, early repayment interest computation is not proper if > interest calculation period is Daily and rest frequency as Daily > 1. Create loan product with following datasets, > Repayment Strategy:Overdue/Due Fee/Int Principal, > Repayments:12 every 1 Months, > Amortization:Equal installments > Interest:12 per annum (1% Per month), > Interest Calculation Period as Daily, > Interest Type:Declining Balance > Recalculate Interest:Yes > Days in year:Actual > Days in month:Actual > Interest recalculation compounding on:None > Advance payments adjustment type:Reduce number of installments > Frequency for recalculate Outstanding Principal:Daily, every 1 day from 01 > September 2015. > 2. Create a client and submit new loan application on 01 September 2015, > approve and disburse on same date. > 3. Make early repayment on 15 September 2015. > >Interest calculated for 01 October 2015 is not proper, > > Since repayment is done on 15 September interest should get computed for 14 > > days for 1, and for 01 October interest should get computed for 16 days > > for principal balance only. > ie Interest for 15 September 2015 > 1*(12%/365)*14 = 46.03, > Principal due > 887.72-46.03 = 841.69, > Balance of Loan > 1 - 841.69 = 9158.31. > Interest for 16 days should get calculated for 9158.31 only. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-20) Improper Interest Calculation for Overdue/Due/Fee/Int/Prin
[ https://issues.apache.org/jira/browse/FINERACT-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-20: - Labels: confirm p3 (was: ) > Improper Interest Calculation for Overdue/Due/Fee/Int/Prin > -- > > Key: FINERACT-20 > URL: https://issues.apache.org/jira/browse/FINERACT-20 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Critical > Labels: confirm, p3 > > https://mifosforge.jira.com/browse/MIFOSX-2396 - see attachments > In "Overdue/Due Fee/Int,Principal" repayment strategy for loans with interest > recalculation enabled, early repayment interest computation is not proper if > interest calculation period is daily and rest frequency as same as repayment > period > In "Overdue/Due Fee/Int,Principal" repayment strategy for loans with interest > recalculation enabled, early repayment interest computation is not proper if > interest calculation period is daily and rest frequency as same as repayment > period -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-24) Getting internal server error when trying to post repayment for some loans
[ https://issues.apache.org/jira/browse/FINERACT-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-24: - Labels: confirm p3 (was: p3) > Getting internal server error when trying to post repayment for some loans > -- > > Key: FINERACT-24 > URL: https://issues.apache.org/jira/browse/FINERACT-24 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Critical > Labels: confirm, p3 > > https://mifosforge.jira.com/browse/MIFOSX-2373 - see attachments and comments > When trying to post repayment for our loans (plain vanilla installment loans), > we get the following error. This happens in about 10% of cases: > "timestamp": 1449545515301 > "status": 500 > "error": "Internal Server Error" > "exception": "java.lang.ArithmeticException" > "message": "Non-terminating decimal expansion; no exact representable decimal > result." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-24) Getting internal server error when trying to post repayment for some loans
[ https://issues.apache.org/jira/browse/FINERACT-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-24: - Labels: p3 (was: ) > Getting internal server error when trying to post repayment for some loans > -- > > Key: FINERACT-24 > URL: https://issues.apache.org/jira/browse/FINERACT-24 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Critical > Labels: confirm, p3 > > https://mifosforge.jira.com/browse/MIFOSX-2373 - see attachments and comments > When trying to post repayment for our loans (plain vanilla installment loans), > we get the following error. This happens in about 10% of cases: > "timestamp": 1449545515301 > "status": 500 > "error": "Internal Server Error" > "exception": "java.lang.ArithmeticException" > "message": "Non-terminating decimal expansion; no exact representable decimal > result." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-63) Edit Center meeting is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-63: - Labels: p1 (was: ) > Edit Center meeting is not working as expected > -- > > Key: FINERACT-63 > URL: https://issues.apache.org/jira/browse/FINERACT-63 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Markus Geiss >Priority: Critical > Labels: p1 > Attachments: Exception.png, Original Calendar.png > > > 1. Create Center on 01 January 2016. Attache meeting from 01 January 2016 > every 1 month. > 2. Create a Group under that Center. > 3. Create a Client under the above Group. > 4. Submit new JLG Loan application for a client on 01 January 2016, Approve > and Disburse on the same date. > 5. Writeoff the above JLG Loan. > 5. Now Navigate back to the Center and click on the edit meeting page. > > Not able to modify the meeting date/Frequency displayed Internal server > > error. > > It should allow to modify the meeting Frequency (eg. from Monthly to > > Weekly) if there is no active loans are there, displays Internal server > > error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-145) Some of the scheduler jobs in demo version is not getting executed as scheduled
[ https://issues.apache.org/jira/browse/FINERACT-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-145: -- Labels: p3 (was: ) > Some of the scheduler jobs in demo version is not getting executed as > scheduled > --- > > Key: FINERACT-145 > URL: https://issues.apache.org/jira/browse/FINERACT-145 > Project: Apache Fineract > Issue Type: Bug > Components: System >Reporter: subramanyasn >Assignee: Shaik Nazeer Hussain >Priority: Critical > Labels: p3 > Attachments: Mifos X Client 2016-04-29 03-43-10.png > > > In demo version some of the scheduler jobs are not getting executed as it is > scheduled. Some of them will not get executed as it has to get executed on a > daily basis. After restarting the server of the demo version it executes, but > the same issue exists after few days again. > Please find the screen shot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-151) If the disbursement date is modified during loan disbursement the first repayment schedule generated is not proper
[ https://issues.apache.org/jira/browse/FINERACT-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-151: -- Labels: confirm p1 (was: confirm) > If the disbursement date is modified during loan disbursement the first > repayment schedule generated is not proper > -- > > Key: FINERACT-151 > URL: https://issues.apache.org/jira/browse/FINERACT-151 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: subramanyasn >Assignee: Markus Geiss >Priority: Critical > Labels: confirm, p1 > Attachments: Mifos X Client 2016-05-06 09-26-49.png > > > 1. Create a loan product with interest recalculation enabled. > 2. Submit new loan application for a client on 01 January 2016, and expected > disbursement date as 01 January 2016. > 3. Approve on 01 January 2016. > 4. While disbursing the modify the date as 06 May 2016 > > The repayment schedule date generated is from 01 February 2016. > It should start from 06 June 2016. > > -ve amounts getting displayed in the repayment schedule under balance loan > > column. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-151) If the disbursement date is modified during loan disbursement the first repayment schedule generated is not proper
[ https://issues.apache.org/jira/browse/FINERACT-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-151: -- Labels: confirm (was: ) > If the disbursement date is modified during loan disbursement the first > repayment schedule generated is not proper > -- > > Key: FINERACT-151 > URL: https://issues.apache.org/jira/browse/FINERACT-151 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: subramanyasn >Assignee: Markus Geiss >Priority: Critical > Labels: confirm, p1 > Attachments: Mifos X Client 2016-05-06 09-26-49.png > > > 1. Create a loan product with interest recalculation enabled. > 2. Submit new loan application for a client on 01 January 2016, and expected > disbursement date as 01 January 2016. > 3. Approve on 01 January 2016. > 4. While disbursing the modify the date as 06 May 2016 > > The repayment schedule date generated is from 01 February 2016. > It should start from 06 June 2016. > > -ve amounts getting displayed in the repayment schedule under balance loan > > column. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-155) Original schedule is getting modified if the advance repayment is done and after second tranche is disbursed
[ https://issues.apache.org/jira/browse/FINERACT-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-155: -- Labels: confirm p1 (was: ) > Original schedule is getting modified if the advance repayment is done and > after second tranche is disbursed > > > Key: FINERACT-155 > URL: https://issues.apache.org/jira/browse/FINERACT-155 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: subramanyasn >Assignee: Markus Geiss >Priority: Critical > Labels: confirm, p1 > Attachments: Mifos X Client 2016-05-10 11-49-54.png > > > 1. Create a loan product with multi tranche enabled and maximum tranche count > as 2. (Repayment strategy - Overdue/Due Fee/Int,Principal) > 2. Create a client and submit new loan application on 01 Jan 2016 for 1s > tranche and on 01 March 2016 for 2nd tranche and amount as 5000 for each > tranche. > 3.Approve and disburse 1st tranche on 01 January 2016. > 4. Make advance repayment on 01March 2016 and amount as 2000. > 5. Click on the original schedule in which first repayment is got modified > with the above repayment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-243) Constitution Type Required Field
[ https://issues.apache.org/jira/browse/FINERACT-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-243: -- Labels: p2 (was: ) > 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.4#6332)
[jira] [Updated] (FINERACT-243) Constitution Type Required Field
[ https://issues.apache.org/jira/browse/FINERACT-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-243: -- Issue Type: Improvement (was: Bug) > 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.4#6332)
[jira] [Updated] (FINERACT-329) The sum of dividend to be posted does not match with total Dividend Amount
[ https://issues.apache.org/jira/browse/FINERACT-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-329: -- Labels: confirm p1 (was: ) > The sum of dividend to be posted does not match with total Dividend Amount > -- > > Key: FINERACT-329 > URL: https://issues.apache.org/jira/browse/FINERACT-329 > Project: Apache Fineract > Issue Type: Bug > Components: Dividends, Shares >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Critical > Labels: confirm, p1 > Attachments: Dividend totals.png > > > Reported by Ippez Robert at https://mifosforge.jira.com/browse/MIFOSX-2710 > Original Description: > Create a share product. > Create share accounts with varying number of shares > Initiate a dividend with a certain dividend amount > Click on this initiated dividend > The total amount allocated does not match with the dividend amount -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-332) Can't create new tenants, new tenant database is empty
[ https://issues.apache.org/jira/browse/FINERACT-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable resolved FINERACT-332. --- Resolution: Invalid > Can't create new tenants, new tenant database is empty > -- > > Key: FINERACT-332 > URL: https://issues.apache.org/jira/browse/FINERACT-332 > Project: Apache Fineract > Issue Type: Bug > Components: System >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Critical > > Reported by Heri Fauzan at https://mifosforge.jira.com/browse/MIFOSX-2750 > I cant create new tenant database after adding a new table in > mifosplatform-tenants... > if there, only database with id=1 can be created, so another databases are > still empty.. > Anyone can help? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-336) Fund Mapping page Points to Advanced Search page
[ https://issues.apache.org/jira/browse/FINERACT-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-336: -- Issue Type: Improvement (was: Bug) > Fund Mapping page Points to Advanced Search page > > > Key: FINERACT-336 > URL: https://issues.apache.org/jira/browse/FINERACT-336 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Critical > Attachments: fundmapping.png > > > Reported by Ed Cable at https://mifosforge.jira.com/browse/MIFOSX-2795 > Original Description: > Hi all, > I think this bug has been existent for several months now as we actually > documented it as intended functionality at > https://mifosforge.jira.com/wiki/display/docs/Fund+Mapping > If you got to Admin >> Organization >> Fund Mapping, clicking the link takes > you to > https://demo4.openmf.org/#/advsearch > rather than the intended page on fund mapping (i'm not sure which it is). > On a similar note, I don't think this advance search link is accessible from > the search menu although it should be there or in the quick links. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-336) Fund Mapping page Points to Advanced Search page
[ https://issues.apache.org/jira/browse/FINERACT-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15818402#comment-15818402 ] Edward Cable commented on FINERACT-336: --- Feature isn't fully completed yet but the advanced search is first step for fund mapping, second step remains to be completed. > Fund Mapping page Points to Advanced Search page > > > Key: FINERACT-336 > URL: https://issues.apache.org/jira/browse/FINERACT-336 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Critical > Attachments: fundmapping.png > > > Reported by Ed Cable at https://mifosforge.jira.com/browse/MIFOSX-2795 > Original Description: > Hi all, > I think this bug has been existent for several months now as we actually > documented it as intended functionality at > https://mifosforge.jira.com/wiki/display/docs/Fund+Mapping > If you got to Admin >> Organization >> Fund Mapping, clicking the link takes > you to > https://demo4.openmf.org/#/advsearch > rather than the intended page on fund mapping (i'm not sure which it is). > On a similar note, I don't think this advance search link is accessible from > the search menu although it should be there or in the quick links. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-348) Issues when doing a "Close-As-Rescheduled" on a loan
[ https://issues.apache.org/jira/browse/FINERACT-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-348: -- Labels: p1 (was: ) > Issues when doing a "Close-As-Rescheduled" on a loan > - > > Key: FINERACT-348 > URL: https://issues.apache.org/jira/browse/FINERACT-348 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Critical > Labels: p1 > > Reported by Binny at https://mifosforge.jira.com/browse/MIFOSX-1205 > Original Description: > When closing a loan using the "Close (as Rescheduled)" button, the loan > account is closed, but there are no transactions or accounting entries made > for this closure. This not correct. > The following should be done: > 1) A new transaction should be visible to user under transactions to show > that the loan was closed as rescheduled rather than leaving the loan as is > without any changes. This means that Mifos X should mkae a new entry > m_loan_transaction table - with transaction_type_enum = 7 and amount as the > total outstanding amount (principal + interest + fees). > 2) Ensure that the right accounting entries are made when closing the loan as > "closed (as rescheduled)". This involves: > For loan products: capturing another General Ledger account head under > “Rescheduled in Suspense” – for example: “Rescheduled Loans Suspense Account” > When closing as loan as rescheduled, passing the following entries: > a) For Cash Accounting: > Debit: Rescheduled Loan Suspense Account (with only principal outstanding > amount) > Credit: Loan portfolio > b) For Accrual (upfront): > Debit: Rescheduled Loan Suspense Account (sum of outstanding principal + > interest + fees + penalties) > Credit: Loan portfolio (with principal outstanding amount) > Credit: Interest Receivable (with interest outstanding amount) > Credit: Fees Receivable (with fees outstanding amount) > Credit: Penalties Receivable (with penalties outstanding amount) > c) For Accrual (periodic): > Debit: Rescheduled Loan Suspense Account (sum of outstanding principal + > interest receivable accounted + fees receivable accounted + penalties > receivable accounted) > Credit: Loan portfolio (with principal outstanding amount) > Credit: Interest Receivable (with interest receivable accounted) > Credit: Fees Receivable (with fees receivable accounted) > Credit: Penalties Receivable (with penalties receivable accounted) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-6) Waive due date penalty should not create additional row
[ https://issues.apache.org/jira/browse/FINERACT-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-6: Labels: p3 (was: ) > Waive due date penalty should not create additional row > --- > > Key: FINERACT-6 > URL: https://issues.apache.org/jira/browse/FINERACT-6 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss > Labels: p3 > > https://mifosforge.jira.com/browse/MIFOSX-2497 > Waive specified due date penalty should not create additional row in > repayment schedule for Overdue/Due Fee/Int,Principal repayment strategy > 1. Create a Specified due date charge as Flat-100-Regular-Penalty. > 2. Create a loan product with Overdue/Due Fee/Int,Principal as repayment > strategy, with daily interest calculation and rest frequency as daily, > Principal : 1, no. of repayments 12, repaid every 1 month. Nominal > interest rate 1 per month. Add above created charge to it. > 3. Create a client and submit new loan application on 01 January 2015, > specified due date charge apply date as 15 January 2015. > 4. Click on charges and waive specified due date penalty. > > Since the penalty is waived it should get displayed with the first > > repayment entry under waived column. But it is creating separate row. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-7) Repayment Schedule after waive fee not correct
[ https://issues.apache.org/jira/browse/FINERACT-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable resolved FINERACT-7. - Resolution: Fixed > 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] [Resolved] (FINERACT-6) Waive due date penalty should not create additional row
[ https://issues.apache.org/jira/browse/FINERACT-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable resolved FINERACT-6. - Resolution: Fixed > Waive due date penalty should not create additional row > --- > > Key: FINERACT-6 > URL: https://issues.apache.org/jira/browse/FINERACT-6 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss > Labels: p3 > > https://mifosforge.jira.com/browse/MIFOSX-2497 > Waive specified due date penalty should not create additional row in > repayment schedule for Overdue/Due Fee/Int,Principal repayment strategy > 1. Create a Specified due date charge as Flat-100-Regular-Penalty. > 2. Create a loan product with Overdue/Due Fee/Int,Principal as repayment > strategy, with daily interest calculation and rest frequency as daily, > Principal : 1, no. of repayments 12, repaid every 1 month. Nominal > interest rate 1 per month. Add above created charge to it. > 3. Create a client and submit new loan application on 01 January 2015, > specified due date charge apply date as 15 January 2015. > 4. Click on charges and waive specified due date penalty. > > Since the penalty is waived it should get displayed with the first > > repayment entry under waived column. But it is creating separate row. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-10) Charge payment by Account transfer is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-10: - Labels: p1 (was: ) > Charge payment by Account transfer is not working as expected > - > > Key: FINERACT-10 > URL: https://issues.apache.org/jira/browse/FINERACT-10 > Project: Apache Fineract > Issue Type: Bug >Reporter: Dayna Harp >Assignee: Markus Geiss > Labels: p1 > > https://mifosforge.jira.com/browse/MIFOSX-2411 > 1. Create a specified due date charge - Flat - 100 - Account transfer. > 2. Create a loan product with the above mentioned charge attached. > 3. Activate a savings application for a client on 01 December 2015 with > balance of 1, > 4. Create a loan account for the same client with linking above savings > account (due for collection on 12 December 2015) on 01 December 2015, approve > and disburse loan on same date. > 5. Make repayment on 01 January 2015. > > Since the savings account is linked for the charge, after repayment the > > charge should get deducted from savings account. > > In Loan account after the repayment on 01 January 2015 the charge got > > collected, but the same entry is not getting created in Savings account > > transactions page. > attachments: https://mifosforge.jira.com/browse/MIFOSX-2411 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-13) Multi-tranche Loan repayment on 2nd tranche incorrect
[ https://issues.apache.org/jira/browse/FINERACT-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-13: - Labels: confirm p1 (was: ) > Multi-tranche Loan repayment on 2nd tranche incorrect > - > > Key: FINERACT-13 > URL: https://issues.apache.org/jira/browse/FINERACT-13 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss > Labels: confirm, p1 > > https://mifosforge.jira.com/browse/MIFOSX-2398 - See for attachments > 1. Create a loan product with following data sets, > Principal:10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max) > Repay Every: 1 Months > Nominal Interest Rate:1 ( Min: , Max) Per month > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Repayment StrategyPenalties, Fees, Interest, Principal order > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > 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-Sep-15 > Enable Multiple DisbursalsTRUE > Maximum Tranche count 2 > Maximum allowed outstanding balance 1 > 2. Create specified due date charge 1% of amount and attache to the above > loan product, > 3. Submit new loan application for a client on 01 September 2015 with first > tranche of 5000 on same date and second tranche on 01 November 2015 and > amount 5000. Add specified due date charge date as 15 September 2015. > 4. Make repayment on 01 October 2015 in which charge applied on 15 September > 2015 got collected and amount as 50 (1% of disbursed amount). > 5. Disburse 2nd tranche as 5000 on 01 November 2015. > > In the repayment schedule 50 is displaying as balance in 01 October 2015 > > repayment. > > Application Should not allowed to modify or apply charge for the repayment > > which is already paid -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-19) On time loan payment, Overdue Charge should be principal ony
[ https://issues.apache.org/jira/browse/FINERACT-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-19: - Labels: confirm p1 (was: ) > On time loan payment, Overdue Charge should be principal ony > > > Key: FINERACT-19 > URL: https://issues.apache.org/jira/browse/FINERACT-19 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss > Labels: confirm, p1 > > https://mifosforge.jira.com/browse/MIFOSX-2400 - see for attachments > 1. Create a simple loan product with with monthly repayment and overdue > charge as flat 100 attached. > 2. Create a client and submit new loan application for a client on 01 > September 2015 approve and disburse on same date. > 3. Execute scheduler job "Apply penalty for overdue loans". > 4. Now overdue charge got applied for 01 October 2015, 01 November 2015 and > 01 December 2015 repayments. > 5. Make back dated repayment with the amount displayed in repayment schedule > on 01 October 2015. > Expected behavior: > .Since the repayment is done on time the extra amount ie 100 paid should go > to the principal only. > Actual behavior: > The extra amount 100 is getting collected as advance payment for the > immediate next repayment. > Also for the 1st of January the penalty displayed wrongly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-19) On time loan payment, Overdue Charge should be principal ony
[ https://issues.apache.org/jira/browse/FINERACT-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-19: - Summary: On time loan payment, Overdue Charge should be principal ony (was: On time loan payment, Overview Charge should be principal ony) > On time loan payment, Overdue Charge should be principal ony > > > Key: FINERACT-19 > URL: https://issues.apache.org/jira/browse/FINERACT-19 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss > Labels: confirm, p1 > > https://mifosforge.jira.com/browse/MIFOSX-2400 - see for attachments > 1. Create a simple loan product with with monthly repayment and overdue > charge as flat 100 attached. > 2. Create a client and submit new loan application for a client on 01 > September 2015 approve and disburse on same date. > 3. Execute scheduler job "Apply penalty for overdue loans". > 4. Now overdue charge got applied for 01 October 2015, 01 November 2015 and > 01 December 2015 repayments. > 5. Make back dated repayment with the amount displayed in repayment schedule > on 01 October 2015. > Expected behavior: > .Since the repayment is done on time the extra amount ie 100 paid should go > to the principal only. > Actual behavior: > The extra amount 100 is getting collected as advance payment for the > immediate next repayment. > Also for the 1st of January the penalty displayed wrongly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-12) For Overdue/Due Fee/Int,Principal strategy with variable installment, late repayment is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-12: - Labels: p1 (was: ) > For Overdue/Due Fee/Int,Principal strategy with variable installment, late > repayment is not working as expected > --- > > Key: FINERACT-12 > URL: https://issues.apache.org/jira/browse/FINERACT-12 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss > Labels: p1 > > https://mifosforge.jira.com/browse/MIFOSX-2401 > 1. Create loan product with following datasets, > Terms > 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 > Settings > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Arrears Tolerance > Repayment Strategy Overdue/Due Fee/Int,Principal > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Allow fixing of the installment amount No > Variable Installments (Min:0 , Max:365) > 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 October 2015 > Is Arrears recognization based on original schedule No > 2. Create a client and submit new loan application on 01 October 2015. > 3. Click on More -> Edit repayment schedule in which delete repayment for 01 > November 2015 and click on validate and submit button. > 4. Approve and disburse loan on 01 October 2015. > 5. Make repayment on 15 December 2015. > > In Overdue/Due Fee/Int,Principal repayment strategy one entry on 15 > > December 2015 should get created, which is not getting getting created. > > Interest should get calculated upto 14 December 2015. (Disbursement date 01 > > October 2015 and first repayment is doing on 15 December 2015). > Attachments: https://mifosforge.jira.com/browse/MIFOSX-2401 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-21) Waive overdue charge is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-21: - Labels: confirm p1 (was: confirm) > Waive overdue charge is not working as expected > --- > > Key: FINERACT-21 > URL: https://issues.apache.org/jira/browse/FINERACT-21 > Project: Apache Fineract > Issue Type: Bug > Components: Charges >Reporter: Dayna Harp >Assignee: Markus Geiss > Labels: confirm, p1 > > https://mifosforge.jira.com/browse/MIFOSX-2392 - see attachments > 1. Create overdue charge - 100 - Flat, Create a simple loan product and apply > the above created charge to it. > 2. Submit new loan application for a client on 01 October 2015 approve and > disburse on same date. > 3. Execute the scheduler job "Apply penalty for overdue loans", > 4. Navigate back to the same loan account page and click on the charges and > waive charge on 01 November 2015. > > Charge got waved, but in the repayment schedule wrong entries got created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-21) Waive overdue charge is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-21: - Labels: confirm (was: ) > Waive overdue charge is not working as expected > --- > > Key: FINERACT-21 > URL: https://issues.apache.org/jira/browse/FINERACT-21 > Project: Apache Fineract > Issue Type: Bug > Components: Charges >Reporter: Dayna Harp >Assignee: Markus Geiss > Labels: confirm, p1 > > https://mifosforge.jira.com/browse/MIFOSX-2392 - see attachments > 1. Create overdue charge - 100 - Flat, Create a simple loan product and apply > the above created charge to it. > 2. Submit new loan application for a client on 01 October 2015 approve and > disburse on same date. > 3. Execute the scheduler job "Apply penalty for overdue loans", > 4. Navigate back to the same loan account page and click on the charges and > waive charge on 01 November 2015. > > Charge got waved, but in the repayment schedule wrong entries got created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-21) Waive overdue charge is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826008#comment-15826008 ] Edward Cable commented on FINERACT-21: -- On original issue was moved to Ready for Testing - checking if still a bug. > Waive overdue charge is not working as expected > --- > > Key: FINERACT-21 > URL: https://issues.apache.org/jira/browse/FINERACT-21 > Project: Apache Fineract > Issue Type: Bug > Components: Charges >Reporter: Dayna Harp >Assignee: Markus Geiss > Labels: confirm, p1 > > https://mifosforge.jira.com/browse/MIFOSX-2392 - see attachments > 1. Create overdue charge - 100 - Flat, Create a simple loan product and apply > the above created charge to it. > 2. Submit new loan application for a client on 01 October 2015 approve and > disburse on same date. > 3. Execute the scheduler job "Apply penalty for overdue loans", > 4. Navigate back to the same loan account page and click on the charges and > waive charge on 01 November 2015. > > Charge got waved, but in the repayment schedule wrong entries got created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-22) Adding Floating Interest Rate "Error" - cannot create floating rate
[ https://issues.apache.org/jira/browse/FINERACT-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-22: - Labels: confirm p1 (was: ) > Adding Floating Interest Rate "Error" - cannot create floating rate > --- > > Key: FINERACT-22 > URL: https://issues.apache.org/jira/browse/FINERACT-22 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss > Labels: confirm, p1 > > https://mifosforge.jira.com/browse/MIFOSX-2391 - see attachments > When a user tries to add a new Floating rate, non-descript "Error" is > returned. > 2nd MAJOR ISSUE: New Product cannot be created if Floating Rate not defined. > "Error > The parameter `isLinkedToFloatingInterestRates` has been passed and is not > supported for this request." returned. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-23) Fees rounding off attached to the loan is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-23: - Labels: p3 (was: ) > Fees rounding off attached to the loan is not working as expected > - > > Key: FINERACT-23 > URL: https://issues.apache.org/jira/browse/FINERACT-23 > Project: Apache Fineract > Issue Type: Bug > Components: Charges, Loan >Reporter: Dayna Harp >Assignee: Markus Geiss > Labels: p3 > > https://mifosforge.jira.com/browse/MIFOSX-2374 > Currently in the community app Fees rounding off is not happening properly, > Eg. In a loan product if > Decimal Places-2 > Currency in Multiples Of-1 > Installment in multiples of-1, > Disbursement fees defined as 9.877% of Approved amount, > Principal is 1, ROI - 18%pm, repaid every 1, > Loan term- 26 weeks. > After disbursement if the repayment schedule is clicked then fees displayed > is not rounded off. > Please find the demo link > https://demo.openmf.org/#/viewloanaccount/6172 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-24) Getting internal server error when trying to post repayment for some loans
[ https://issues.apache.org/jira/browse/FINERACT-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-24: - Labels: p3 (was: confirm p3) > Getting internal server error when trying to post repayment for some loans > -- > > Key: FINERACT-24 > URL: https://issues.apache.org/jira/browse/FINERACT-24 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss > Labels: p3 > > https://mifosforge.jira.com/browse/MIFOSX-2373 - see attachments and comments > When trying to post repayment for our loans (plain vanilla installment loans), > we get the following error. This happens in about 10% of cases: > "timestamp": 1449545515301 > "status": 500 > "error": "Internal Server Error" > "exception": "java.lang.ArithmeticException" > "message": "Non-terminating decimal expansion; no exact representable decimal > result." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-24) Getting internal server error when trying to post repayment for some loans
[ https://issues.apache.org/jira/browse/FINERACT-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-24: - Labels: p3 unable (was: p3) > Getting internal server error when trying to post repayment for some loans > -- > > Key: FINERACT-24 > URL: https://issues.apache.org/jira/browse/FINERACT-24 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss > Labels: p3, unable > > https://mifosforge.jira.com/browse/MIFOSX-2373 - see attachments and comments > When trying to post repayment for our loans (plain vanilla installment loans), > we get the following error. This happens in about 10% of cases: > "timestamp": 1449545515301 > "status": 500 > "error": "Internal Server Error" > "exception": "java.lang.ArithmeticException" > "message": "Non-terminating decimal expansion; no exact representable decimal > result." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-36) User defined Templates do not work when Tomcat is behind a proxy
[ https://issues.apache.org/jira/browse/FINERACT-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-36: - Labels: p3 (was: ) > User defined Templates do not work when Tomcat is behind a proxy > > > Key: FINERACT-36 > URL: https://issues.apache.org/jira/browse/FINERACT-36 > Project: Apache Fineract > Issue Type: Bug > Components: System > Environment: Linux, Nginx that proxy passes to Tomcat, OpenJDK7 >Reporter: James Rowe >Assignee: Markus Geiss > Labels: p3 > > Related to https://mifosforge.jira.com/browse/MIFOSX-2322 This issue was > raised by our client and the fix provided did not actually resolve the root > issue. As mentioned in the Environment section, our server is a multitenant > server and has Nginx set up to proxy requests to Tomcat. Because of this > setup though, User defined templates do not work. Looking through the code > (https://github.com/openMF/mifosx/blob/develop/fineract-provider/src/main/java/org/apache/fineract/template/service/TemplateMergeService.java) > I have found out that the TemplateMergeService uses the HTTP API to return > the results for the templates. The issue is it tries to connect to the wrong > port and with the wrong tenant. The tomcat server is running on port 8008 and > 8443 and the template merge service attempts to connect on port 80/433. Nginx > will receive the request and ignore them because of how my routing rules are > set up. Our server is setup to give a subdomain to each tenant and nginx uses > this subdomain name to set the Fineract-Platform-Id header on the request. > Because the API tries to connect on localhost (without any subdomain), the > requests made from the API to the API fail to connect. It doesn't really > matter in the end, since the service grabs the wrong tenant information. I'm > not sure where it gets the tenant identifier from, but it chose "default" as > the tenant when it should have used the name of our client instead. (As a > precaution, our default tenant is a completely empty tenant) > In summary, the TemplateMergeService attempts to make calls to the API, but > fails to ascertain the correct settings to connect to the API. It fails to > choose the correct tenant identifier (uses default, when that is not > correct), connects on the wrong port (80 instead of 8008), and doesn't use > the right server name for the port it connects to. The last two issues are > very related as a proper fix would be to either change the port or change the > server name. I hope this is enough information to write a fix, but if you > need any more information let me know. I'll be glad to help however I can. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-69) Wrong interest amount when using Rounding Mode - Down/Floor for Flat Loans
[ https://issues.apache.org/jira/browse/FINERACT-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-69: - Issue Type: Improvement (was: Bug) > Wrong interest amount when using Rounding Mode - Down/Floor for Flat Loans > -- > > Key: FINERACT-69 > URL: https://issues.apache.org/jira/browse/FINERACT-69 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: George Lteif >Assignee: Markus Geiss > Attachments: screenshot-1.png > > > For organizations using the Floor rounding Mode, the expected behavior is to > have the rounding rules done for the loan schedules and not the total > interest amount > what is currently done in Mifos X is applying the rounding rule on the total > interest amount calculated first which is leading to a loss of profit for the > organization > Scenario: > create a FLAT interest loan product with a monthly 1.3% interest rate > rounding mode is set to Floor > create a loan for the amount of 2900$ over a period of 21 months repayments > (one repayment per month) > expected result would be > 2900*1.3%*21 repayments = 791.7 > it should always be rounded up here regardless of the rounding mode being set > to not lead to any loss of profit > interest calculated in MifosX is 791 (screenshot attaches) > which is a 0.7$ or 1$ less than expected -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (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:all-tabpanel ] Edward Cable updated FINERACT-78: - Labels: p1 (was: ) > 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: confirm, 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.4#6332)
[jira] [Updated] (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:all-tabpanel ] Edward Cable updated FINERACT-78: - Labels: confirm p1 (was: p1) > 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: confirm, 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.4#6332)
[jira] [Updated] (FINERACT-80) Group loans not included in resultset returned by "LoanReadPlatformServiceImpl.retrieveAll" method
[
https://issues.apache.org/jira/browse/FINERACT-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Cable updated FINERACT-80:
-
Labels: p2 (was: )
> Group loans not included in resultset returned by
> "LoanReadPlatformServiceImpl.retrieveAll" method
> --
>
> Key: FINERACT-80
> URL: https://issues.apache.org/jira/browse/FINERACT-80
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Emmanuel Nnaa
>Assignee: Markus Geiss
> Labels: p2
>
> *Replace the following line:*
> {code}
> sqlBuilder.append(" join m_office o on o.id = c.office_id");
> {code}
> *with:*
> {code}
> sqlBuilder.append(" join m_office o on (o.id = c.office_id or o.id =
> g.office_id) ");
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FINERACT-80) Group loans not included in resultset returned by "LoanReadPlatformServiceImpl.retrieveAll" method
[
https://issues.apache.org/jira/browse/FINERACT-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Cable updated FINERACT-80:
-
Issue Type: Improvement (was: Bug)
> Group loans not included in resultset returned by
> "LoanReadPlatformServiceImpl.retrieveAll" method
> --
>
> Key: FINERACT-80
> URL: https://issues.apache.org/jira/browse/FINERACT-80
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: Emmanuel Nnaa
>Assignee: Markus Geiss
> Labels: p2
>
> *Replace the following line:*
> {code}
> sqlBuilder.append(" join m_office o on o.id = c.office_id");
> {code}
> *with:*
> {code}
> sqlBuilder.append(" join m_office o on (o.id = c.office_id or o.id =
> g.office_id) ");
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FINERACT-87) Attache meeting should not get displayed after the meeting is attached to a Group
[ https://issues.apache.org/jira/browse/FINERACT-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-87: - Labels: p3 (was: ) > Attache meeting should not get displayed after the meeting is attached to a > Group > - > > Key: FINERACT-87 > URL: https://issues.apache.org/jira/browse/FINERACT-87 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Markus Geiss > Labels: p3 > Attachments: Attache meeting-2.png > > > Create a Group and attach meeting to it. Even after attaching meeting the > "Attache meeting" field is displaying under more. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FINERACT-87) Attache meeting should not get displayed after the meeting is attached to a Group
[ https://issues.apache.org/jira/browse/FINERACT-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable resolved FINERACT-87. -- Resolution: Fixed Attach meeting option is no longer displayed on demo 3 running 16.12.01 - edit button is available. > Attache meeting should not get displayed after the meeting is attached to a > Group > - > > Key: FINERACT-87 > URL: https://issues.apache.org/jira/browse/FINERACT-87 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Markus Geiss > Labels: p3 > Attachments: Attache meeting-2.png > > > Create a Group and attach meeting to it. Even after attaching meeting the > "Attache meeting" field is displaying under more. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-89) 1st tranche will appear twice in repayment schedule when disbursement date and first repayment date is on same date
[ https://issues.apache.org/jira/browse/FINERACT-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-89: - Labels: confirm p1 (was: ) > 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: confirm, 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.4#6332)
[jira] [Updated] (FINERACT-98) unable to delete a tranche from loan tranche details screen
[ https://issues.apache.org/jira/browse/FINERACT-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-98: - Labels: confirm p1 (was: ) > unable to delete a tranche from loan tranche details screen > --- > > Key: FINERACT-98 > URL: https://issues.apache.org/jira/browse/FINERACT-98 > Project: Apache Fineract > Issue Type: Bug >Reporter: bharath c >Assignee: Markus Geiss > Labels: confirm, p1 > > steps to reproduce: > 1.create a 2 tranche loan > 2.disburse 2 tranches > 3.undo the last tranche using "undo last tranche" option > 4.try to delete the 2nd tranche from "loan tranche details" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-98) unable to delete a tranche from loan tranche details screen
[ https://issues.apache.org/jira/browse/FINERACT-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826040#comment-15826040 ] Edward Cable commented on FINERACT-98: -- This one should be fixed but other issues related to tranches have arisen. > unable to delete a tranche from loan tranche details screen > --- > > Key: FINERACT-98 > URL: https://issues.apache.org/jira/browse/FINERACT-98 > Project: Apache Fineract > Issue Type: Bug >Reporter: bharath c >Assignee: Markus Geiss > Labels: confirm, p1 > > steps to reproduce: > 1.create a 2 tranche loan > 2.disburse 2 tranches > 3.undo the last tranche using "undo last tranche" option > 4.try to delete the 2nd tranche from "loan tranche details" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-99) Waiving of charge results in an incorrect account balance status
[ https://issues.apache.org/jira/browse/FINERACT-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826043#comment-15826043 ] Edward Cable commented on FINERACT-99: -- [~emmanueln...@musoni.eu] Can you please provide reproducible steps and the details of the loan product you have configured. > Waiving of charge results in an incorrect account balance status > > > Key: FINERACT-99 > URL: https://issues.apache.org/jira/browse/FINERACT-99 > Project: Apache Fineract > Issue Type: Bug >Reporter: Emmanuel Nnaa >Assignee: Markus Geiss > Labels: confirm, p1 > > Example affected loan: > - The summary for this loan shows it as active: Contract > Paid, however > Outstanding balance is 0. > - When checking the Transactions the balance is -67 (which suggests overpaid). > - And finally the "Disbursed Loan Report" reports an overdue status with a > balance of 0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-99) Waiving of charge results in an incorrect account balance status
[ https://issues.apache.org/jira/browse/FINERACT-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-99: - Labels: confirm p1 (was: ) > Waiving of charge results in an incorrect account balance status > > > Key: FINERACT-99 > URL: https://issues.apache.org/jira/browse/FINERACT-99 > Project: Apache Fineract > Issue Type: Bug >Reporter: Emmanuel Nnaa >Assignee: Markus Geiss > Labels: confirm, p1 > > Example affected loan: > - The summary for this loan shows it as active: Contract > Paid, however > Outstanding balance is 0. > - When checking the Transactions the balance is -67 (which suggests overpaid). > - And finally the "Disbursed Loan Report" reports an overdue status with a > balance of 0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-105) Issue related to Change future meeting functionality
[ https://issues.apache.org/jira/browse/FINERACT-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-105: -- Labels: confirm p2 (was: ) > Issue related to Change future meeting functionality > > > Key: FINERACT-105 > URL: https://issues.apache.org/jira/browse/FINERACT-105 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Markus Geiss > Labels: confirm, p2 > > 1. If the loan is disbursed on 01 March 2016 and first repayment date is on > 01 April 2016, then it should allow to change future meeting date with in > current system date to 30 April 2016. > > If the future meeting date is set to current system date then first > > repayment should fall on today's date only. > 2. It should not allow to change future meeting date from 01 April 2016 to 01 > May 2016 or beyond that,(beyond immediate next meeting date) and proper error > message should get displayed. > 3. If the future meeting date is changed from 01 April 2016 to today's system > date and again changed to 05 April 2016, then first repayment date should > fall on 05 April 2016. > 4. After change in future meeting date from 01 April 2016 to today's system > date and new loan is disbursed on 01 March 2016 then first repayment date > should fall on today's (current system) date. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FINERACT-106) Not able to change week day in Center meeting with weekly meeting attached, displays Internal server error
[ https://issues.apache.org/jira/browse/FINERACT-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-106: -- Labels: confirm p1 (was: ) > Not able to change week day in Center meeting with weekly meeting attached, > displays Internal server error > -- > > Key: FINERACT-106 > URL: https://issues.apache.org/jira/browse/FINERACT-106 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Markus Geiss > Labels: confirm, p1 > Attachments: Edit Center meeting.png > > > 1. Create a Center with weekly meeting attached from 01 March 2016 and every > week on Friday. > 2. Click on edit meeting and change day in a week as Wednesday and click on > submit button. > > Not able to save the page displays internal server error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
