[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 ] Ed Cable updated FINERACT-26: - Fix Version/s: 3.0.0 (was: 1.9.0) > 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 >Affects Versions: 1.8.0 >Reporter: Dayna Harp >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p1 > Fix For: 3.0.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 (v8.20.10#820010)
[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 ] Ed Cable updated FINERACT-26: - Labels: 2019-mifos-gsoc Volunteer gsoc p1 (was: 2019-mifos-gsoc 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 >Affects Versions: 1.8.0 >Reporter: Dayna Harp >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p1 > Fix For: 1.9.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 (v8.20.10#820010)
[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 ] Ed Cable updated FINERACT-176: -- Labels: 2019-mifos-gsoc Beginner Volunteer gsoc p3 (was: 2019-mifos-gsoc 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 > Components: Teller Module >Affects Versions: 1.8.0 >Reporter: subramanyasn >Priority: Major > Labels: 2019-mifos-gsoc, Beginner, Volunteer, gsoc, p3 > Fix For: 1.9.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 (v8.20.10#820010)
[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 ] Ed Cable updated FINERACT-176: -- Component/s: Teller Module > 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 > Components: Teller Module >Affects Versions: 1.8.0 >Reporter: subramanyasn >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p3 > Fix For: 1.9.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 (v8.20.10#820010)
[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 ] Ed Cable updated FINERACT-176: -- Fix Version/s: 3.0.0 (was: 1.9.0) > 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 > Components: Teller Module >Affects Versions: 1.8.0 >Reporter: subramanyasn >Priority: Major > Labels: 2019-mifos-gsoc, Beginner, Volunteer, gsoc, p3 > Fix For: 3.0.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 (v8.20.10#820010)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17761885#comment-17761885 ] Ed Cable commented on FINERACT-225: --- [~bgowda] we should see if this is still reproducible. > 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 >Affects Versions: 1.8.0 >Reporter: subramanyasn >Priority: Minor > Labels: 2019-mifos-gsoc, GCI-2019, Triage, Volunteer, gsoc, p2 > Fix For: 3.0.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 (v8.20.10#820010)
[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 ] Ed Cable updated FINERACT-225: -- Labels: 2019-mifos-gsoc GCI-2019 Triage Volunteer gsoc p2 (was: 2019-mifos-gsoc GCI-2019 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 >Affects Versions: 1.8.0 >Reporter: subramanyasn >Priority: Minor > Labels: 2019-mifos-gsoc, GCI-2019, Triage, Volunteer, gsoc, p2 > Fix For: 1.9.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 (v8.20.10#820010)
[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 ] Ed Cable updated FINERACT-225: -- Fix Version/s: 3.0.0 (was: 1.9.0) > 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 >Affects Versions: 1.8.0 >Reporter: subramanyasn >Priority: Minor > Labels: 2019-mifos-gsoc, GCI-2019, Triage, Volunteer, gsoc, p2 > Fix For: 3.0.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 (v8.20.10#820010)
[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 ] Ed Cable updated FINERACT-231: -- Labels: 2019-mifos-gsoc Triage Volunteer gsoc p2 (was: 2019-mifos-gsoc 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 >Affects Versions: 1.8.0 >Reporter: subramanyasn >Priority: Minor > Labels: 2019-mifos-gsoc, Triage, Volunteer, gsoc, p2 > Fix For: 1.9.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 (v8.20.10#820010)
[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 ] Ed Cable updated FINERACT-231: -- Fix Version/s: 3.0.0 (was: 1.9.0) > 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 >Affects Versions: 1.8.0 >Reporter: subramanyasn >Priority: Minor > Labels: 2019-mifos-gsoc, Triage, Volunteer, gsoc, p2 > Fix For: 3.0.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 (v8.20.10#820010)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17761883#comment-17761883 ] Ed Cable commented on FINERACT-231: --- [~bgowda] Do we know if this issue is still reproducible? > 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 >Affects Versions: 1.8.0 >Reporter: subramanyasn >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p2 > Fix For: 1.9.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 (v8.20.10#820010)
[jira] [Updated] (FINERACT-254) Add the Ability to Customize the Password Email Notice
[ https://issues.apache.org/jira/browse/FINERACT-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ed Cable updated FINERACT-254: -- Fix Version/s: 3.0.0 (was: 1.9.0) > Add the Ability to Customize the Password Email Notice > -- > > Key: FINERACT-254 > URL: https://issues.apache.org/jira/browse/FINERACT-254 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.8.0 >Reporter: Dayna Harp >Priority: Major > Labels: Volunteer, gsoc, p2 > Fix For: 3.0.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 (v8.20.10#820010)
[jira] [Updated] (FINERACT-248) Two or more SMS Campaigns should not have the same Name.
[ https://issues.apache.org/jira/browse/FINERACT-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ed Cable updated FINERACT-248: -- Fix Version/s: 3.0.0 (was: 1.9.0) > Two or more SMS Campaigns should not have the same Name. > - > > Key: FINERACT-248 > URL: https://issues.apache.org/jira/browse/FINERACT-248 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Affects Versions: 1.8.0 > Environment: Creating SMS campaign >Reporter: Santosh Math >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, beginner, gsoc, p2, technical > Fix For: 3.0.0 > > > When we create new SMS campaign and if we give same name of existing SMS > campaign, it accepts the name. SMS Campaigns should not accept the same name. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-13) Multi-tranche Loan repayment on 2nd tranche incorrect
[ https://issues.apache.org/jira/browse/FINERACT-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ed Cable updated FINERACT-13: - Fix Version/s: 3.0.0 (was: 1.9.0) > Multi-tranche Loan repayment on 2nd tranche incorrect > - > > Key: FINERACT-13 > URL: https://issues.apache.org/jira/browse/FINERACT-13 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.8.0 >Reporter: Dayna Harp >Priority: Major > Labels: Volunteer, gsoc, p1, triage > Fix For: 3.0.0 > > Original Estimate: 10h > Remaining Estimate: 10h > > https://mifosforge.jira.com/browse/MIFOSX-2398 - See for attachments > 1. Create a loan product with following data sets, > Principal:10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max) > Repay Every: 1 Months > Nominal Interest Rate:1 ( Min: , Max) Per month > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Repayment StrategyPenalties, Fees, Interest, Principal order > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Recalculate Interest Yes > Advance payments adjustment type Reduce number of installments > Pre-closure interest calculation rule Calculate till pre closure date > Interest recalculation compounding on None > Frequency for recalculate Outstanding Principal Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01-Sep-15 > Enable Multiple DisbursalsTRUE > Maximum Tranche count 2 > Maximum allowed outstanding balance 1 > 2. Create specified due date charge 1% of amount and attache to the above > loan product, > 3. Submit new loan application for a client on 01 September 2015 with first > tranche of 5000 on same date and second tranche on 01 November 2015 and > amount 5000. Add specified due date charge date as 15 September 2015. > 4. Make repayment on 01 October 2015 in which charge applied on 15 September > 2015 got collected and amount as 50 (1% of disbursed amount). > 5. Disburse 2nd tranche as 5000 on 01 November 2015. > > In the repayment schedule 50 is displaying as balance in 01 October 2015 > > repayment. > > Application Should not allowed to modify or apply charge for the repayment > > which is already paid -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-13) Multi-tranche Loan repayment on 2nd tranche incorrect
[ https://issues.apache.org/jira/browse/FINERACT-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ed Cable updated FINERACT-13: - Labels: Volunteer gsoc p1 triage (was: Volunteer gsoc p1) > Multi-tranche Loan repayment on 2nd tranche incorrect > - > > Key: FINERACT-13 > URL: https://issues.apache.org/jira/browse/FINERACT-13 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.8.0 >Reporter: Dayna Harp >Priority: Major > Labels: Volunteer, gsoc, p1, triage > Fix For: 1.9.0 > > Original Estimate: 10h > Remaining Estimate: 10h > > https://mifosforge.jira.com/browse/MIFOSX-2398 - See for attachments > 1. Create a loan product with following data sets, > Principal:10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max) > Repay Every: 1 Months > Nominal Interest Rate:1 ( Min: , Max) Per month > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Repayment StrategyPenalties, Fees, Interest, Principal order > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Recalculate Interest Yes > Advance payments adjustment type Reduce number of installments > Pre-closure interest calculation rule Calculate till pre closure date > Interest recalculation compounding on None > Frequency for recalculate Outstanding Principal Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01-Sep-15 > Enable Multiple DisbursalsTRUE > Maximum Tranche count 2 > Maximum allowed outstanding balance 1 > 2. Create specified due date charge 1% of amount and attache to the above > loan product, > 3. Submit new loan application for a client on 01 September 2015 with first > tranche of 5000 on same date and second tranche on 01 November 2015 and > amount 5000. Add specified due date charge date as 15 September 2015. > 4. Make repayment on 01 October 2015 in which charge applied on 15 September > 2015 got collected and amount as 50 (1% of disbursed amount). > 5. Disburse 2nd tranche as 5000 on 01 November 2015. > > In the repayment schedule 50 is displaying as balance in 01 October 2015 > > repayment. > > Application Should not allowed to modify or apply charge for the repayment > > which is already paid -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-12) For Overdue/Due Fee/Int,Principal strategy with variable installment, late repayment is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ed Cable updated FINERACT-12: - Fix Version/s: 3.0.0 (was: 1.9.0) > For Overdue/Due Fee/Int,Principal strategy with variable installment, late > repayment is not working as expected > --- > > Key: FINERACT-12 > URL: https://issues.apache.org/jira/browse/FINERACT-12 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.8.0 >Reporter: Dayna Harp >Priority: Major > Labels: Volunteer, cleanup22, gci, gsoc, p1, triage > Fix For: 3.0.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2401 > 1. Create loan product with following datasets, > Terms > Terms vary based on loan cycle : false > Principal: 10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max) > Repay Every: 1 Months > Nominal Interest Rate: 1 ( Min: , Max) Per month > Minimum days between disbursal and first repayment date > Settings > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Arrears Tolerance > Repayment Strategy Overdue/Due Fee/Int,Principal > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Allow fixing of the installment amount No > Variable Installments (Min:0 , Max:365) > Interest Recalculation > Recalculate Interest Yes > Advance payments adjustment type Reduce number of installments > Pre-closure interest calculation rule Calculate till pre closure date > Interest recalculation compounding on None > Frequency for recalculate Outstanding Principal Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01 October 2015 > Is Arrears recognization based on original schedule No > 2. Create a client and submit new loan application on 01 October 2015. > 3. Click on More -> Edit repayment schedule in which delete repayment for 01 > November 2015 and click on validate and submit button. > 4. Approve and disburse loan on 01 October 2015. > 5. Make repayment on 15 December 2015. > > In Overdue/Due Fee/Int,Principal repayment strategy one entry on 15 > > December 2015 should get created, which is not getting getting created. > > Interest should get calculated upto 14 December 2015. (Disbursement date 01 > > October 2015 and first repayment is doing on 15 December 2015). > Attachments: https://mifosforge.jira.com/browse/MIFOSX-2401 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-12) For Overdue/Due Fee/Int,Principal strategy with variable installment, late repayment is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ed Cable updated FINERACT-12: - Labels: Volunteer cleanup22 gci gsoc p1 triage (was: Volunteer cleanup22 gci gsoc p1) > For Overdue/Due Fee/Int,Principal strategy with variable installment, late > repayment is not working as expected > --- > > Key: FINERACT-12 > URL: https://issues.apache.org/jira/browse/FINERACT-12 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.8.0 >Reporter: Dayna Harp >Priority: Major > Labels: Volunteer, cleanup22, gci, gsoc, p1, triage > Fix For: 1.9.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2401 > 1. Create loan product with following datasets, > Terms > Terms vary based on loan cycle : false > Principal: 10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max) > Repay Every: 1 Months > Nominal Interest Rate: 1 ( Min: , Max) Per month > Minimum days between disbursal and first repayment date > Settings > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Arrears Tolerance > Repayment Strategy Overdue/Due Fee/Int,Principal > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Allow fixing of the installment amount No > Variable Installments (Min:0 , Max:365) > Interest Recalculation > Recalculate Interest Yes > Advance payments adjustment type Reduce number of installments > Pre-closure interest calculation rule Calculate till pre closure date > Interest recalculation compounding on None > Frequency for recalculate Outstanding Principal Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01 October 2015 > Is Arrears recognization based on original schedule No > 2. Create a client and submit new loan application on 01 October 2015. > 3. Click on More -> Edit repayment schedule in which delete repayment for 01 > November 2015 and click on validate and submit button. > 4. Approve and disburse loan on 01 October 2015. > 5. Make repayment on 15 December 2015. > > In Overdue/Due Fee/Int,Principal repayment strategy one entry on 15 > > December 2015 should get created, which is not getting getting created. > > Interest should get calculated upto 14 December 2015. (Disbursement date 01 > > October 2015 and first repayment is doing on 15 December 2015). > Attachments: https://mifosforge.jira.com/browse/MIFOSX-2401 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-12) For Overdue/Due Fee/Int,Principal strategy with variable installment, late repayment is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761882#comment-17761882 ] Ed Cable commented on FINERACT-12: -- [~bgowda] Do we know if this issue is still valid? > For Overdue/Due Fee/Int,Principal strategy with variable installment, late > repayment is not working as expected > --- > > Key: FINERACT-12 > URL: https://issues.apache.org/jira/browse/FINERACT-12 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.8.0 >Reporter: Dayna Harp >Priority: Major > Labels: Volunteer, cleanup22, gci, gsoc, p1 > Fix For: 1.9.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2401 > 1. Create loan product with following datasets, > Terms > Terms vary based on loan cycle : false > Principal: 10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max) > Repay Every: 1 Months > Nominal Interest Rate: 1 ( Min: , Max) Per month > Minimum days between disbursal and first repayment date > Settings > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Arrears Tolerance > Repayment Strategy Overdue/Due Fee/Int,Principal > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Allow fixing of the installment amount No > Variable Installments (Min:0 , Max:365) > Interest Recalculation > Recalculate Interest Yes > Advance payments adjustment type Reduce number of installments > Pre-closure interest calculation rule Calculate till pre closure date > Interest recalculation compounding on None > Frequency for recalculate Outstanding Principal Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01 October 2015 > Is Arrears recognization based on original schedule No > 2. Create a client and submit new loan application on 01 October 2015. > 3. Click on More -> Edit repayment schedule in which delete repayment for 01 > November 2015 and click on validate and submit button. > 4. Approve and disburse loan on 01 October 2015. > 5. Make repayment on 15 December 2015. > > In Overdue/Due Fee/Int,Principal repayment strategy one entry on 15 > > December 2015 should get created, which is not getting getting created. > > Interest should get calculated upto 14 December 2015. (Disbursement date 01 > > October 2015 and first repayment is doing on 15 December 2015). > Attachments: https://mifosforge.jira.com/browse/MIFOSX-2401 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1424) Make collateral feature optional for multi disbursement
[ https://issues.apache.org/jira/browse/FINERACT-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761743#comment-17761743 ] Benura Lasan commented on FINERACT-1424: Hi Aleks, The issue "Making collateral feature optional" is already done AFAIR. I think we can clarify this with Avik and Manoj. I remember someone worked on this. Thanks, Benura On Mon, 4 Sep 2023, 12:50 Aleksandar Vidakovic (Jira), > Make collateral feature optional for multi disbursement > --- > > Key: FINERACT-1424 > URL: https://issues.apache.org/jira/browse/FINERACT-1424 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.6.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Major > Fix For: 3.0.0 > > > Loan collateral should be optional when creating a loan. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1201) Remove copy/paste between FileSystemContentRepository and S3ContentRepository
[
https://issues.apache.org/jira/browse/FINERACT-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-1201:
---
Fix Version/s: 3.0.0
> Remove copy/paste between FileSystemContentRepository and S3ContentRepository
> -
>
> Key: FINERACT-1201
> URL: https://issues.apache.org/jira/browse/FINERACT-1201
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Michael Vorburger
>Assignee: Michael Vorburger
>Priority: Major
> Fix For: 3.0.0
>
>
> While looking into FINERACT-955, I have found that a lot of the code between
> the {{FileSystemContentRepository}} and the {{S3ContentRepository}} appear to
> very similar.. historically most likely copy/pasted from one to the other.
> There are also some subtle differences e.g. {{FileSystemContentRepository}}
> does not seem to invoke
> {{ContentRepositoryUtils.validateFileSizeWithinPermissibleRange(documentCommand.getSize(),
> fileName);}} like {{S3ContentRepository}}. I suspect that probably was not
> intentional?
> Before implementing FINERACT-955, I'll attempt to remove this copy/paste and
> unify those two implementations of {{ContentRepository}}.
> I'll do this in 2 steps: 1. just move some lines, and add some missig lines,
> to make them "look" more similar; 2. actually merge their code by refactoring
> into a common abstract super classes or utilities for composition.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-786) Fineract on Google Cloud ("managed", with Cloud SQL)
[
https://issues.apache.org/jira/browse/FINERACT-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-786:
--
Fix Version/s: 3.0.0
> Fineract on Google Cloud ("managed", with Cloud SQL)
>
>
> Key: FINERACT-786
> URL: https://issues.apache.org/jira/browse/FINERACT-786
> Project: Apache Fineract
> Issue Type: New Feature
>Reporter: Michael Vorburger
>Assignee: Michael Vorburger
>Priority: Major
> Fix For: 3.0.0
>
>
> The goal of this issue to run an instance of Fineract (non-CN) on Google
> Cloud.
> The idea would be to go "managed", with Cloud Run and Cloud SQL; not using
> GKE, if possible.
> The outcome of this task should be an actually running demo instance, and
> (ideally) documentation.
> This, of course, requires Google Cloud credits.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-932) Parent Issue for Error Logs seeing during "normal" usage (e.g. on fineract.dev)
[ https://issues.apache.org/jira/browse/FINERACT-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-932: -- Fix Version/s: 3.0.0 > Parent Issue for Error Logs seeing during "normal" usage (e.g. on > fineract.dev) > --- > > Key: FINERACT-932 > URL: https://issues.apache.org/jira/browse/FINERACT-932 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Michael Vorburger >Assignee: Michael Vorburger >Priority: Blocker > Fix For: 3.0.0 > > > I'm seeing a number of exceptions in the logs of > [https://www.fineract.dev|https://www.fineract.dev/], and at least some if > not most of them, to me, seem like things that probably should not be logged > as errors. > IMHO, a log.error() should only be used to indicate something "broken" (e.g. > can't connect to a database), but not, typically, for something like a > missing field problem in an incoming JSON? That's "normal", and already > signaled to th e client through an expected response. An "operator" can't > typically "do something" about those kinds of errors. > We can also think of some special cases, e.g. the log.error we currently for > FINERACT-726, which may be useful to help people more easily see that > widespread problem, during transitioning. But perhaps log warn or even info > instead of error would be more appropriate than error for such things? > Perhaps what I'm outlining here should be documented on the README in a > (succinct) "Log Policy" kind of section? > I'll create dedicated linked issues for each such exception I'm seeing, for > analysis by others interested. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-955) ContentRepository for Google Cloud Storage
[
https://issues.apache.org/jira/browse/FINERACT-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-955:
--
Fix Version/s: 3.0.0
> ContentRepository for Google Cloud Storage
> --
>
> Key: FINERACT-955
> URL: https://issues.apache.org/jira/browse/FINERACT-955
> Project: Apache Fineract
> Issue Type: New Feature
>Reporter: Michael Vorburger
>Assignee: Michael Vorburger
>Priority: Major
> Labels: beginner
> Fix For: 3.0.0
>
>
> Similarly to S3ContentRepository, a {{ContentRepository}} for Google Cloud
> Storage (GCS) could be useful, for FINERACT-786, and I would use it on
> https://www.fineract.dev.
> It may actually even be possible to use the S3 API, but a GCS native
> implementation is probably smoother and easier to use. One thing in
> particular I'm hoping for is that it could pick up the required
> authentication when running on GCloud automatically from some service account
> environment variables which as far as I know are present there; it would be
> nice, if possible, if there was no need, or as little as possible, need for
> additional configuration parameters.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1376) Invalid field name in various class of objects defined in GetSavingsProductsTemplateResponse
[ https://issues.apache.org/jira/browse/FINERACT-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1376: --- Fix Version/s: 3.0.0 (was: 1.5.0) > Invalid field name in various class of objects defined in > GetSavingsProductsTemplateResponse > > > Key: FINERACT-1376 > URL: https://issues.apache.org/jira/browse/FINERACT-1376 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.5.0 >Reporter: Danish Jamal >Assignee: Danish Jamal >Priority: Major > Labels: gsoc2021, savings, swagger > Fix For: 3.0.0 > > > In all the below classes the "description" must be "value". > # GetSavingsProductsInterestCompoundingPeriodType > # GetSavingsProductsInterestPostingPeriodType > # GetSavingsProductsInterestCalculationType > # GetSavingsProductsInterestCalculationDaysInYearType > # GetSavingsProductsTemplateAccountingRule > # GetSavingsProductsLockinPeriodFrequencyTypeOptions > # GetSavingsProductsWithdrawalFeeTypeOptions > # GetSavingsProductsTemplateAccountingRule -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1377) multiple field missing in GetSavingsProductsPaymentTypeOptions
[
https://issues.apache.org/jira/browse/FINERACT-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-1377:
---
Fix Version/s: 3.0.0
(was: 1.5.0)
> multiple field missing in GetSavingsProductsPaymentTypeOptions
> --
>
> Key: FINERACT-1377
> URL: https://issues.apache.org/jira/browse/FINERACT-1377
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.5.0
>Reporter: Danish Jamal
>Assignee: Danish Jamal
>Priority: Major
> Labels: gsoc2021, savings, swagger
> Fix For: 3.0.0
>
>
> Fields "description" and "isCashPayment" missing in the
> GetSavingsProductsPaymentTypeOptions generated class. Refer below two code
> snippets attached for the difference.
> {code:java}
> // fields defined in GetSavingsProductsPaymentTypeOptions
> public static final String SERIALIZED_NAME_ID = "id";
> @SerializedName("id")
> private Integer id;
> public static final String SERIALIZED_NAME_NAME = "name";
> @SerializedName("name")
> private String name;
> public static final String SERIALIZED_NAME_POSITION = "position";
> @SerializedName("position")
> private Integer position;
> {code}
> {code:java}
> // api response
> {
> "id": 1,
> "name": "Money Transfer",
> "description": "Money Transfer",
> "isCashPayment": false,
> "position": 1
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1373) invalid response while getting datatable info in GetDataTablesAppTableIdResponse
[
https://issues.apache.org/jira/browse/FINERACT-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-1373:
---
Fix Version/s: 3.0.0
(was: 1.5.0)
> invalid response while getting datatable info in
> GetDataTablesAppTableIdResponse
>
>
> Key: FINERACT-1373
> URL: https://issues.apache.org/jira/browse/FINERACT-1373
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Danish Jamal
>Assignee: Danish Jamal
>Priority: Major
> Labels: datatable, gsoc2021, swagger
> Fix For: 3.0.0
>
>
> The generated class "GetDataTablesAppTableIdResponse" is invalid since the
> backend response is not same as the generated class for the endpoint
> "datatables/\{dataTableName}/\{entityId}/". See example below
> {code:java}
> // fields defined in GetDataTablesAppTableIdResponse class
> public static final String SERIALIZED_NAME_COLUMN_HEADERS = "columnHeaders";
> @SerializedName("columnHeaders")
> private List columnHeaders = null;
> public static final String SERIALIZED_NAME_DATA = "data";
> @SerializedName("data")
> private List data = null;{code}
>
> {code:java}
> // actual json response
> {
> "id": 2,
> "client_id": 1,
> "FirstName": "First name",
> "LastName": "Last name",
> "Mobile Number": null
> }{code}
>
> Also note that the actual JSON response is contextual, which contains
> key-value pair and key will be different based on the specific table. Hence
> the generic response class should be used.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1372) invalid fields in GetDataTablesResponse when getting datatables
[
https://issues.apache.org/jira/browse/FINERACT-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-1372:
---
Fix Version/s: 3.0.0
(was: 1.5.0)
> invalid fields in GetDataTablesResponse when getting datatables
> ---
>
> Key: FINERACT-1372
> URL: https://issues.apache.org/jira/browse/FINERACT-1372
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Danish Jamal
>Assignee: Danish Jamal
>Priority: Major
> Labels: datatable, gsoc2021, swagger
> Fix For: 3.0.0
>
>
> Currently the "GetDataTablesResponse" class has fields named "appTableName",
> "datatableName" and "column", but below data is returned from backend. This
> can be cross check from older(html) doc of the api.
> [localhost|https://localhost:8443/fineract-provider/api-docs/apiLive.htm#datatables_list]
> or
> [demo.fineract.dev|https://demo.fineract.dev/fineract-provider/api-docs/apiLive.htm#datatables_list]
> {code:java}
> {
> "applicationTableName": "m_client",
> "registeredTableName": "Client Beneficiary information",
> "columnHeaderData": []
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1378) invalid data type of a field accountingMappingOptions in GetSavingsProductsTemplateResponse
[ https://issues.apache.org/jira/browse/FINERACT-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1378: --- Fix Version/s: 3.0.0 (was: 1.5.0) > invalid data type of a field accountingMappingOptions in > GetSavingsProductsTemplateResponse > --- > > Key: FINERACT-1378 > URL: https://issues.apache.org/jira/browse/FINERACT-1378 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.5.0 >Reporter: Danish Jamal >Assignee: Danish Jamal >Priority: Major > Labels: gsoc2021, savings, swagger > Fix For: 3.0.0 > > Attachments: Screenshot 2021-08-12 at 8.17.06 PM.png > > > The "accountingMappingOptions" in "GetSavingsProductsTemplateResponse" is > expected to be List of object in the generated class but actual response is > returned as object. Take a look in below SS for actual response. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1424) Make collateral feature optional for multi disbursement
[ https://issues.apache.org/jira/browse/FINERACT-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1424: --- Fix Version/s: 3.0.0 (was: 1.5.0) > Make collateral feature optional for multi disbursement > --- > > Key: FINERACT-1424 > URL: https://issues.apache.org/jira/browse/FINERACT-1424 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.6.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Major > Fix For: 3.0.0 > > > Loan collateral should be optional when creating a loan. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1521) DefaultSqlScriptExecutor DB: Unknown table 'fineract_default.
[
https://issues.apache.org/jira/browse/FINERACT-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-1521:
---
Fix Version/s: 3.0.0
(was: 1.5.0)
> DefaultSqlScriptExecutor DB: Unknown table 'fineract_default.
> --
>
> Key: FINERACT-1521
> URL: https://issues.apache.org/jira/browse/FINERACT-1521
> Project: Apache Fineract
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 1.6.0
>Reporter: Francis Guchie
>Assignee: Aleksandar Vidakovic
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: image-2022-03-06-12-50-03-752.png
>
>
> During the first boot of the apache fineract using tomcat 9, users will see
> this messages in the image below. I think we should have some "{*}if not
> exists{*}" conditions in the database migration scripts
>
> !image-2022-03-06-12-50-03-752.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1387) multiple field missing in savings account model ("GetClientsSavingsAccounts") while fetching clients acccounts
[
https://issues.apache.org/jira/browse/FINERACT-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-1387:
---
Fix Version/s: 3.0.0
(was: 1.5.0)
> multiple field missing in savings account model ("GetClientsSavingsAccounts")
> while fetching clients acccounts
> ---
>
> Key: FINERACT-1387
> URL: https://issues.apache.org/jira/browse/FINERACT-1387
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.5.0
>Reporter: Danish Jamal
>Assignee: Danish Jamal
>Priority: Major
> Labels: fineract-client-sdk, gsoc2021, swagger
> Fix For: 3.0.0
>
>
> One of the missing field is "depositType" and "subStatus" in generated
> "GetClientsSavingsAccounts" class(their are multiple fields missing in status
> model also).
> This model is used for the endpoint "clients/\{clientId}/accounts". Take a
> look at below json response which contains the actual response from the API.
>
> {code:java}
> // clients/{clientId}/accounts
> {
> "groupLoanIndividualMonitoringAccounts": [],
> "savingsAccounts": [
> {
> "id": 3,
> "accountNo": "3",
> "externalId": "537",
> "productId": 1,
> "productName": "Passbook Savings",
> "shortProductName": "PBSV",
> "status": {
> "id": 100,
> "code": "savingsAccountStatusType.submitted.and.pending.approval",
> "value": "Submitted and pending approval",
> "submittedAndPendingApproval": true,
> "approved": false,
> "rejected": false,
> "withdrawnByApplicant": false,
> "active": false,
> "closed": false,
> "prematureClosed": false,
> "transferInProgress": false,
> "transferOnHold": false,
> "matured": false
> },
> "currency": {
> "code": "USD",
> "name": "US Dollar",
> "decimalPlaces": 2,
> "inMultiplesOf": 0,
> "displaySymbol": "$",
> "nameCode": "currency.USD",
> "displayLabel": "US Dollar ($)"
> },
> "accountType": {
> "id": 1,
> "code": "accountType.individual",
> "value": "Individual"
> },
> "timeline": {
> "submittedOnDate": [
> 2020,
> 8,
> 18
> ],
> "submittedByUsername": "mifos",
> "submittedByFirstname": "App",
> "submittedByLastname": "Administrator"
> },
> "subStatus": {
> "id": 0,
> "code": "SavingsAccountSubStatusEnum.none",
> "value": "None",
> "none": true,
> "inactive": false,
> "dormant": false,
> "escheat": false,
> "block": false,
> "blockCredit": false,
> "blockDebit": false
> },
> "depositType": {
> "id": 100,
> "code": "depositAccountType.savingsDeposit",
> "value": "Savings"
> }
> },
> {
> "id": 1,
> "accountNo": "1",
> "productId": 1,
> "productName": "Passbook Savings",
> "shortProductName": "PBSV",
> "status": {
> "id": 300,
> "code": "savingsAccountStatusType.active",
> "value": "Active",
> "submittedAndPendingApproval": false,
> "approved": false,
> "rejected": false,
> "withdrawnByApplicant": false,
> "active": true,
> "closed": false,
> "prematureClosed": false,
> "transferInProgress": false,
> "transferOnHold": false,
> "matured": false
> },
> "currency": {
> "code": "USD",
> "name": "US Dollar",
> "decimalPlaces": 2,
> "inMultiplesOf": 0,
> "displaySymbol": "$",
> "nameCode": "currency.USD",
> "displayLabel": "US Dollar ($)"
> },
> "accountType": {
> "id": 1,
> "code": "accountType.individual",
> "value": "Individual"
> },
> "timeline": {
> "submittedOnDate": [
> 2021,
> 8,
> 9
> ],
> "submittedByUsername": "mifos",
> "submittedByFirstname": "App",
> "submittedByLastname": "Administrator",
> "approvedOnDate": [
> 2021,
> 8,
> 11
> ],
> "approvedByUsername": "mifos",
> "approvedByFirstname": "App",
> "approvedByLastname": "Administrator",
> "activatedOnDate": [
> 2021,
> 8,
> 12
> ]
> },
> "subStatus": {
> "id": 0,
> "code": "SavingsAccountSubStatusEnum.none",
> "value": "None",
> "none": true,
> "inactive": false,
> "dor
[jira] [Updated] (FINERACT-1385) multiple field missing in ResultsetColumnHeaderData
[
https://issues.apache.org/jira/browse/FINERACT-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-1385:
---
Fix Version/s: 3.0.0
(was: 1.5.0)
> multiple field missing in ResultsetColumnHeaderData
> ---
>
> Key: FINERACT-1385
> URL: https://issues.apache.org/jira/browse/FINERACT-1385
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.5.0
>Reporter: Danish Jamal
>Assignee: Danish Jamal
>Priority: Major
> Labels: datatable, fineract-client-sdk, gsoc2021, swagger
> Fix For: 3.0.0
>
>
> Their are some fields missing in the "ResultsetColumnHeaderData" model, which
> are returned from the api. Take a look at below snippets to compare the class
> definition and actual api response.
> {code:java}
> // fields defined in "ResultsetColumnHeaderData" model
> private String columnName;
> private String columnType;
> private Long columnLength;
> private String columnDisplayType;
> private String columnCode;
> private Boolean mandatory;
> private Boolean optional;
> private Boolean string;
> private Boolean codeValueDisplayType;
> private Boolean decimalDisplayType;
> private Boolean integerDisplayType;
> private Boolean dateDisplayType;
> private Boolean dateTimeDisplayType;
> private Boolean codeLookupDisplayType;
> private Boolean booleanDisplayType;
> {code}
> {code:java}
> // API json response
> {
> "columnName": "id",
> "columnType": "bigint",
> "columnLength": 0,
> "columnDisplayType": "INTEGER",
> "isColumnNullable": false,
> "isColumnPrimaryKey": true,
> "columnValues": []
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1877) Custom module templates with Skeletal
[ https://issues.apache.org/jira/browse/FINERACT-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1877: --- Fix Version/s: 3.0.0 (was: 1.10.0) > Custom module templates with Skeletal > - > > Key: FINERACT-1877 > URL: https://issues.apache.org/jira/browse/FINERACT-1877 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Minor > Fix For: 3.0.0 > > > https://github.com/cbmarcum/skeletal -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FINERACT-1587) Add new email field to Client
[ https://issues.apache.org/jira/browse/FINERACT-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic closed FINERACT-1587. -- Fix Version/s: (was: 1.9.0) Resolution: Invalid Looks like the PR was abandoned. > Add new email field to Client > - > > Key: FINERACT-1587 > URL: https://issues.apache.org/jira/browse/FINERACT-1587 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Minor > > As a user, I’d like to capture the email of a client without any validation. > *Acceptance criteria:* > * Email field is present for Client > * Email field is not mandatory > * Email field is not validated but a plain text field > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1587) Add new email field to Client
[ https://issues.apache.org/jira/browse/FINERACT-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic reassigned FINERACT-1587: -- Assignee: Aleksandar Vidakovic > Add new email field to Client > - > > Key: FINERACT-1587 > URL: https://issues.apache.org/jira/browse/FINERACT-1587 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Minor > Fix For: 1.9.0 > > > As a user, I’d like to capture the email of a client without any validation. > *Acceptance criteria:* > * Email field is present for Client > * Email field is not mandatory > * Email field is not validated but a plain text field > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1790) Reduce compile warnings
[ https://issues.apache.org/jira/browse/FINERACT-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1790: --- Fix Version/s: 1.10.0 (was: 1.9.0) > Reduce compile warnings > --- > > Key: FINERACT-1790 > URL: https://issues.apache.org/jira/browse/FINERACT-1790 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Minor > Fix For: 1.10.0 > > > We have currently 30-40 compiler warnings (mostly related to generic types) > that are polluting the compile output... this makes hard so search for errors > when on the command line. > Consider introducing OpenRewrite to help with the refactoring (might not > catch all issues). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1797) Remove tenant references from cache annotations
[ https://issues.apache.org/jira/browse/FINERACT-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1797: --- Fix Version/s: 1.10.0 (was: 1.9.0) > Remove tenant references from cache annotations > --- > > Key: FINERACT-1797 > URL: https://issues.apache.org/jira/browse/FINERACT-1797 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.10.0 > > > At the moment pretty much all "@Cache" annotations contain a reference to " > org.apache.fineract.infrastructure.core.service.ThreadLocalContextUtil" to > keep the cache separated by tenant. This makes the code quite unreadable, but > spreads the use of this util class all over the place and makes it quite > impossible to refactor the tenant mechanics. > As a preparation for this (=simplifying the tenant mechanics) the thread > context utility class will be removed from the cache annotations and replaced > with a central Spring Java config. This should also make it easier to split > up the code base into separate modules (one less dependency). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1803) Extension point: content repository
[ https://issues.apache.org/jira/browse/FINERACT-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1803: --- Fix Version/s: 1.10.0 (was: 1.9.0) > Extension point: content repository > --- > > Key: FINERACT-1803 > URL: https://issues.apache.org/jira/browse/FINERACT-1803 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.10.0 > > > This is a low hanging fruit. Currently the content repository is set via a > database configuration table. It would be better and more consistent to move > this to application.properties instead. Dependency injection best practices > are not followed, so we would improve that too and have - as a nice side > effect - less files to deal with, no more database dependency and users could > develop more custom content repositories. > While we are at it: remove the unnecessary distinction between "files" and > "images"... and within images: no need to distinguish between client, staff > or any other image for that matter. > Provide a migration tool to import existing legacy files/images into the new > repository format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1798) Extension point: command processing service
[ https://issues.apache.org/jira/browse/FINERACT-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1798: --- Fix Version/s: 1.10.0 (was: 1.9.0) > Extension point: command processing service > --- > > Key: FINERACT-1798 > URL: https://issues.apache.org/jira/browse/FINERACT-1798 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.10.0 > > > Make the current - synchronous - command processing service replaceable. > Provide an example implementation in custom modules based on Apache Camel + > LMAX disruptor routes. Provide enough documentation to enable users to > implement their own command processing (could by a way to integrate workflow > engines). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1142) Recommend OAuth security for production installations
[ https://issues.apache.org/jira/browse/FINERACT-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic reassigned FINERACT-1142: -- Assignee: Aleksandar Vidakovic > Recommend OAuth security for production installations > - > > Key: FINERACT-1142 > URL: https://issues.apache.org/jira/browse/FINERACT-1142 > Project: Apache Fineract > Issue Type: Sub-task > Components: Security >Affects Versions: 1.8.0 >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.9.0 > > > [~awasum] [~edcable] a reminder of our recent discussion as suggested by > Awasum -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1527) Conventional Commits
[ https://issues.apache.org/jira/browse/FINERACT-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1527: --- Fix Version/s: (was: 1.9.0) > Conventional Commits > > > Key: FINERACT-1527 > URL: https://issues.apache.org/jira/browse/FINERACT-1527 > Project: Apache Fineract > Issue Type: Task >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 3.0.0 > > > Format all commit messages according to: > [https://www.conventionalcommits.org/] > This will help a lot to create changelogs that people actually read. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1527) Conventional Commits
[ https://issues.apache.org/jira/browse/FINERACT-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1527: --- Fix Version/s: 3.0.0 > Conventional Commits > > > Key: FINERACT-1527 > URL: https://issues.apache.org/jira/browse/FINERACT-1527 > Project: Apache Fineract > Issue Type: Task >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.9.0, 3.0.0 > > > Format all commit messages according to: > [https://www.conventionalcommits.org/] > This will help a lot to create changelogs that people actually read. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1142) Recommend OAuth security for production installations
[ https://issues.apache.org/jira/browse/FINERACT-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1142: --- Parent: FINERACT-1908 Issue Type: Sub-task (was: Improvement) > Recommend OAuth security for production installations > - > > Key: FINERACT-1142 > URL: https://issues.apache.org/jira/browse/FINERACT-1142 > Project: Apache Fineract > Issue Type: Sub-task > Components: Security >Affects Versions: 1.8.0 >Reporter: Aleksandar Vidakovic >Priority: Major > Fix For: 1.9.0 > > > [~awasum] [~edcable] a reminder of our recent discussion as suggested by > Awasum -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1792) Update OAuth configuration and provide sample Keycloak setup
[ https://issues.apache.org/jira/browse/FINERACT-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-1792: --- Parent: FINERACT-1908 Issue Type: Sub-task (was: Improvement) > Update OAuth configuration and provide sample Keycloak setup > > > Key: FINERACT-1792 > URL: https://issues.apache.org/jira/browse/FINERACT-1792 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.9.0 > > > Do not use the Keycloak Spring Boot adapter, because it will be deprecated > soon. Use the officially preferred Spring OAuth client auto configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
