[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: -- Labels: Volunteer confirm p3 verify (was: Volunteer confirm p3) > 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 >Priority: Major > Labels: Volunteer, confirm, p3, verify > 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 (v7.6.3#76005)
[jira] [Updated] (FINERACT-274) Not able to create the same datatable which was rejected by the maker checker before
[ https://issues.apache.org/jira/browse/FINERACT-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-274: -- Labels: 2019-mifos-gsoc Volunteer gci gsoc p2 verify (was: 2019-mifos-gsoc Volunteer gci gsoc p2) > Not able to create the same datatable which was rejected by the maker checker > before > > > Key: FINERACT-274 > URL: https://issues.apache.org/jira/browse/FINERACT-274 > Project: Apache Fineract > Issue Type: Bug > Components: Data Tables >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, gci, gsoc, p2, verify > Fix For: 1.4.0 > > Attachments: JIRA-274.JPG > > > Posted by Subramanya at [https://mifosforge.jira.com/browse/MIFOSX-1246] > Original Description: > 1. Click on Admin ->System - enable maker-checker. > 2. Click on Admin ->System - Configure maker-checker tasks -> Select > Configurations ->select check box for create, update and delete data tables. > 3. Click on the Admin -> System -> Manage data tables -> Create data table - > and create data table for client. > 4. The navigated page displays "Waiting For Checker Approval" -> Click on > details -> Click on reject button in "View Checker Inbox" -> click on confirm > in confirmation page. > With the above action in UI the data table will not appear, but in the > database the table is still exist. > > Again try to create datable with the same name as above, which displays > error message as the data table already exists, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-302) Principal Threshold (%) for Last Installment is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-302: -- Summary: Principal Threshold (%) for Last Installment is not working as expected (was: Principal Threshold (%) for Last Instalment is not working as expected) > Principal Threshold (%) for Last Installment is not working as expected > --- > > Key: FINERACT-302 > URL: https://issues.apache.org/jira/browse/FINERACT-302 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, fineract-gci, gsoc, p1 > Fix For: 1.5.0 > > Attachments: Scr-664.png, Screenshot from 2018-12-23 22-13-02.png, > Screenshot from 2018-12-23 22-14-34.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2031 > Original Desription: > 1. Create loan product with out mentioning any thing in the "Principal > Threshold (%) for Last Instalment" - by default it is getting set to zero > Instead it should get set to 50% > 2, Create a client and submit new loan application wit the above mentioned > loan product on 01 Jan 2015 with interest recalculation -> Approve and > disburse on same date. > 3. The last installment is getting collected more amount than EMI. > If the "Principal Threshold (%) for Last Instalment" is set to zero then then > the last installment should never be combined with the previous installment > even if the last installment amount is of a very small value. > But here it is displaying the amount>last installment amount -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-305) Dropdowns are using values directly from API instead of using translation
[ https://issues.apache.org/jira/browse/FINERACT-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853715#comment-16853715 ] Edward Cable commented on FINERACT-305: --- [~santoshmath] Can you please make sure this is documented as an issue on Github for the front-end? > Dropdowns are using values directly from API instead of using translation > - > > Key: FINERACT-305 > URL: https://issues.apache.org/jira/browse/FINERACT-305 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, gsoc, p3 > > Reported by Chandrika at https://mifosforge.jira.com/browse/MIFOSX-2081 > Original Description: > For example, the below dropdown uses documenttype.name from API (which is by > default in English language).Instead we should use > translate(documenttype.name) so that the values will be in sync with the > respective language selected by user. > ng-options="documenttype.id as documenttype.name for documenttype in > documenttypes" value="documenttype.id" required="required" > class="form-control"> -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-392) Ability to edit a self guarantor
[ https://issues.apache.org/jira/browse/FINERACT-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853713#comment-16853713 ] Edward Cable commented on FINERACT-392: --- [~mexina] Is this still needed for Singo Africa? Do you still have this requirement? Have you implemented it yet? > Ability to edit a self guarantor > > > Key: FINERACT-392 > URL: https://issues.apache.org/jira/browse/FINERACT-392 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, gsoc, verify > Fix For: 1.5.0 > > > Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2814 > Original Description: > When a self guarantor has been created there is a chance for a user to attach > a wrong saving account or to allocate a wrong amount. For now when that > happens you have to delete a guarantor and create again. It will be helpful > if a user can edit details of a self guarantor and be able to change deposit > account and amount. > You can see this by applying new loan then in the profile of the loan > navigate to more -> create guarantor, then create a guarantor (same client) > attach the saving account and allocate the amount and submit. Then navigate > to more -> view guarantor, there you will be able to see the guarantor with > "view" icon, "View transaction", "delete" icon . > It could be better if there was "Edit" icon too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-391) Fund Management-Delete Enhancement
[ https://issues.apache.org/jira/browse/FINERACT-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853714#comment-16853714 ] Edward Cable commented on FINERACT-391: --- [~mexina] Is this still needed for Singo Africa? Do you still have this requirement? Have you implemented it yet? > Fund Management-Delete Enhancement > -- > > Key: FINERACT-391 > URL: https://issues.apache.org/jira/browse/FINERACT-391 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p3 > Fix For: 1.5.0 > > > Reported by Agness Meena at https://mifosforge.jira.com/browse/MIFOSX-2822 > Go to Admin > Organization > Manage Fund > Once you create a new fund you can only edit it but not deleting it. > Need a Delete button to delete existing fund. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-392) Ability to edit a self guarantor
[ https://issues.apache.org/jira/browse/FINERACT-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-392: -- Labels: 2019-mifos-gsoc Volunteer gsoc verify (was: 2019-mifos-gsoc Volunteer gsoc) > Ability to edit a self guarantor > > > Key: FINERACT-392 > URL: https://issues.apache.org/jira/browse/FINERACT-392 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, gsoc, verify > Fix For: 1.5.0 > > > Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2814 > Original Description: > When a self guarantor has been created there is a chance for a user to attach > a wrong saving account or to allocate a wrong amount. For now when that > happens you have to delete a guarantor and create again. It will be helpful > if a user can edit details of a self guarantor and be able to change deposit > account and amount. > You can see this by applying new loan then in the profile of the loan > navigate to more -> create guarantor, then create a guarantor (same client) > attach the saving account and allocate the amount and submit. Then navigate > to more -> view guarantor, there you will be able to see the guarantor with > "view" icon, "View transaction", "delete" icon . > It could be better if there was "Edit" icon too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-392) Ability to edit a self guarantor
[ https://issues.apache.org/jira/browse/FINERACT-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-392: -- Summary: Ability to edit a self guarantor (was: Ability to edit a self guararntor) > Ability to edit a self guarantor > > > Key: FINERACT-392 > URL: https://issues.apache.org/jira/browse/FINERACT-392 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, gsoc > Fix For: 1.5.0 > > > Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2814 > Original Description: > When a self guarantor has been created there is a chance for a user to attach > a wrong saving account or to allocate a wrong amount. For now when that > happens you have to delete a guarantor and create again. It will be helpful > if a user can edit details of a self guarantor and be able to change deposit > account and amount. > You can see this by applying new loan then in the profile of the loan > navigate to more -> create guarantor, then create a guarantor (same client) > attach the saving account and allocate the amount and submit. Then navigate > to more -> view guarantor, there you will be able to see the guarantor with > "view" icon, "View transaction", "delete" icon . > It could be better if there was "Edit" icon too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-391) Fund Management-Delete Enhancement
[ https://issues.apache.org/jira/browse/FINERACT-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-391: -- Labels: 2019-mifos-gsoc Volunteer gsoc p3 (was: Volunteer gsoc p3) > Fund Management-Delete Enhancement > -- > > Key: FINERACT-391 > URL: https://issues.apache.org/jira/browse/FINERACT-391 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p3 > Fix For: 1.5.0 > > > Reported by Agness Meena at https://mifosforge.jira.com/browse/MIFOSX-2822 > Go to Admin > Organization > Manage Fund > Once you create a new fund you can only edit it but not deleting it. > Need a Delete button to delete existing fund. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-388) Improvement in the characters allowed in the column names of Data tables
[ https://issues.apache.org/jira/browse/FINERACT-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-388: -- Labels: 2019-mifos-gsoc Volunteer gsoc p3 (was: Volunteer gsoc p3) > Improvement in the characters allowed in the column names of Data tables > > > Key: FINERACT-388 > URL: https://issues.apache.org/jira/browse/FINERACT-388 > Project: Apache Fineract > Issue Type: Improvement > Components: Data Tables >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p3 > Attachments: Datatable.png > > > Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2826. > Original Description: > The system when configuring Data tables, in the field of column name it does > not allow some of the characters which it could be better to be allowed. For > instance when you want to call your column "Guarantor's phone number" or "A/C > No" the system through an error because of character ' and / > I would suggest for the system to be able to allow other characters rather > than alpha-numeric only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-392) Ability to edit a self guararntor
[ https://issues.apache.org/jira/browse/FINERACT-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-392: -- Labels: 2019-mifos-gsoc Volunteer gsoc (was: Volunteer gsoc) > Ability to edit a self guararntor > - > > Key: FINERACT-392 > URL: https://issues.apache.org/jira/browse/FINERACT-392 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, gsoc > Fix For: 1.5.0 > > > Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2814 > Original Description: > When a self guarantor has been created there is a chance for a user to attach > a wrong saving account or to allocate a wrong amount. For now when that > happens you have to delete a guarantor and create again. It will be helpful > if a user can edit details of a self guarantor and be able to change deposit > account and amount. > You can see this by applying new loan then in the profile of the loan > navigate to more -> create guarantor, then create a guarantor (same client) > attach the saving account and allocate the amount and submit. Then navigate > to more -> view guarantor, there you will be able to see the guarantor with > "view" icon, "View transaction", "delete" icon . > It could be better if there was "Edit" icon too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-410) Ability to remove On-Hold flag and make the amount available for the client (loan guarantor) for withdrawal
[ https://issues.apache.org/jira/browse/FINERACT-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-410: -- Labels: Volunteer gsoc moreinfo p2 (was: Volunteer gsoc p2) > Ability to remove On-Hold flag and make the amount available for the client > (loan guarantor) for withdrawal > --- > > Key: FINERACT-410 > URL: https://issues.apache.org/jira/browse/FINERACT-410 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, moreinfo, p2 > > When a client guarantees a loan and some amount of his/her savings is put > onHold, he/she can not withdraw this amount till the loan client finishes > his/her loan. NB: I stand to be corrected if i understood his wrongly. > As a manager, i should be able to remove the onhold flag and make the client > to withdraw the amount onHold. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-410) Ability to remove On-Hold flag and make the amount available for the client (loan guarantor) for withdrawal
[ https://issues.apache.org/jira/browse/FINERACT-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-410: -- Summary: Ability to remove On-Hold flag and make the amount available for the client (loan guarantor) for withdrawal (was: Ability to remove On-Hold flag and make the amount available for the client (loan gurantor) for withdrawal) > Ability to remove On-Hold flag and make the amount available for the client > (loan guarantor) for withdrawal > --- > > Key: FINERACT-410 > URL: https://issues.apache.org/jira/browse/FINERACT-410 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > > When a client guarantees a loan and some amount of his/her savings is put > onHold, he/she can not withdraw this amount till the loan client finishes > his/her loan. NB: I stand to be corrected if i understood his wrongly. > As a manager, i should be able to remove the onhold flag and make the client > to withdraw the amount onHold. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-440) Include runningBalance, appUser in m_share_account_transactions table.
[ https://issues.apache.org/jira/browse/FINERACT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-440: -- Labels: 2019-mifos-gsoc Volunteer gci gsoc p2 (was: Volunteer gci gsoc p2) > Include runningBalance, appUser in m_share_account_transactions table. > -- > > Key: FINERACT-440 > URL: https://issues.apache.org/jira/browse/FINERACT-440 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, gci, gsoc, p2 > Fix For: 1.5.0 > > > Include the two parameters runningBalance, appUser in > m_share_account_transactions to be used to generate Share Transaction > Statement. Currently its not posible to generate standard statement since > runningBalance is missing and kind of hard to determine it from current Share > Transaction table -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-441) Ability to Related Accounts i.e Loan Accounts with Guarantors in Client Profile
[ https://issues.apache.org/jira/browse/FINERACT-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853707#comment-16853707 ] Edward Cable commented on FINERACT-441: --- [~courage] and [~rahul.usit12] Let's do a quick design of how this could be implemented to see if it's feasible for Dylan's project. > Ability to Related Accounts i.e Loan Accounts with Guarantors in Client > Profile > --- > > Key: FINERACT-441 > URL: https://issues.apache.org/jira/browse/FINERACT-441 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p2 > > As a Loan Officer, i would like to easy know all accounts related to a client > in client profile with clearly defined relation. > E.g > If an account belongs to a client, the Relationship will be "Principal Owner" > If a client guarantees a loan, the account is shown on his/her profile but > the Relationship will be "Guarantor" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-441) Ability to Related Accounts i.e Loan Accounts with Guarantors in Client Profile
[ https://issues.apache.org/jira/browse/FINERACT-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-441: -- Labels: 2019-mifos-gsoc Volunteer gsoc p2 (was: Volunteer gsoc p2) > Ability to Related Accounts i.e Loan Accounts with Guarantors in Client > Profile > --- > > Key: FINERACT-441 > URL: https://issues.apache.org/jira/browse/FINERACT-441 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p2 > > As a Loan Officer, i would like to easy know all accounts related to a client > in client profile with clearly defined relation. > E.g > If an account belongs to a client, the Relationship will be "Principal Owner" > If a client guarantees a loan, the account is shown on his/her profile but > the Relationship will be "Guarantor" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-442) Add Note/Comment fields to Share Account Transactions
[ https://issues.apache.org/jira/browse/FINERACT-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853706#comment-16853706 ] Edward Cable commented on FINERACT-442: --- [~santoshmath] Please create corresponding ticket in Github Issues for the front-end. > Add Note/Comment fields to Share Account Transactions > - > > Key: FINERACT-442 > URL: https://issues.apache.org/jira/browse/FINERACT-442 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p2 > > As a cashier at a teller, i would like to add custom transaction description > to share account transactions e.g Share Dep - Robert -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-463) Dashboard showing no data for 'Amount Collected for Today' even though there are transactions today
[ https://issues.apache.org/jira/browse/FINERACT-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-463: -- Labels: 2019-mifos-gsoc GSOC Volunteer community-app gci p1 verify (was: GSOC Volunteer community-app gci p1) > Dashboard showing no data for 'Amount Collected for Today' even though there > are transactions today > - > > Key: FINERACT-463 > URL: https://issues.apache.org/jira/browse/FINERACT-463 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, GSOC, Volunteer, community-app, gci, > p1, verify > Fix For: 1.4.0 > > Attachments: dashboard.png > > > Reported by Onyedikachi Nwosu > 1. Create a new office and create a client under the new office. > 2. perform a deposit of 10,000 to a savings account and issued a loan to the > value of 10,000 for the same client. > As can be seen from the attached screenshot, On the dashboard, Amount > Disbursed for Today reflects the 10,000 loan, but the Amount Collected for > Today does not reflect 10,000 savings made. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-442) Add Note/Comment fields to Share Account Transactions
[ https://issues.apache.org/jira/browse/FINERACT-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-442: -- Labels: 2019-mifos-gsoc Volunteer gsoc p2 (was: Volunteer gsoc p2) > Add Note/Comment fields to Share Account Transactions > - > > Key: FINERACT-442 > URL: https://issues.apache.org/jira/browse/FINERACT-442 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p2 > > As a cashier at a teller, i would like to add custom transaction description > to share account transactions e.g Share Dep - Robert -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-461) Need of setting Minimum, Default and Maximum values of principal values as zero in loan product level
[ https://issues.apache.org/jira/browse/FINERACT-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853704#comment-16853704 ] Edward Cable commented on FINERACT-461: --- [~santoshmath] We don't understand why this is a requirement, can you share more details about why this feature is required? > Need of setting Minimum, Default and Maximum values of principal values as > zero in loan product level > - > > Key: FINERACT-461 > URL: https://issues.apache.org/jira/browse/FINERACT-461 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, confirm, gsoc, p2 > Fix For: 1.5.0 > > > Currently(with latest Mifos 12.01.RELEASE), you can set Principal > values(min,default,max) greater than zero. The zero values for principal > value s in product level should be acceptable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-462) Need an option to filter provisioning entries by date
[ https://issues.apache.org/jira/browse/FINERACT-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853703#comment-16853703 ] Edward Cable commented on FINERACT-462: --- [~santoshmath] Can you please make sure corresponding ticket for the community app/web app is created? > Need an option to filter provisioning entries by date > - > > Key: FINERACT-462 > URL: https://issues.apache.org/jira/browse/FINERACT-462 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p2 > > Go to Accounting>Provisioning Entries > There is no option to filter provisioning entries by date. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-462) Need an option to filter provisioning entries by date
[ https://issues.apache.org/jira/browse/FINERACT-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-462: -- Labels: 2019-mifos-gsoc Volunteer gsoc p2 (was: Volunteer gsoc p2) > Need an option to filter provisioning entries by date > - > > Key: FINERACT-462 > URL: https://issues.apache.org/jira/browse/FINERACT-462 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p2 > > Go to Accounting>Provisioning Entries > There is no option to filter provisioning entries by date. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-463) Dashboard showing no data for 'Amount Collected for Today' even though there are transactions today
[ https://issues.apache.org/jira/browse/FINERACT-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-463: -- Summary: Dashboard showing no data for 'Amount Collected for Today' even though there are transactions today (was: Dashboard showing no data for 'Amount Collected for Today' even though there are trasactions today) > Dashboard showing no data for 'Amount Collected for Today' even though there > are transactions today > - > > Key: FINERACT-463 > URL: https://issues.apache.org/jira/browse/FINERACT-463 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: GSOC, Volunteer, community-app, gci, p1 > Fix For: 1.4.0 > > Attachments: dashboard.png > > > Reported by Onyedikachi Nwosu > 1. Create a new office and create a client under the new office. > 2. perform a deposit of 10,000 to a savings account and issued a loan to the > value of 10,000 for the same client. > As can be seen from the attached screenshot, On the dashboard, Amount > Disbursed for Today reflects the 10,000 loan, but the Amount Collected for > Today does not reflect 10,000 savings made. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-471) Preview feature for uploaded document
[ https://issues.apache.org/jira/browse/FINERACT-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-471: -- Labels: 2019-mifos-gsoc Volunteer gsoc p2 (was: Volunteer gsoc p2) > Preview feature for uploaded document > - > > Key: FINERACT-471 > URL: https://issues.apache.org/jira/browse/FINERACT-471 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization, System >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p2 > Fix For: 1.5.0 > > > Enhance Request by Boniphace Fredrick > Original Description: > Currently the system allows to upload a document and once you want to view it > again there is only one option ie, to download it. > This act can probably violate client's privacy( ie, client information > vulnerability) for example if a user(eg. Loan officer) uses somebody computer > to access system, so there is possibility he/she can download a document and > forget to delete if from that local machine > Therefore I suggest there should first an option to preview the document fist > maybe as a pdf and then a user can choose either to download, print or just > view it only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-484) In Mifos report 'Client Loan Schedule', it does not indicate the amounts paid by the client, only shows the loan balance. Ideally the client would be interested to see
[ https://issues.apache.org/jira/browse/FINERACT-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-484: -- Labels: Volunteer review (was: Volunteer) > In Mifos report 'Client Loan Schedule', it does not indicate the amounts paid > by the client, only shows the loan balance. Ideally the client would be > interested to see how much interest and principal has been paid > - > > Key: FINERACT-484 > URL: https://issues.apache.org/jira/browse/FINERACT-484 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Alex Mbatha >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, review > Attachments: screenshot-1.png, screenshot-2.png > > > In Mifos report 'Client Loan Schedule', it does not indicate the amounts paid > by the client, only shows the loan balance. Ideally the client would be > interested to see how much interest and principal has been paid. Kindly > include this. > Regards, > Alex -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-505) Loan Tranche Details should be captured in Bulk JLG loan application.
[ https://issues.apache.org/jira/browse/FINERACT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-505: -- Labels: 2019-mifos-gsoc Volunteer gsoc p2 (was: Volunteer gsoc p2) > Loan Tranche Details should be captured in Bulk JLG loan application. > - > > Key: FINERACT-505 > URL: https://issues.apache.org/jira/browse/FINERACT-505 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p2 > Fix For: Backlog > > > Presently, there is no fields to capture multi-tranche details in 'Bulk JLG > loan application' . Therefore, Bulk JLG loan application doesn't support > multi-tranche loan products. The current temperory fix is, the loan products > with multi-tranche aren't displaying in drop-down menu of 'Bulk JLG loan > application'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-528) After taking survey for a client, Survey is displaying score of each question in stead of total score of each survey
[ https://issues.apache.org/jira/browse/FINERACT-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-528: -- Labels: 2019-mifos-gsoc GSOC Volunteer gsoc p1 (was: GSOC Volunteer gsoc p1) > After taking survey for a client, Survey is displaying score of each question > in stead of total score of each survey > > > Key: FINERACT-528 > URL: https://issues.apache.org/jira/browse/FINERACT-528 > Project: Apache Fineract > Issue Type: Improvement > Components: Client, Surveys >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: 2019-mifos-gsoc, GSOC, Volunteer, gsoc, p1 > Fix For: 1.5.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-643) Journal Entries are not filterable by type of entry: system
[ https://issues.apache.org/jira/browse/FINERACT-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-643: -- Labels: 2019-mifos-gsoc GSOC Volunteer gci p2 (was: GSOC Volunteer gci p2) > Journal Entries are not filterable by type of entry: system > --- > > Key: FINERACT-643 > URL: https://issues.apache.org/jira/browse/FINERACT-643 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Major > Labels: 2019-mifos-gsoc, GSOC, Volunteer, gci, p2 > Fix For: 1.5.0 > > > Related Front -End Issue: > https://github.com/openMF/web-app/issues/236 > As a developer, I am unable to implement the filter for Journal Entries by > type of entry: system, as the only parameter available to filter entries by > type is manualEntriesOnly which filters manual entries (as clear from its > name). There is no way to filter system entries from server-side. > (similar issue in community-app) > Due to a large number of entries in database (over 8), its essential to > implement it from server-side because the default implementation of sending a > HTTP request to get all the entries at once and implementing the logic on > client-side will be too costly for people with slow internet connections. > > Refer: [https://demo.openmf.org/api-docs/apiLive.htm#journalentries_list] > Expected Behaviour: > Journal Entries should be filterable by type of entry: system apart from the > manual as well from the server-side so that it can be implemented on the > client side. > h2. Actual Behaviour > Journal Entries are not filterable by type of entry: system from the > server-side due to which filter by type of entry cannot be implemented > properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-677) Hide Sensitive contents in xml files and logs
[ https://issues.apache.org/jira/browse/FINERACT-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-677: -- Labels: 2019-mifos-gsoc p1 (was: p1) > Hide Sensitive contents in xml files and logs > - > > Key: FINERACT-677 > URL: https://issues.apache.org/jira/browse/FINERACT-677 > Project: Apache Fineract > Issue Type: Bug > Environment: All environments, Linux/Unix and Windows. >Reporter: ApacheSF User >Priority: Major > Labels: 2019-mifos-gsoc, p1 > Fix For: 1.4.0 > > > This is an issue explaining about hiding sensitive issues in xml files. > These files include. > Usernames & passwords in: > tomcat/conf/server.xml > Mifos system username and password are visible in : > tomcat/logs/localhost_access_log.2018-12-07 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-726) Changes to /authentication API's to pass data as part of request body
[
https://issues.apache.org/jira/browse/FINERACT-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Cable updated FINERACT-726:
--
Labels: 2019-mifos-gsoc gsoc p1 volunteer (was: gsoc p1 volunteer)
> Changes to /authentication API's to pass data as part of request body
> -
>
> Key: FINERACT-726
> URL: https://issues.apache.org/jira/browse/FINERACT-726
> Project: Apache Fineract
> Issue Type: Improvement
>Affects Versions: 1.2.0
>Reporter: Vishwas Babu A J
>Priority: Major
> Labels: 2019-mifos-gsoc, gsoc, p1, volunteer
> Fix For: 1.4.0
>
>
> Fineract supports authentication either using Basic auth or Oauth. The
> initial authentication is done using the endpoints described at
> [https://demo.openmf.org/api-docs/apiLive.htm#authentication_basicauth] and
> [https://demo.openmf.org/api-docs/apiLive.htm#authentication_oauth]
> Both rely on passing the username and password as URL query parameters.
> Ex, the endpoint for /authentication is
> POST :
> [https://localhost:8443/fineract-provider/api/v1/authentication?username=mifos=password=default]
>
> We would want to change the same to
> POST
> [https://localhost:8443/fineract-provider/api/v1/authentication?tenantIdentifier=default]
> and pass the username and password as apart of the post body in json format.
> Ex:
> {code:java}
> {
> "username":"mifos",
> "password":"password"
> }{code}
>
> After making this change, the APIdocs and integration test cases would have
> to be updated accordingly
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FINERACT-701) In Individual Collection sheet and Collection Sheet, Not able to select previous year dates(2018) through date picker.
[ https://issues.apache.org/jira/browse/FINERACT-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-701: -- Labels: GSOC Volunteer review (was: GSOC Volunteer p1) > In Individual Collection sheet and Collection Sheet, Not able to select > previous year dates(2018) through date picker. > -- > > Key: FINERACT-701 > URL: https://issues.apache.org/jira/browse/FINERACT-701 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Critical > Labels: GSOC, Volunteer, review > Fix For: 1.4.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-26) Allow a Logo (for Organization) to be set, which will be displayed on the header
[ https://issues.apache.org/jira/browse/FINERACT-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-26: - Labels: 2019-mifos-gsoc gsoc p1 (was: gsoc p1) > Allow a Logo (for Organization) to be set, which will be displayed on the > header > > > Key: FINERACT-26 > URL: https://issues.apache.org/jira/browse/FINERACT-26 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Minor > Labels: 2019-mifos-gsoc, gsoc, p1 > Fix For: 1.4.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2511 > As a Implementation Specialist, I wish to setup a logo (for the organization) > which will be displayed before the Mifos logo > As a first step : there is no user interface needed for uploading the logo. > As a second step : we can provide user interface for logo-upload > Logo can be different for different tenants (in a multi-tenant setup). > Logo should be same size as Mifos X logo - to maintain aesthetics of the > header band. > Part 2 ] While we are at it, we should probably also allow themes to be > picked on on a per tenant basis -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-176) During allocation and settle cash for a cashier if valid inputs are not given then error message displayed as Unknown data integrity issue
[ https://issues.apache.org/jira/browse/FINERACT-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-176: -- Labels: 2019-mifos-gsoc Volunteer gsoc p3 (was: Volunteer gsoc p3) > During allocation and settle cash for a cashier if valid inputs are not given > then error message displayed as Unknown data integrity issue > -- > > Key: FINERACT-176 > URL: https://issues.apache.org/jira/browse/FINERACT-176 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p3 > Fix For: 1.5.0 > > Attachments: AllocationorSettle cash.png > > > 1. Create teller and create a cashier for that teller. > 2. Click on allocate/settle cash > > Do not enter any values and click on submit button - > > "error.msg.teller.unknown.data.integrity.issue" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-225) If Loan rescheduling page is submitted with out checking any checkboxes then error message displayed is not proper
[ https://issues.apache.org/jira/browse/FINERACT-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-225: -- Labels: 2019-mifos-gsoc Volunteer gsoc p2 (was: Volunteer gsoc p2) > If Loan rescheduling page is submitted with out checking any checkboxes then > error message displayed is not proper > -- > > Key: FINERACT-225 > URL: https://issues.apache.org/jira/browse/FINERACT-225 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Markus Geiss >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p2 > Fix For: 1.5.0 > > Attachments: Reschedule loan.png > > > Error message displayed as > "validation.msg.rescheduleloan.graceOnPrincipal.cannot.be.blank" if no check > box is checked. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-231) Error message displayed is not proper if the valid Center/Group is not selected for generation of collection sheet
[ https://issues.apache.org/jira/browse/FINERACT-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-231: -- Labels: 2019-mifos-gsoc Volunteer gsoc p2 (was: Volunteer gsoc p2) > Error message displayed is not proper if the valid Center/Group is not > selected for generation of collection sheet > -- > > Key: FINERACT-231 > URL: https://issues.apache.org/jira/browse/FINERACT-231 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Markus Geiss >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p2 > Fix For: 1.5.0 > > > 1. Create a loan product, Create a Center and attache Group to it, Attache > weekly meeting from 01 June 2016 on friday. > 2. Create a client under above group and attache JLG loan on 01 June 2016 > with synk repayment with meeting. > 3. Approve and disburse the loan > 4. Click on the collection sheet and enter meeting calendar as 10 June 2016 > and click on generate collection sheet, > error message displayed as "Collection sheet cannot be generated for > center/group without attach meeting define" though the meting date is valid. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-244) New Repayment Schedule Not Populating
[ https://issues.apache.org/jira/browse/FINERACT-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-244: -- Labels: Volunteer confirm gsoc (was: Volunteer gsoc p3) > New Repayment Schedule Not Populating > - > > Key: FINERACT-244 > URL: https://issues.apache.org/jira/browse/FINERACT-244 > Project: Apache Fineract > Issue Type: Bug >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, confirm, gsoc > Fix For: 1.5.0 > > > Mifos - View Loan Account - More Drop Down - Reschedule > After complete Reschedule Loan Screen - Press Submit > View Loan reschedule request - then select View new Repayment Schedule > New Repayment Schedule Screen does not populate any information for > verification prior to accepting the change. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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:
--
Labels: 2019-mifos-gsoc Volunteer fineract-gci gsoc p2 (was: Volunteer
fineract-gci gsoc p2)
> "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
>Affects Versions: 1.1.0
>Reporter: Edward Cable
>Assignee: Markus Geiss
>Priority: Minor
> Labels: 2019-mifos-gsoc, Volunteer, fineract-gci, gsoc, p2
> Fix For: 1.4.0
>
>
> 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
(v7.6.3#76005)
[jira] [Updated] (FINERACT-478) Savings overdraft fee with charge time type 'overdraft fee' and charge calculation '%amount' is not working
[ https://issues.apache.org/jira/browse/FINERACT-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-478: -- Labels: 2019-mifos-gsoc gsoc p1 (was: gsoc p1) > Savings overdraft fee with charge time type 'overdraft fee' and charge > calculation '%amount' is not working > --- > > Key: FINERACT-478 > URL: https://issues.apache.org/jira/browse/FINERACT-478 > Project: Apache Fineract > Issue Type: Bug > Components: Charges, Savings >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: 2019-mifos-gsoc, gsoc, p1 > Fix For: 1.4.0 > > > 1. Go to charges and select charge applied to 'Savings and deposits' > 2. Fill other required inputs with > Charge Time type: overdraft fee > Charge calculation : % amount. > Amount : 1 > > After submission , it is throwing error: > > "validation.msg.charges.charge.calculation.type.percentage.allowed.only.for.withdrawal.or.noactivity" > Expected: > 1.This feature of overdraft fee with charge calculation as % amount need to > be implemented. > 2. Until the feature is implemented, the following proper error message > should be thrown in stead of above mentioned: > ""validation.msg: > charge.calculation.type.percentage.allowed.only.for.withdrawal.or.noactivityand > yet to be implemented for overdraft fee" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-520) The field for "is staff" in the client creation does not store data
[ https://issues.apache.org/jira/browse/FINERACT-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-520: -- Labels: 2019-mifos-gsoc Volunteer client gci gsoc p2 (was: GSOC Volunteer client gci gsoc p2) > The field for "is staff" in the client creation does not store data > > > Key: FINERACT-520 > URL: https://issues.apache.org/jira/browse/FINERACT-520 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Mexina Daniel >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, client, gci, gsoc, p2 > Fix For: 1.5.0 > > > When you create a client and select the field "is staff", it is selected but > after submission and come again to edit, you find the field not selected, > which shows the value was not stored. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-592) Undo a charge waive
[ https://issues.apache.org/jira/browse/FINERACT-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-592: -- Labels: confirm gsoc p2 (was: gsoc p2) > Undo a charge waive > --- > > Key: FINERACT-592 > URL: https://issues.apache.org/jira/browse/FINERACT-592 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Jan Antonie Peens >Assignee: Markus Geiss >Priority: Minor > Labels: confirm, gsoc, p2 > > Reverse a charge waiver. > We have gotten the situation were a charge was waived by accident and we > would therefore like to undo the mistake. > Would such a feature be possible? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-591) Partialy waive a charge
[ https://issues.apache.org/jira/browse/FINERACT-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-591: -- Labels: confirm gci gsoc p2 (was: gci gsoc p2) > Partialy waive a charge > --- > > Key: FINERACT-591 > URL: https://issues.apache.org/jira/browse/FINERACT-591 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Jan Antonie Peens >Assignee: Markus Geiss >Priority: Minor > Labels: confirm, gci, gsoc, p2 > > Would it be possible to waive a certain amount of a loan charge. > For example, for the second installment of a loan we wish to waive 50% of a > service charge as a client incentive. The monthly service charge is $2, so > therefore we want to waive $1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-594) Recent Transactions Only Displays Charges, It should show savings and loan transitions too
[ https://issues.apache.org/jira/browse/FINERACT-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-594: -- Labels: 2019-mifos-gsoc GSOC Volunteer easyfix enha patch (was: GSOC Volunteer easyfix enha patch) > Recent Transactions Only Displays Charges, It should show savings and loan > transitions too > --- > > Key: FINERACT-594 > URL: https://issues.apache.org/jira/browse/FINERACT-594 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Charges, Loan, Savings >Affects Versions: 1.0.0 >Reporter: Rajan Maurya >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, GSOC, Volunteer, easyfix, enha, patch > Fix For: 1.4.0 > > Original Estimate: 96h > Remaining Estimate: 96h > > Recent Transactions of the self-service user Only Displays Charges but It > should show savings and loan transitions too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-595) Should allow user to specify an account nickname
[ https://issues.apache.org/jira/browse/FINERACT-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-595: -- Labels: 2019-mifos-gsoc Volunteer confirm gsoc p2 patch (was: Volunteer confirm gsoc p2 patch) > Should allow user to specify an account nickname > > > Key: FINERACT-595 > URL: https://issues.apache.org/jira/browse/FINERACT-595 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan, Savings >Affects Versions: 1.1.0 >Reporter: Rajan Maurya >Assignee: Shaik Nazeer Hussain >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, confirm, gsoc, p2, patch > Fix For: 1.5.0 > > > *Summary:* > For users to be able to quickly identify their accounts when doing transfers > or payments, we should allow them to specify an account nickname. > We would have to decide if the account nickname is just stored locally in the > app on the device or if the account nickname would be stored at the platform > level for Apache Fineract. > Storing it the Apache Fineract level, would allow the user to have account > nickname persist across the mobile and online banking apps. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-609) Top loan is not working for Group loans
[ https://issues.apache.org/jira/browse/FINERACT-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853309#comment-16853309 ] Edward Cable commented on FINERACT-609: --- [~santoshmath] can you please provide more details here so we can understand if it's in scope for [~DylanRobson] to work on for GSOC > Top loan is not working for Group loans > > > Key: FINERACT-609 > URL: https://issues.apache.org/jira/browse/FINERACT-609 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.0.0 >Reporter: Santosh Math >Priority: Major > Labels: gsoc, p1, volunteers > > # Create a loan product with top up enabled. > # Take a group loan and disburse it. > # Take another group loan application , Check 'Is top loan' and try to > select previous loan account. Previously created loan account is not > displaying. > Top up loan is working fine client level loan application. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-612) Interest Calculation for partial early payment is incorrect
[ https://issues.apache.org/jira/browse/FINERACT-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-612: -- Labels: 2019-mifos-gsoc gsoc p2 (was: gsoc p2) > Interest Calculation for partial early payment is incorrect > --- > > Key: FINERACT-612 > URL: https://issues.apache.org/jira/browse/FINERACT-612 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.0.0 > Environment: https://demo.openmf.org/#/viewloanaccount/2522 >Reporter: Marcell >Priority: Major > Labels: 2019-mifos-gsoc, gsoc, p2 > > Loan Configuration : > Interest : 32.04% / year > Loan term 150 Days > Repayment : 1x > Disburse date : 4 Oct 2017 > Mature Date : 3 Mar 2018 > Loan Amount : 85,000,000 > > 1st early repayment > Date : 25 Jan 2018 > Amount : 9,000,000 > Expected allocated paid to interest : 113 Days x (32.04%/360) = 8,548,450 > Expected allocated paid to pricipal : 9,000,000 - 8,548,450 = 451,550 > However, Mifos allocate all payment into interest > https://demo.openmf.org/#/viewloanaccount/2522 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-631) Allow to specify transfer date when transferring client from one branch to another
[ https://issues.apache.org/jira/browse/FINERACT-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-631: -- Labels: 2019-mifos-gsoc gsoc p2 (was: gsoc p2) > Allow to specify transfer date when transferring client from one branch to > another > -- > > Key: FINERACT-631 > URL: https://issues.apache.org/jira/browse/FINERACT-631 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Mexina Daniel >Priority: Major > Labels: 2019-mifos-gsoc, gsoc, p2 > > Then transferring the client from one branch to another, the system take the > current data and assume its a transfer date, the system should allow a user > to specify, sometimes it might be a back date. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-641) Withdrawal fee support for overdrawing account
[ https://issues.apache.org/jira/browse/FINERACT-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853299#comment-16853299 ] Edward Cable commented on FINERACT-641: --- [~santoshmath] I think this would be a good fit for Dylan. Since you're original reporter, could you provide a few more details on what needs to be supported and how this should work? > Withdrawal fee support for overdrawing account > --- > > Key: FINERACT-641 > URL: https://issues.apache.org/jira/browse/FINERACT-641 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Major > Labels: 2019-mifos-gsoc, GSOC, Volunteer, p1 > Fix For: 1.5.0 > > Original Estimate: 72h > Remaining Estimate: 72h > > Currently, Savings Withdrawal fee only applicable if withdrawal is done when > balance is greater than zero. > If try to overdraw from savings account, withdrawal fee won't support and > it's throwing the error. > Expected: Withdrawal fee should support overdrawn account . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-641) Withdrawal fee support for overdrawing account
[ https://issues.apache.org/jira/browse/FINERACT-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-641: -- Labels: 2019-mifos-gsoc GSOC Volunteer p1 (was: GSOC Volunteer p1) > Withdrawal fee support for overdrawing account > --- > > Key: FINERACT-641 > URL: https://issues.apache.org/jira/browse/FINERACT-641 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Major > Labels: 2019-mifos-gsoc, GSOC, Volunteer, p1 > Fix For: 1.5.0 > > Original Estimate: 72h > Remaining Estimate: 72h > > Currently, Savings Withdrawal fee only applicable if withdrawal is done when > balance is greater than zero. > If try to overdraw from savings account, withdrawal fee won't support and > it's throwing the error. > Expected: Withdrawal fee should support overdrawn account . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-689) Able to Create Fixed Deposit/Recurring Deposit product without adding Interest Rate Chart
[ https://issues.apache.org/jira/browse/FINERACT-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-689: -- Labels: 2019-mifos-gsoc GSOC Volunteer p1 (was: GSOC Volunteer p1) > Able to Create Fixed Deposit/Recurring Deposit product without adding > Interest Rate Chart > -- > > Key: FINERACT-689 > URL: https://issues.apache.org/jira/browse/FINERACT-689 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.2.0 >Reporter: Santosh Math >Priority: Critical > Labels: 2019-mifos-gsoc, GSOC, Volunteer, p1 > Fix For: 1.4.0 > > Time Spent: 50m > Remaining Estimate: 0h > > 1) Go to Admin>Products and select either Fixed Deposit Products or Recurring > Deposit Products and then click on Create Fixed Deposit Product/Recurring > Deposit Product. > 2) Give all mandatory inputs and under 'Interest Rate Chart' provide 'Valid > From Date' and then just submit it without adding interest rate. > > Able to Submit and create FD/RD product without interest rate chart. > Expected: Validation should be thrown 'Interest Rate is not added' , once > submit button is hit. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-690) Global configuration to disallow the change of overdue charges on a loan product to affect the already created loans.
[ https://issues.apache.org/jira/browse/FINERACT-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853294#comment-16853294 ] Edward Cable commented on FINERACT-690: --- [~mexina] could you provide some more details on what you needed for this feature request? > Global configuration to disallow the change of overdue charges on a loan > product to affect the already created loans. > - > > Key: FINERACT-690 > URL: https://issues.apache.org/jira/browse/FINERACT-690 > Project: Apache Fineract > Issue Type: New Feature > Components: Charges, Loan >Reporter: Mexina Daniel >Priority: Major > Labels: 2019-mifos-gsoc, GSoC > Fix For: 1.5.0 > > > For now when you attach an overdue charge to a loan product which did not > have previously, it affect the active loans that were created without a > penalty. > Am suggesting for the system to have a configuration to allow are disallow > this feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-652) Deliver status is not getting updated to 'Delivered' (status:300) even message is delivered to the mobile
[ https://issues.apache.org/jira/browse/FINERACT-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-652: -- Labels: 2019-mifos-gsoc GSOC Volunteer p1 (was: GSOC Volunteer p1) > Deliver status is not getting updated to 'Delivered' (status:300) even > message is delivered to the mobile > -- > > Key: FINERACT-652 > URL: https://issues.apache.org/jira/browse/FINERACT-652 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: 2019-mifos-gsoc, GSOC, Volunteer, p1 > Fix For: 1.4.0 > > > The following are the sms status: > Pending: 100 > Waiting for Delivery Report: 150 > Sent sms: 200 > Delivered sms: 300 > Failed sms: 400 > Even sms is delivered to given mobile number the status in the database is > not getting updating from 150 to 300. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-690) Global configuration to disallow the change of overdue charges on a loan product to affect the already created loans.
[ https://issues.apache.org/jira/browse/FINERACT-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-690: -- Labels: 2019-mifos-gsoc GSoC (was: GSoC) > Global configuration to disallow the change of overdue charges on a loan > product to affect the already created loans. > - > > Key: FINERACT-690 > URL: https://issues.apache.org/jira/browse/FINERACT-690 > Project: Apache Fineract > Issue Type: New Feature > Components: Charges, Loan >Reporter: Mexina Daniel >Priority: Major > Labels: 2019-mifos-gsoc, GSoC > Fix For: 1.5.0 > > > For now when you attach an overdue charge to a loan product which did not > have previously, it affect the active loans that were created without a > penalty. > Am suggesting for the system to have a configuration to allow are disallow > this feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-614) Creation of sub rates
[ https://issues.apache.org/jira/browse/FINERACT-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable reassigned FINERACT-614: - Assignee: Edward Cable > Creation of sub rates > - > > Key: FINERACT-614 > URL: https://issues.apache.org/jira/browse/FINERACT-614 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.1.0 >Reporter: Angel Cajas >Assignee: Edward Cable >Priority: Minor > Labels: external, p2 > Fix For: 1.4.0 > > > Nominal interest rate for loans can be composed of previously defined > interest rates, When a new loan product or loan account is created you can > choose which rates should apply for the loan. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-462) Need an option to filter provisioning entries by date
[ https://issues.apache.org/jira/browse/FINERACT-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-462: -- Labels: Volunteer gsoc p2 (was: gsoc p2) > Need an option to filter provisioning entries by date > - > > Key: FINERACT-462 > URL: https://issues.apache.org/jira/browse/FINERACT-462 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > > Go to Accounting>Provisioning Entries > There is no option to filter provisioning entries by date. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-433) Transactions done by cashier for one teller is replicating in other teller with same cashier but different time duration.
[ https://issues.apache.org/jira/browse/FINERACT-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791162#comment-16791162 ] Edward Cable commented on FINERACT-433: --- [~santoshmath] Does the title now properly reflect the remaining scope of the issue? > Transactions done by cashier for one teller is replicating in other teller > with same cashier but different time duration. > - > > Key: FINERACT-433 > URL: https://issues.apache.org/jira/browse/FINERACT-433 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: GSOC, gci, p2, volunteer > Fix For: 1.4.0 > > > 1. Create a 'Teller 1' with 'cashier A' with time duration 9am to 1pm. > 2. Create another 'Teller 2', with same 'cashier A' and time duration 2pm to > 5pm > 3. Create an user with employee as 'cashier A' with valid credentials and > permissions. > 4. Login with the credentials of the user for cashier A and do all > disbursements and repayments,etc. for the time duration between 9am to 1pm > >If you check the transactions for Teller 1 and Teller 2, both have same > >transactions though same cashier is assigned with different time duration. > > The transactions done by cashier for specific teller(say Teller 1) at > > specific time duration must be highlighted only to that teller , not in > > other teller . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-471) Preview feature for uploaded document
[ https://issues.apache.org/jira/browse/FINERACT-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-471: -- Labels: Volunteer gsoc p2 (was: gsoc p2) > Preview feature for uploaded document > - > > Key: FINERACT-471 > URL: https://issues.apache.org/jira/browse/FINERACT-471 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization, System >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > > Enhance Request by Boniphace Fredrick > Original Description: > Currently the system allows to upload a document and once you want to view it > again there is only one option ie, to download it. > This act can probably violate client's privacy( ie, client information > vulnerability) for example if a user(eg. Loan officer) uses somebody computer > to access system, so there is possibility he/she can download a document and > forget to delete if from that local machine > Therefore I suggest there should first an option to preview the document fist > maybe as a pdf and then a user can choose either to download, print or just > view it only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-471) Preview feature for uploaded document
[ https://issues.apache.org/jira/browse/FINERACT-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-471: -- Fix Version/s: 1.5.0 > Preview feature for uploaded document > - > > Key: FINERACT-471 > URL: https://issues.apache.org/jira/browse/FINERACT-471 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization, System >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > Fix For: 1.5.0 > > > Enhance Request by Boniphace Fredrick > Original Description: > Currently the system allows to upload a document and once you want to view it > again there is only one option ie, to download it. > This act can probably violate client's privacy( ie, client information > vulnerability) for example if a user(eg. Loan officer) uses somebody computer > to access system, so there is possibility he/she can download a document and > forget to delete if from that local machine > Therefore I suggest there should first an option to preview the document fist > maybe as a pdf and then a user can choose either to download, print or just > view it only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-410) Ability to remove On-Hold flag and make the amount available for the client (loan gurantor) for withdrawal
[ https://issues.apache.org/jira/browse/FINERACT-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791156#comment-16791156 ] Edward Cable commented on FINERACT-410: --- [~vishwasbabu] Could you reply to my previous comment on this? > Ability to remove On-Hold flag and make the amount available for the client > (loan gurantor) for withdrawal > -- > > Key: FINERACT-410 > URL: https://issues.apache.org/jira/browse/FINERACT-410 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > > When a client guarantees a loan and some amount of his/her savings is put > onHold, he/she can not withdraw this amount till the loan client finishes > his/her loan. NB: I stand to be corrected if i understood his wrongly. > As a manager, i should be able to remove the onhold flag and make the client > to withdraw the amount onHold. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-461) Need of setting Minimum, Default and Maximum values of principal values as zero in loan product level
[ https://issues.apache.org/jira/browse/FINERACT-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-461: -- Labels: Volunteer gsoc p2 (was: gsoc p2) > Need of setting Minimum, Default and Maximum values of principal values as > zero in loan product level > - > > Key: FINERACT-461 > URL: https://issues.apache.org/jira/browse/FINERACT-461 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, gsoc, p2 > > Currently(with latest Mifos 12.01.RELEASE), you can set Principal > values(min,default,max) greater than zero. The zero values for principal > value s in product level should be acceptable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-461) Need of setting Minimum, Default and Maximum values of principal values as zero in loan product level
[ https://issues.apache.org/jira/browse/FINERACT-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-461: -- Fix Version/s: 1.5.0 > Need of setting Minimum, Default and Maximum values of principal values as > zero in loan product level > - > > Key: FINERACT-461 > URL: https://issues.apache.org/jira/browse/FINERACT-461 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, gsoc, p2 > Fix For: 1.5.0 > > > Currently(with latest Mifos 12.01.RELEASE), you can set Principal > values(min,default,max) greater than zero. The zero values for principal > value s in product level should be acceptable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-409) Improvement to min_required_balance: Make minimum balance for all savings accounts global
[ https://issues.apache.org/jira/browse/FINERACT-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-409: -- Labels: Volunteer gsoc p3 (was: gsoc p3 volunteers) > Improvement to min_required_balance: Make minimum balance for all savings > accounts global > - > > Key: FINERACT-409 > URL: https://issues.apache.org/jira/browse/FINERACT-409 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p3 > > Currently when you have created savings account for a product, the minimum > balance for that product is one capture and entered in min_required_balance > for this savings account. Now if you change the minimum balance for this > product, accounts already created are not affected by this changes i.e > min_required_balance is not updated for the accounts in existence. > Any changes in min required balance should affect all accounts of that > product i.e those accounts already created and those yet to be created. This > will make sense and will be fair to all clients -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-424) SELF-SERVICE: store 4 digit pin on back-end
[ https://issues.apache.org/jira/browse/FINERACT-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791160#comment-16791160 ] Edward Cable commented on FINERACT-424: --- [~vishwasbabu] Should I close my previous request as invalid? I think it's more standard practice that the four digit pin is only on the device correct? for most of my banking apps taht require the four-digit pin code, I have to create it again each time I am fully logged out of the app and it's a code I use per device so there wouldn't be a need to share across multiple devices. > SELF-SERVICE: store 4 digit pin on back-end > --- > > Key: FINERACT-424 > URL: https://issues.apache.org/jira/browse/FINERACT-424 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Edward Cable >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p3 > > First off, in order to make it easier for a user to log in and not have to > fully authenticate themselves each time they leave the self-service app, we > wanted to enable a 4 digit pin code that could be used to log in to the app > (once fully authenticated for a first time). This is pretty standard practice > in banking apps. > We didn't want to store that locally since it wouldn't be secure on phones > that are rooted. > With that constraint, we need to be able to store this pin on the back-end - > then it can also be shared across phones as well. > See https://github.com/openMF/self-service-app/issues/115 and > https://github.com/openMF/self-service-app/issues/132 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-405) Client/Staff SMS phone number back-end validation, incl. default country code
[ https://issues.apache.org/jira/browse/FINERACT-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-405: -- Fix Version/s: 1.5.0 > Client/Staff SMS phone number back-end validation, incl. default country code > - > > Key: FINERACT-405 > URL: https://issues.apache.org/jira/browse/FINERACT-405 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Trivial > Labels: gsoc, p2 > Fix For: 1.5.0 > > > Reported by [~vorburger] at https://mifosforge.jira.com/browse/MIFOSX-779 > Original Description: > We'll likely start with just using String / VARCHAR as type for SMS phone > numbers in client/staff, but in order get serious about SMS support, the > "data quality" of those will quickly be fairly import. > Therefore, it would probably be very useful if the platform technically > enforced that such phone numbers are always represented and stored in the > database including country code prefix (using the +91 ... notation). > The should also have some validation logic in the UI enforcing this > (FrontlineSMS says: "This number is not in international format. This may > cause problems matching messages to contacts."). > The UI could assist in making it easier to capture phone numbers and propose > a default country code saved in some System Administration configuration > somewhere when entering new phone numbers. > The Java back-end could use some proper strongly typed self validating > PhoneNumber value object type, instead of just passing around String? May be > something like this exists already? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-419) Non-Person Client codes can not be updated to blank
[ https://issues.apache.org/jira/browse/FINERACT-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791157#comment-16791157 ] Edward Cable commented on FINERACT-419: --- [~santoshmath] Can you please re-test? > Non-Person Client codes can not be updated to blank > --- > > Key: FINERACT-419 > URL: https://issues.apache.org/jira/browse/FINERACT-419 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Reporter: Brian C Cooke >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p2 > > Steps to reproduce: > 1. Create a client with Legal Form=Entity and assign this client a value from > the Main Business Line. Save. > 2. Edit this client and try to remove Main Business Line (assign back to > --Select Main Business Line). Save. > 3. Edit again and observe Main Business Line is still assigned. > Seems to be an issue for Client Nonperson domain object, as other drop downs > related to Client domain object are working as expected. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-415) Loan product should not allow to be created and should throw proper error when mandatory guarantee is not equal to any one of the guarantee(own or guarantor) or sum of
[ https://issues.apache.org/jira/browse/FINERACT-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-415: -- Labels: Volunteer gsoc p2 (was: Volunteer gsoc2017 p2) > Loan product should not allow to be created and should throw proper error > when mandatory guarantee is not equal to any one of the guarantee(own or > guarantor) or sum of both > > > Key: FINERACT-415 > URL: https://issues.apache.org/jira/browse/FINERACT-415 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > > While creating loan product, Enable 'Place guarantee funds on Hold'. > There you will see three fileds: > a) Mandatory Guarantee > b) Minimum Guarantee from Own Funds > c) Minimum Guarantee from Guarantor funds. > a should be equal to b+c. > If a=b then 'c' can be blank. > If a=c then 'b' can be blank. > If not, the loan product should not allow to be created and should throw > proper error: "Mandatory Guarantee should be equal to sum of own fund and > guarantor fund OR any one of them". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-408) When closing Savings account and Withdraw Balance option is enabled, only cash withdrawal is possible, not able to withdraw to a GL Account by Voucher
[ https://issues.apache.org/jira/browse/FINERACT-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-408: -- Labels: Fineract-CN gsoc p3 (was: fineract-2.0 gsoc p3) > When closing Savings account and Withdraw Balance option is enabled, only > cash withdrawal is possible, not able to withdraw to a GL Account by Voucher > -- > > Key: FINERACT-408 > URL: https://issues.apache.org/jira/browse/FINERACT-408 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Critical > Labels: Fineract-CN, gsoc, p3 > > As a system admin, i should be able to close a savings account and make > Balance withdrawal to a GL Account (Contra Account) and payment type for this > should be restricted to by Voucher only. > If Withdraw Balance is not to a GL Account then Cash Payment Type. > Extend this functionality of Withdraw Balance to Share Accounts too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-322) Rewarding Early Repayment
[ https://issues.apache.org/jira/browse/FINERACT-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791137#comment-16791137 ] Edward Cable commented on FINERACT-322: --- [~vishwasbabu] [~santoshmath] Is this still a valid feature request we want to keep open? If they want interest reduced shouldn't they just use a declining balance interest method and not flat? > Rewarding Early Repayment > - > > Key: FINERACT-322 > URL: https://issues.apache.org/jira/browse/FINERACT-322 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p2 > > Reported by Shepard Chihoro at https://mifosforge.jira.com/browse/MIFOSX-2520 > Original Description: > MIFOSX does not reward customers who make early repayments on a flat interest > calculation method.My normal client contract is has a maximum repayment > period of 6 months and a minimum repayment period of 3 months.On > disbursement,MIFOSX calculates the interest for the entire 6 months and makes > principal and interest for 6 months outstanding.In the event that the > customer repays the full principal in 3 months,the customer`s account remains > with 3 months interest due.I would like to see interest outstanding being > stopped once the principal has been repaid in full. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-407) Ability to Re-open closed Accounts (especially Savings and Share Accounts)
[ https://issues.apache.org/jira/browse/FINERACT-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791154#comment-16791154 ] Edward Cable commented on FINERACT-407: --- [~vishwasbabu] [~santoshmath] Any thoughts on this relative to the dormant account functionality that was previously added? > Ability to Re-open closed Accounts (especially Savings and Share Accounts) > -- > > Key: FINERACT-407 > URL: https://issues.apache.org/jira/browse/FINERACT-407 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Fineract-CN, gsoc, p3 > > When a client has not make transactions for many years for example, the MFI > may not know if the client is alive or dead so the MFI can decide to close > this client's Accounts (Savings and Share Accounts). The balances of this > account can be transferred to a GL Account. > Client - GL Transfer: DR Client Accounts and CR. GL Account e.g Share Transfer > After some time, the client surfaces and would like to make transactions on > his accounts. > As a system admin, i should be able to re-open these closed accounts and be > able to transfer the balances from the contra Account back to client's > Savings Account either automatically or manually through batch/journal > Entries where you DR. GL Accounts affected (where the balances are > transferred) and Credit Clients Savings and Share Accounts with the balances > at closure. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-407) Ability to Re-open closed Accounts (especially Savings and Share Accounts)
[ https://issues.apache.org/jira/browse/FINERACT-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-407: -- Labels: Fineract-CN fineract-2.0 gsoc p3 (was: fineract-2.0 gsoc p3) > Ability to Re-open closed Accounts (especially Savings and Share Accounts) > -- > > Key: FINERACT-407 > URL: https://issues.apache.org/jira/browse/FINERACT-407 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Fineract-CN, fineract-2.0, gsoc, p3 > > When a client has not make transactions for many years for example, the MFI > may not know if the client is alive or dead so the MFI can decide to close > this client's Accounts (Savings and Share Accounts). The balances of this > account can be transferred to a GL Account. > Client - GL Transfer: DR Client Accounts and CR. GL Account e.g Share Transfer > After some time, the client surfaces and would like to make transactions on > his accounts. > As a system admin, i should be able to re-open these closed accounts and be > able to transfer the balances from the contra Account back to client's > Savings Account either automatically or manually through batch/journal > Entries where you DR. GL Accounts affected (where the balances are > transferred) and Credit Clients Savings and Share Accounts with the balances > at closure. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-407) Ability to Re-open closed Accounts (especially Savings and Share Accounts)
[ https://issues.apache.org/jira/browse/FINERACT-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-407: -- Labels: Fineract-CN gsoc p3 (was: Fineract-CN fineract-2.0 gsoc p3) > Ability to Re-open closed Accounts (especially Savings and Share Accounts) > -- > > Key: FINERACT-407 > URL: https://issues.apache.org/jira/browse/FINERACT-407 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Fineract-CN, gsoc, p3 > > When a client has not make transactions for many years for example, the MFI > may not know if the client is alive or dead so the MFI can decide to close > this client's Accounts (Savings and Share Accounts). The balances of this > account can be transferred to a GL Account. > Client - GL Transfer: DR Client Accounts and CR. GL Account e.g Share Transfer > After some time, the client surfaces and would like to make transactions on > his accounts. > As a system admin, i should be able to re-open these closed accounts and be > able to transfer the balances from the contra Account back to client's > Savings Account either automatically or manually through batch/journal > Entries where you DR. GL Accounts affected (where the balances are > transferred) and Credit Clients Savings and Share Accounts with the balances > at closure. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-403) Intergrate a chat system where other system users can chat with the system admin
[ https://issues.apache.org/jira/browse/FINERACT-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791148#comment-16791148 ] Edward Cable commented on FINERACT-403: --- As part of the scope of RocketChat integration for clients - we can also explore integration for staff-facing chat activities as well. > Intergrate a chat system where other system users can chat with the system > admin > > > Key: FINERACT-403 > URL: https://issues.apache.org/jira/browse/FINERACT-403 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Fineract-CN, gsoc, p3 > > As a user at one branch of an MFI which can be in a different country, i > should be able to have an inbuilt chat system with Fineract to interact with > my IT Officer at the head officer to trouble should any problem > As systems users at institutional level (different MFIs have a common chat > room), we should be able to have open chat (group chat) or private chat with > system developers especially one that handles users and have troubleshot > discussion -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-392) Ability to edit a self guararntor
[ https://issues.apache.org/jira/browse/FINERACT-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-392: -- Labels: Volunteer gsoc (was: Volunteer) > Ability to edit a self guararntor > - > > Key: FINERACT-392 > URL: https://issues.apache.org/jira/browse/FINERACT-392 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, gsoc > > Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2814 > Original Description: > When a self guarantor has been created there is a chance for a user to attach > a wrong saving account or to allocate a wrong amount. For now when that > happens you have to delete a guarantor and create again. It will be helpful > if a user can edit details of a self guarantor and be able to change deposit > account and amount. > You can see this by applying new loan then in the profile of the loan > navigate to more -> create guarantor, then create a guarantor (same client) > attach the saving account and allocate the amount and submit. Then navigate > to more -> view guarantor, there you will be able to see the guarantor with > "view" icon, "View transaction", "delete" icon . > It could be better if there was "Edit" icon too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-403) Intergrate a chat system where other system users can chat with the system admin
[ https://issues.apache.org/jira/browse/FINERACT-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-403: -- Labels: Fineract-CN gsoc p3 (was: fineract-2.0 gsoc p3) > Intergrate a chat system where other system users can chat with the system > admin > > > Key: FINERACT-403 > URL: https://issues.apache.org/jira/browse/FINERACT-403 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Fineract-CN, gsoc, p3 > > As a user at one branch of an MFI which can be in a different country, i > should be able to have an inbuilt chat system with Fineract to interact with > my IT Officer at the head officer to trouble should any problem > As systems users at institutional level (different MFIs have a common chat > room), we should be able to have open chat (group chat) or private chat with > system developers especially one that handles users and have troubleshot > discussion -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-314) If Tranche disbursement charge payment mode is Account transfer then after first disbursement the charge collection is improper
[ https://issues.apache.org/jira/browse/FINERACT-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791135#comment-16791135 ] Edward Cable commented on FINERACT-314: --- [~santoshmath] is this still valid issue? > If Tranche disbursement charge payment mode is Account transfer then after > first disbursement the charge collection is improper > --- > > Key: FINERACT-314 > URL: https://issues.apache.org/jira/browse/FINERACT-314 > Project: Apache Fineract > Issue Type: Bug > Components: Charges >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Minor > Labels: gsoc, p2 > Fix For: 1.5.0 > > Attachments: 91.png, 93.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2194 > Original Description: > 1. Create Tranche disbursement charge with Charge Payment Mode as Account > transfer. > 2. Create Tranche loan product with 2 tranches and above created charge > attached > 3. Create Savings product and create a client with active savings product > above created. > 4. For the same above client submit new loan application with the above > savings account and Tranche disbursement charge attached while submitting the > application, tranche attached on 01 August 2015 and amount is 5000, 2nd > tranche on 01 September 2015 and amount is 5000 -> Approve and disburse the > first tranche on 01 August 2015. > > In Summary page displaying as both tranche disbursement charges as due > > In Repayment schedule is displaying properly > > In Transactions page and In Charges page both Tranche disbursement charges > > are displaying as collected. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-391) Fund Management-Delete Enhancement
[ https://issues.apache.org/jira/browse/FINERACT-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-391: -- Labels: Volunteer gsoc p3 (was: gsoc p3) > Fund Management-Delete Enhancement > -- > > Key: FINERACT-391 > URL: https://issues.apache.org/jira/browse/FINERACT-391 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, gsoc, p3 > > Reported by Agness Meena at https://mifosforge.jira.com/browse/MIFOSX-2822 > Go to Admin > Organization > Manage Fund > Once you create a new fund you can only edit it but not deleting it. > Need a Delete button to delete existing fund. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-392) Ability to edit a self guararntor
[ https://issues.apache.org/jira/browse/FINERACT-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-392: -- Fix Version/s: 1.5.0 > Ability to edit a self guararntor > - > > Key: FINERACT-392 > URL: https://issues.apache.org/jira/browse/FINERACT-392 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, gsoc > Fix For: 1.5.0 > > > Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2814 > Original Description: > When a self guarantor has been created there is a chance for a user to attach > a wrong saving account or to allocate a wrong amount. For now when that > happens you have to delete a guarantor and create again. It will be helpful > if a user can edit details of a self guarantor and be able to change deposit > account and amount. > You can see this by applying new loan then in the profile of the loan > navigate to more -> create guarantor, then create a guarantor (same client) > attach the saving account and allocate the amount and submit. Then navigate > to more -> view guarantor, there you will be able to see the guarantor with > "view" icon, "View transaction", "delete" icon . > It could be better if there was "Edit" icon too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-388) Improvement in the characters allowed in the column names of Data tables
[ https://issues.apache.org/jira/browse/FINERACT-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-388: -- Labels: Volunteer gsoc p3 (was: gsoc p3 volunteers) > Improvement in the characters allowed in the column names of Data tables > > > Key: FINERACT-388 > URL: https://issues.apache.org/jira/browse/FINERACT-388 > Project: Apache Fineract > Issue Type: Improvement > Components: Data Tables >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, gsoc, p3 > Attachments: Datatable.png > > > Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2826. > Original Description: > The system when configuring Data tables, in the field of column name it does > not allow some of the characters which it could be better to be allowed. For > instance when you want to call your column "Guarantor's phone number" or "A/C > No" the system through an error because of character ' and / > I would suggest for the system to be able to allow other characters rather > than alpha-numeric only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-277) No option to writeoff Overdraft account in Client savings account page
[ https://issues.apache.org/jira/browse/FINERACT-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791130#comment-16791130 ] Edward Cable commented on FINERACT-277: --- [~santoshmath] Can we please provide more detail around this? > No option to writeoff Overdraft account in Client savings account page > -- > > Key: FINERACT-277 > URL: https://issues.apache.org/jira/browse/FINERACT-277 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p3 > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1363 > Original Description: > Write off option in overdraft account (in savings) is not present. It should > be implemented. > In Saving product creation page for cash based accounting writeoff is > introduced under Expense heading -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-305) Dropdowns are using values directly from API instead of using translation
[ https://issues.apache.org/jira/browse/FINERACT-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-305: -- Labels: Volunteer gsoc p3 (was: gsoc p3) > Dropdowns are using values directly from API instead of using translation > - > > Key: FINERACT-305 > URL: https://issues.apache.org/jira/browse/FINERACT-305 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, gsoc, p3 > > Reported by Chandrika at https://mifosforge.jira.com/browse/MIFOSX-2081 > Original Description: > For example, the below dropdown uses documenttype.name from API (which is by > default in English language).Instead we should use > translate(documenttype.name) so that the values will be in sync with the > respective language selected by user. > ng-options="documenttype.id as documenttype.name for documenttype in > documenttypes" value="documenttype.id" required="required" > class="form-control"> -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-302) Principal Threshold (%) for Last Instalment is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791134#comment-16791134 ] Edward Cable commented on FINERACT-302: --- [~santoshmath] Can you please reply to [~sanyam96]'s comment? > Principal Threshold (%) for Last Instalment is not working as expected > -- > > Key: FINERACT-302 > URL: https://issues.apache.org/jira/browse/FINERACT-302 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, fineract-gci, gsoc, p1 > Fix For: 1.5.0 > > Attachments: Scr-664.png, Screenshot from 2018-12-23 22-13-02.png, > Screenshot from 2018-12-23 22-14-34.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2031 > Original Desription: > 1. Create loan product with out mentioning any thing in the "Principal > Threshold (%) for Last Instalment" - by default it is getting set to zero > Instead it should get set to 50% > 2, Create a client and submit new loan application wit the above mentioned > loan product on 01 Jan 2015 with interest recalculation -> Approve and > disburse on same date. > 3. The last installment is getting collected more amount than EMI. > If the "Principal Threshold (%) for Last Instalment" is set to zero then then > the last installment should never be combined with the previous installment > even if the last installment amount is of a very small value. > But here it is displaying the amount>last installment amount -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-290) Additional collateral options. (pawn shop support)
[ https://issues.apache.org/jira/browse/FINERACT-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791133#comment-16791133 ] Edward Cable commented on FINERACT-290: --- [~avikganguly] Are these incorporated into your collateral module requirements? > Additional collateral options. (pawn shop support) > -- > > Key: FINERACT-290 > URL: https://issues.apache.org/jira/browse/FINERACT-290 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: collateral, gsoc, large, p3 > > Reported by MIFOS@FINA at https://mifosforge.jira.com/browse/MIFOSX-1734 > Original Description: > In order to implement Mifos in Georgia and post-soviet region, we need > additional pawn shop collateral support. For example functionality to bind a > car to a loan, with all the details of the car. Also is we want to bind a > house with a price 100 000$ to a loan, and the loan is only 10 000$, we must > be able to bind the house to another loan ( up to 90 000$ ). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-290) Additional collateral options. (pawn shop support)
[ https://issues.apache.org/jira/browse/FINERACT-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-290: -- Labels: collateral gsoc large p3 (was: gsoc p3) > Additional collateral options. (pawn shop support) > -- > > Key: FINERACT-290 > URL: https://issues.apache.org/jira/browse/FINERACT-290 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: collateral, gsoc, large, p3 > > Reported by MIFOS@FINA at https://mifosforge.jira.com/browse/MIFOSX-1734 > Original Description: > In order to implement Mifos in Georgia and post-soviet region, we need > additional pawn shop collateral support. For example functionality to bind a > car to a loan, with all the details of the car. Also is we want to bind a > house with a price 100 000$ to a loan, and the loan is only 10 000$, we must > be able to bind the house to another loan ( up to 90 000$ ). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-274) Not able to create the same datatable which was rejected by the maker checker before
[ https://issues.apache.org/jira/browse/FINERACT-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-274: -- Labels: Volunteer gci gsoc p2 (was: Volunteer confirm gci gsoc p2) > Not able to create the same datatable which was rejected by the maker checker > before > > > Key: FINERACT-274 > URL: https://issues.apache.org/jira/browse/FINERACT-274 > Project: Apache Fineract > Issue Type: Bug > Components: Data Tables >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, gci, gsoc, p2 > Fix For: 1.4.0 > > Attachments: JIRA-274.JPG > > > Posted by Subramanya at [https://mifosforge.jira.com/browse/MIFOSX-1246] > Original Description: > 1. Click on Admin ->System - enable maker-checker. > 2. Click on Admin ->System - Configure maker-checker tasks -> Select > Configurations ->select check box for create, update and delete data tables. > 3. Click on the Admin -> System -> Manage data tables -> Create data table - > and create data table for client. > 4. The navigated page displays "Waiting For Checker Approval" -> Click on > details -> Click on reject button in "View Checker Inbox" -> click on confirm > in confirmation page. > With the above action in UI the data table will not appear, but in the > database the table is still exist. > > Again try to create datable with the same name as above, which displays > error message as the data table already exists, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-274) Not able to create the same datatable which was rejected by the maker checker before
[ https://issues.apache.org/jira/browse/FINERACT-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791129#comment-16791129 ] Edward Cable commented on FINERACT-274: --- [~jonathanzhang53] Are you still looking to complete this task? > Not able to create the same datatable which was rejected by the maker checker > before > > > Key: FINERACT-274 > URL: https://issues.apache.org/jira/browse/FINERACT-274 > Project: Apache Fineract > Issue Type: Bug > Components: Data Tables >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, confirm, gci, gsoc, p2 > Fix For: 1.4.0 > > Attachments: JIRA-274.JPG > > > Posted by Subramanya at [https://mifosforge.jira.com/browse/MIFOSX-1246] > Original Description: > 1. Click on Admin ->System - enable maker-checker. > 2. Click on Admin ->System - Configure maker-checker tasks -> Select > Configurations ->select check box for create, update and delete data tables. > 3. Click on the Admin -> System -> Manage data tables -> Create data table - > and create data table for client. > 4. The navigated page displays "Waiting For Checker Approval" -> Click on > details -> Click on reject button in "View Checker Inbox" -> click on confirm > in confirmation page. > With the above action in UI the data table will not appear, but in the > database the table is still exist. > > Again try to create datable with the same name as above, which displays > error message as the data table already exists, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-269) Add Info Base on Clients Account - Loans, Shares, Fixed Deposit, Loans and Recuring Deposit Account
[ https://issues.apache.org/jira/browse/FINERACT-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791128#comment-16791128 ] Edward Cable commented on FINERACT-269: --- [~santoshmath] Is there a corresponding issue on the community app side for this? > Add Info Base on Clients Account - Loans, Shares, Fixed Deposit, Loans and > Recuring Deposit Account > --- > > Key: FINERACT-269 > URL: https://issues.apache.org/jira/browse/FINERACT-269 > Project: Apache Fineract > Issue Type: Improvement > Components: Client >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Fineract-CN, gsoc, p2 > Attachments: Infobase.pdf > > > Infobase > This allows you to add free-form descriptions or notes to certain accounts. > These notes can be unlimited in size and can be used to provide all kind of > additional information about any account or its owner. > Later then whenever this account will be accessed this information will be > displayed on the screen as in following example. > See attachment for visual explanation > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-269) Add Info Base on Clients Account - Loans, Shares, Fixed Deposit, Loans and Recuring Deposit Account
[ https://issues.apache.org/jira/browse/FINERACT-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-269: -- Labels: Fineract-CN gsoc p2 (was: gsoc p2) > Add Info Base on Clients Account - Loans, Shares, Fixed Deposit, Loans and > Recuring Deposit Account > --- > > Key: FINERACT-269 > URL: https://issues.apache.org/jira/browse/FINERACT-269 > Project: Apache Fineract > Issue Type: Improvement > Components: Client >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Fineract-CN, gsoc, p2 > Attachments: Infobase.pdf > > > Infobase > This allows you to add free-form descriptions or notes to certain accounts. > These notes can be unlimited in size and can be used to provide all kind of > additional information about any account or its owner. > Later then whenever this account will be accessed this information will be > displayed on the screen as in following example. > See attachment for visual explanation > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-242) Transaction history doesn't show occured transactions inside the "View standing instructions" for a client account
[ https://issues.apache.org/jira/browse/FINERACT-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-242: -- Labels: Volunteer gsoc p3 (was: Volunteer p3) > Transaction history doesn't show occured transactions inside the "View > standing instructions" for a client account > -- > > Key: FINERACT-242 > URL: https://issues.apache.org/jira/browse/FINERACT-242 > Project: Apache Fineract > Issue Type: Bug > Components: Client, Savings > Environment: Amazon AMI - Mifos X Release Version: 16.09.01.RELEASE >Reporter: Auguste Niragira >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, gsoc, p3 > > I noticed that when you go to > Client account > More > View standing instructions > Select standing > instruction from list > View transaction history > There are no transactions listed, although I know for a fact the automated > transactions were successful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-242) Transaction history doesn't show occured transactions inside the "View standing instructions" for a client account
[ https://issues.apache.org/jira/browse/FINERACT-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791113#comment-16791113 ] Edward Cable commented on FINERACT-242: --- [~santoshmath] Can you please reproduce this and confirm it exists? > Transaction history doesn't show occured transactions inside the "View > standing instructions" for a client account > -- > > Key: FINERACT-242 > URL: https://issues.apache.org/jira/browse/FINERACT-242 > Project: Apache Fineract > Issue Type: Bug > Components: Client, Savings > Environment: Amazon AMI - Mifos X Release Version: 16.09.01.RELEASE >Reporter: Auguste Niragira >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, gsoc, p3 > > I noticed that when you go to > Client account > More > View standing instructions > Select standing > instruction from list > View transaction history > There are no transactions listed, although I know for a fact the automated > transactions were successful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-263) "Add Notes" for Centers permission is missing
[
https://issues.apache.org/jira/browse/FINERACT-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791121#comment-16791121
]
Edward Cable commented on FINERACT-263:
---
[~santoshmath] Can you verify that this issue still exists?
> "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: Volunteer, fineract-gci, gsoc, p2
>
> 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
(v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel=16791119#comment-16791119 ] Edward Cable commented on FINERACT-259: --- [~santoshmath]Can you reproduce and verify this issue still exists? > 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 >Priority: Major > Labels: Volunteer, confirm, p3 > 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 (v7.6.3#76005)
[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:
--
Labels: Volunteer fineract-gci gsoc p2 (was: Volunteer fineract-gci p2)
> "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: Volunteer, fineract-gci, gsoc, p2
>
> 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
(v7.6.3#76005)
[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: -- Labels: Fineract-CN gsoc large p3 (was: gsoc p3) > 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 >Priority: Major > Labels: Fineract-CN, gsoc, large, p3 > > 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 (v7.6.3#76005)
[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: -- Labels: Fineract-CN gsoc large p2 volunteers (was: gsoc p2 volunteers) > 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 >Priority: Major > Labels: Fineract-CN, gsoc, large, p2, volunteers > > 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 (v7.6.3#76005)
[jira] [Updated] (FINERACT-254) Password Email Notice
[ https://issues.apache.org/jira/browse/FINERACT-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-254: -- Fix Version/s: 1.5.0 > Password Email Notice > - > > Key: FINERACT-254 > URL: https://issues.apache.org/jira/browse/FINERACT-254 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > Fix For: 1.5.0 > > > While requesting documentation be written to describe how an organization can > customize the outgoing message to the user that provides their password, it > was discovered that this is hard coded. > https://mifosforge.jira.com/browse/MXD-107 > The expected result is that an organization can enter their own subject line, > and edit the message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-232) Ability to Post General Ledger Entries Directly to Customer Account
[ https://issues.apache.org/jira/browse/FINERACT-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-232: -- Labels: Fineract-CN gsoc large p3 (was: gsoc large p3) > Ability to Post General Ledger Entries Directly to Customer Account > --- > > Key: FINERACT-232 > URL: https://issues.apache.org/jira/browse/FINERACT-232 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Fineract-CN, gsoc, large, p3 > Attachments: Complete New UI Mock up for Journal Entry Screen.png, > Enhancements for Journal Entry.pdf > > > https://mifosforge.jira.com/browse/MIFOSX-2182 > From MIFOS X: As an accountant, i would like to be able to make a transfer > from a client's account (Savings Account or Loan Account) to a GL Account and > also be able to make transfer from a GL Account (e.g Cash at Hand) to > Client's Account (e.g Savings Account or Loan Account) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-250) Place Guarantor Funds On Hold
[ https://issues.apache.org/jira/browse/FINERACT-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791117#comment-16791117 ] Edward Cable commented on FINERACT-250: --- [~santoshmath] how much of this has yet to be implemented? Should this ticket still be open? > Place Guarantor Funds On Hold > - > > Key: FINERACT-250 > URL: https://issues.apache.org/jira/browse/FINERACT-250 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p3 > > Functional Spec: > https://cwiki.apache.org/confluence/display/FINERACT/Blocking+Funds+in+Guarantor+Account -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-248) SMS Campaign- Two or more than two SMS campaigns can accept same name.
[ https://issues.apache.org/jira/browse/FINERACT-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-248: -- Fix Version/s: 1.5.0 > SMS Campaign- Two or more than two SMS campaigns can accept same name. > --- > > Key: FINERACT-248 > URL: https://issues.apache.org/jira/browse/FINERACT-248 > Project: Apache Fineract > Issue Type: Bug > Components: Organization > Environment: Creating SMS campaign >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, gsoc, p2 > Fix For: 1.5.0 > > > When we create new SMS campaign and if we give same name of existing SMS > campaign, it accepts the name. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-250) Place Guarantor Funds On Hold
[ https://issues.apache.org/jira/browse/FINERACT-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-250: -- Summary: Place Guarantor Funds On Hold (was: Plance Guarantor Funds On Hold) > Place Guarantor Funds On Hold > - > > Key: FINERACT-250 > URL: https://issues.apache.org/jira/browse/FINERACT-250 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p3 > > Functional Spec: > https://cwiki.apache.org/confluence/display/FINERACT/Blocking+Funds+in+Guarantor+Account -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-248) SMS Campaign- Two or more than two SMS campaigns can accept same name.
[ https://issues.apache.org/jira/browse/FINERACT-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-248: -- Labels: Volunteer gsoc p2 (was: Volunteer p2) > SMS Campaign- Two or more than two SMS campaigns can accept same name. > --- > > Key: FINERACT-248 > URL: https://issues.apache.org/jira/browse/FINERACT-248 > Project: Apache Fineract > Issue Type: Bug > Components: Organization > Environment: Creating SMS campaign >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, gsoc, p2 > > When we create new SMS campaign and if we give same name of existing SMS > campaign, it accepts the name. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-244) New Repayment Schedule Not Populating
[ https://issues.apache.org/jira/browse/FINERACT-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-244: -- Fix Version/s: 1.5.0 > New Repayment Schedule Not Populating > - > > Key: FINERACT-244 > URL: https://issues.apache.org/jira/browse/FINERACT-244 > Project: Apache Fineract > Issue Type: Bug >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p3 > Fix For: 1.5.0 > > > Mifos - View Loan Account - More Drop Down - Reschedule > After complete Reschedule Loan Screen - Press Submit > View Loan reschedule request - then select View new Repayment Schedule > New Repayment Schedule Screen does not populate any information for > verification prior to accepting the change. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
