[jira] [Commented] (FINERACT-1683) Webhook URL is not executed after a webhook is created and triggered
[ https://issues.apache.org/jira/browse/FINERACT-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17578102#comment-17578102 ] Awasum Yannick commented on FINERACT-1683: -- [~francisguchie] .. next time you someone to add so they can show up in the assignee dropdown..just go here: [https://issues.apache.org/jira/plugins/servlet/project-config/FINERACT/roles] and add them to the Contributor role. > Webhook URL is not executed after a webhook is created and triggered > > > Key: FINERACT-1683 > URL: https://issues.apache.org/jira/browse/FINERACT-1683 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.6.0, 1.7.0 >Reporter: Davies Tobi Alex >Assignee: Davies Tobi Alex >Priority: Major > > When webhooks is created and triggered, the hook url is not called. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1683) Webhook URL is not executed after a webhook is created and triggered
[ https://issues.apache.org/jira/browse/FINERACT-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17578101#comment-17578101 ] Awasum Yannick commented on FINERACT-1683: -- Good work [~daviestobialex] ... Keep up. > Webhook URL is not executed after a webhook is created and triggered > > > Key: FINERACT-1683 > URL: https://issues.apache.org/jira/browse/FINERACT-1683 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.6.0, 1.7.0 >Reporter: Davies Tobi Alex >Assignee: Davies Tobi Alex >Priority: Major > > When webhooks is created and triggered, the hook url is not called. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1683) Webhook URL is not executed after a webhook is created and triggered
[ https://issues.apache.org/jira/browse/FINERACT-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick reassigned FINERACT-1683: Assignee: Davies Tobi Alex > Webhook URL is not executed after a webhook is created and triggered > > > Key: FINERACT-1683 > URL: https://issues.apache.org/jira/browse/FINERACT-1683 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.6.0, 1.7.0 >Reporter: Davies Tobi Alex >Assignee: Davies Tobi Alex >Priority: Major > > When webhooks is created and triggered, the hook url is not called. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1683) Webhook URL is not executed after a webhook is created and triggered
[ https://issues.apache.org/jira/browse/FINERACT-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17578097#comment-17578097 ] Awasum Yannick commented on FINERACT-1683: -- [~francisguchie] ..I will be happy to do that... I also recall you have a committer and PMC Apache Form to fill..which if you had done..you will have the permission to manage Fineract Jira issues, backlogs and merge MRs based on your view. > Webhook URL is not executed after a webhook is created and triggered > > > Key: FINERACT-1683 > URL: https://issues.apache.org/jira/browse/FINERACT-1683 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.6.0, 1.7.0 >Reporter: Davies Tobi Alex >Priority: Major > > When webhooks is created and triggered, the hook url is not called. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1687) Migrating from java.util.Date to java.time.LocalDate/LocalDateTime
[ https://issues.apache.org/jira/browse/FINERACT-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1687: - Labels: hardening (was: ) > Migrating from java.util.Date to java.time.LocalDate/LocalDateTime > -- > > Key: FINERACT-1687 > URL: https://issues.apache.org/jira/browse/FINERACT-1687 > Project: Apache Fineract > Issue Type: Improvement > Components: Performance >Affects Versions: 1.7.0 >Reporter: Adam Saghy >Assignee: Adam Saghy >Priority: Major > Labels: hardening > Fix For: 1.8.0 > > > java.util.Date is outdated and flawed. It is making hard to support multi > tenancy and multiple timezones. > See more: > [https://programminghints.com/2017/05/still-using-java-util-date-dont/] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1687) Migrating from java.util.Date to java.time.LocalDate/LocalDateTime
[ https://issues.apache.org/jira/browse/FINERACT-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1687: - Component/s: Performance > Migrating from java.util.Date to java.time.LocalDate/LocalDateTime > -- > > Key: FINERACT-1687 > URL: https://issues.apache.org/jira/browse/FINERACT-1687 > Project: Apache Fineract > Issue Type: Improvement > Components: Performance >Affects Versions: 1.7.0 >Reporter: Adam Saghy >Assignee: Adam Saghy >Priority: Major > > java.util.Date is outdated and flawed. It is making hard to support multi > tenancy and multiple timezones. > See more: > [https://programminghints.com/2017/05/still-using-java-util-date-dont/] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1687) Migrating from java.util.Date to java.time.LocalDate/LocalDateTime
[ https://issues.apache.org/jira/browse/FINERACT-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1687: - Affects Version/s: 1.7.0 > Migrating from java.util.Date to java.time.LocalDate/LocalDateTime > -- > > Key: FINERACT-1687 > URL: https://issues.apache.org/jira/browse/FINERACT-1687 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.7.0 >Reporter: Adam Saghy >Assignee: Adam Saghy >Priority: Major > > java.util.Date is outdated and flawed. It is making hard to support multi > tenancy and multiple timezones. > See more: > [https://programminghints.com/2017/05/still-using-java-util-date-dont/] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1687) Migrating from java.util.Date to java.time.LocalDate/LocalDateTime
[ https://issues.apache.org/jira/browse/FINERACT-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17577302#comment-17577302 ] Awasum Yannick commented on FINERACT-1687: -- Great work [~adamsaghy] ... Please [~avidakovic] and [~arnoldgalovics] wonder which fixed version this falls under? > Migrating from java.util.Date to java.time.LocalDate/LocalDateTime > -- > > Key: FINERACT-1687 > URL: https://issues.apache.org/jira/browse/FINERACT-1687 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Adam Saghy >Assignee: Adam Saghy >Priority: Major > > java.util.Date is outdated and flawed. It is making hard to support multi > tenancy and multiple timezones. > See more: > [https://programminghints.com/2017/05/still-using-java-util-date-dont/] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1649) Error for Journal entry table
[ https://issues.apache.org/jira/browse/FINERACT-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17561507#comment-17561507 ] Awasum Yannick commented on FINERACT-1649: -- Please add link to PR. > Error for Journal entry table > - > > Key: FINERACT-1649 > URL: https://issues.apache.org/jira/browse/FINERACT-1649 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.7.0 >Reporter: Dhaval Maniyar >Assignee: Dhaval Maniyar >Priority: Major > Fix For: 1.7.0 > > > org.springframework.dao.DataIntegrityViolationException: > PreparedStatementCallback; SQL [INSERT INTO > acc_gl_journal_entry(account_id,office_id,reversal_id,currency_code,transaction_id,savings_transaction_id,client_transaction_id,reversed,ref_num,manual_entry,entry_date,type_enum,amount,description,entity_type_enum,entity_id,created_date,lastmodified_date,is_running_balance_calculated,office_running_balance,organization_running_balance,payment_details_id,transaction_date,share_transaction_id, > createdby_id, lastmodifiedby_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, > ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]; ERROR: insert or update on table > "acc_gl_journal_entry" violates foreign key constraint > "FK_acc_gl_journal_entry_acc_gl_account" > Detail: Key (account_id)=(0) is not present in table "acc_gl_account".; > nested exception is org.postgresql.util.PSQLException: ERROR: insert or > update on table "acc_gl_journal_entry" violates foreign key constraint > "FK_acc_gl_journal_entry_acc_gl_account" > Detail: Key (account_id)=(0) is not present in table "acc_gl_account". > at > org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.doTranslate(SQLErrorCodeSQLExceptionTranslator.java:251) > at > org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:70) > at > org.springframework.jdbc.core.JdbcTemplate.translateException(JdbcTemplate.java:1541) > at > org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:667) > at > org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:691) > at > org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1034) > at > org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1088) > at > org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1079) > at > org.apache.fineract.portfolio.savings.service.SavingsSchedularInterestPoster.batchUpdateJournalEntries(SavingsSchedularInterestPoster.java:270) > at > org.apache.fineract.portfolio.savings.service.SavingsSchedularInterestPoster.batchUpdate(SavingsSchedularInterestPoster.java:351) > at > org.apache.fineract.portfolio.savings.service.SavingsSchedularInterestPoster.call(SavingsSchedularInterestPoster.java:195) > at > org.apache.fineract.portfolio.savings.service.SavingsSchedularInterestPoster.call(SavingsSchedularInterestPoster.java:61) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) > at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) > at java.base/java.lang.Thread.run(Thread.java:833) > Caused by: org.postgresql.util.PSQLException: ERROR: insert or update on > table "acc_gl_journal_entry" violates foreign key constraint > "FK_acc_gl_journal_entry_acc_gl_account" > Detail: Key (account_id)=(0) is not present in table "acc_gl_account". > at > org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2675) > at > org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2365) > at > org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:559) > at > org.postgresql.jdbc.PgStatement.internalExecuteBatch(PgStatement.java:887) > at org.postgresql.jdbc.PgStatement.executeBatch(PgStatement.java:910) > at > org.postgresql.jdbc.PgPreparedStatement.executeBatch(PgPreparedStatement.java:1649) > at > com.zaxxer.hikari.pool.ProxyStatement.executeBatch(ProxyStatement.java:127) > at > com.zaxxer.hikari.pool.HikariProxyPreparedStatement.executeBatch(HikariProxyPreparedStatement.java) > at > org.springframework.jdbc.core.JdbcTemplate.lambda$batchUpdate$4(JdbcTemplate.java:1048) > at > org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:651) > ... 12 common frames omitted -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1460) Change of currency name from Swaziland Lilangeni to ESwatini Lilangeni
[ https://issues.apache.org/jira/browse/FINERACT-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17467283#comment-17467283 ] Awasum Yannick commented on FINERACT-1460: -- This sounds like something important. Can someone send a PR. we will be happy to review and merge. Thanks. > Change of currency name from Swaziland Lilangeni to ESwatini Lilangeni > -- > > Key: FINERACT-1460 > URL: https://issues.apache.org/jira/browse/FINERACT-1460 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > > If you read > [here|https://www.investopedia.com/terms/forex/s/szl-swaziland-lilangeni.asp], > you will notice that in 2018 Swaziland was renamed to Eswatini. > Thus the new currency name is Eswatini Lilangeni even if the currency code > remains SZL -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (FINERACT-1440) Enable Daily Interest Posting for Savings
[ https://issues.apache.org/jira/browse/FINERACT-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441695#comment-17441695 ] Awasum Yannick commented on FINERACT-1440: -- [~infrastruct...@apache.org] Please check if user: [https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vickyshiv] is a troll as he has attached unrelated artifacts to different issues over the past few days. > Enable Daily Interest Posting for Savings > - > > Key: FINERACT-1440 > URL: https://issues.apache.org/jira/browse/FINERACT-1440 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Manoj Mohanan >Priority: Minor > Fix For: 1.6.0 > > > Add daily interest posting to savings account. > currently Savings account supports monthly, quarterly, annually, bi-annually > etc, > > Daily interest posting will be done as part of the Interest posting to > savings scheduler job which already exist. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FINERACT-1440) Enable Daily Interest Posting for Savings
[ https://issues.apache.org/jira/browse/FINERACT-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1440: - Attachment: (was: chrome_proxy.exe) > Enable Daily Interest Posting for Savings > - > > Key: FINERACT-1440 > URL: https://issues.apache.org/jira/browse/FINERACT-1440 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Manoj Mohanan >Priority: Minor > Fix For: 1.6.0 > > > Add daily interest posting to savings account. > currently Savings account supports monthly, quarterly, annually, bi-annually > etc, > > Daily interest posting will be done as part of the Interest posting to > savings scheduler job which already exist. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (FINERACT-1440) Enable Daily Interest Posting for Savings
[ https://issues.apache.org/jira/browse/FINERACT-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441694#comment-17441694 ] Awasum Yannick commented on FINERACT-1440: -- [~fynmanoj] I have removed the unrelated attachment. > Enable Daily Interest Posting for Savings > - > > Key: FINERACT-1440 > URL: https://issues.apache.org/jira/browse/FINERACT-1440 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Manoj Mohanan >Priority: Minor > Fix For: 1.6.0 > > > Add daily interest posting to savings account. > currently Savings account supports monthly, quarterly, annually, bi-annually > etc, > > Daily interest posting will be done as part of the Interest posting to > savings scheduler job which already exist. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (FINERACT-1430) Restricting access to clients by Status
[ https://issues.apache.org/jira/browse/FINERACT-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17439222#comment-17439222 ] Awasum Yannick commented on FINERACT-1430: -- Please add more details/description to your issues > Restricting access to clients by Status > > > Key: FINERACT-1430 > URL: https://issues.apache.org/jira/browse/FINERACT-1430 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Francis Guchie >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1420) API REST with Idempotency
[ https://issues.apache.org/jira/browse/FINERACT-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick reassigned FINERACT-1420: Assignee: Victor Romero > API REST with Idempotency > - > > Key: FINERACT-1420 > URL: https://issues.apache.org/jira/browse/FINERACT-1420 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Victor Romero >Assignee: Victor Romero >Priority: Major > Attachments: Idempotency - API Retry Fault Tolerance - Apache > Fineract (3).pdf > > > We have to make Apache Fineract API Rest _*fault-tolerant*_ in such a way > that the duplicate requests do not leave the system unstable. > https://restfulapi.net/idempotent-rest-apis/ > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-698) Ability to associate a GUID with every request
[ https://issues.apache.org/jira/browse/FINERACT-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438759#comment-17438759 ] Awasum Yannick commented on FINERACT-698: - @lingalamadhukar [~ct.madhukar] this work is becoming relevant now on the Fineract Dev List and here: https://github.com/apache/fineract/pull/1951, Please will you like to engage and try to help make your changes happen? > Ability to associate a GUID with every request > -- > > Key: FINERACT-698 > URL: https://issues.apache.org/jira/browse/FINERACT-698 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Madhukar Lingala >Priority: Minor > Labels: gsoc2019, technical > Time Spent: 20m > Remaining Estimate: 0h > > 1) Ability to associate a GUID with every request. The Client is responsible > for generating and passing the GUID with every request. As far as the > platform is concerned, we assume that the GUID is unique. We do not add any > constraint checks on the database to ensure that there is no impact on > performance. > 2) New API to query on the result of a request by passing the GUID as the > parameter. > 3) If the request was successful, the API returns the same response that the > successful original API call would have returned. If the original request has > failed, the API returns a resource not found response (since errors are not > logged into the system). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINCN-60) Update Readme
[ https://issues.apache.org/jira/browse/FINCN-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick reassigned FINCN-60: --- Assignee: Audrey Ndum > Update Readme > - > > Key: FINCN-60 > URL: https://issues.apache.org/jira/browse/FINCN-60 > Project: Fineract Cloud Native > Issue Type: Improvement > Components: fineract-cn-mobile >Reporter: Dilpreet Singh >Assignee: Audrey Ndum >Priority: Minor > Labels: outreachy2020 > > ReadMe.md does not have proper infromation.Actually for a begginer to start > with it is very difficult to understand the project. So it is requirede to > update readme file > Steps to reproduce: > will gather the required and additional information from Various Sources and > write it in readme in a proper manner > provide link to dummy login id > paste screenshot for app -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINCN-60) Update Readme
[ https://issues.apache.org/jira/browse/FINCN-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick resolved FINCN-60. - Resolution: Fixed > Update Readme > - > > Key: FINCN-60 > URL: https://issues.apache.org/jira/browse/FINCN-60 > Project: Fineract Cloud Native > Issue Type: Improvement > Components: fineract-cn-mobile >Reporter: Dilpreet Singh >Assignee: Audrey Ndum >Priority: Minor > Labels: outreachy2020 > > ReadMe.md does not have proper infromation.Actually for a begginer to start > with it is very difficult to understand the project. So it is requirede to > update readme file > Steps to reproduce: > will gather the required and additional information from Various Sources and > write it in readme in a proper manner > provide link to dummy login id > paste screenshot for app -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1152) Loan Rescheduling: Validation for End date to be on an instalment date should consider new Schedule
[ https://issues.apache.org/jira/browse/FINERACT-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17434295#comment-17434295 ] Awasum Yannick commented on FINERACT-1152: -- Any updates on this.. > Loan Rescheduling: Validation for End date to be on an instalment date should > consider new Schedule > > > Key: FINERACT-1152 > URL: https://issues.apache.org/jira/browse/FINERACT-1152 > Project: Apache Fineract > Issue Type: Bug >Reporter: Manoj Mohanan >Assignee: Manoj Mohanan >Priority: Minor > > In Loan Rescheduling while changing EMI, there is a validation for the input > End date to check whether End date falls on an installment date. > when multple rescheduling is applied together, for example : extend tenure > and change EMI, the newly added installment dates cannot be given as end > date, As the validation consider the current schedule for cheking the > validtity of End date. > This validation should be changed so that it should consider the future > schedule ( the Schedule that is generated as result of the rescheduling) for > the validation. > or remove the validation and take the nearest installment date before given > end date as the last installment to be modified. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1321) Create Loan Charges with options to be Deducted from Loan Amount So that Net loan Amount Minus charges is Disbursed
[ https://issues.apache.org/jira/browse/FINERACT-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick resolved FINERACT-1321. -- Resolution: Fixed This issue has now been fixed by [~Cadreia] here: [https://github.com/apache/fineract/pull/1841] Thank for the fix. [~TOLBERT] can you get the changes from the develop branch and see if you can be unblocked. Let us know how it goes. Closing this now. > Create Loan Charges with options to be Deducted from Loan Amount So that Net > loan Amount Minus charges is Disbursed > --- > > Key: FINERACT-1321 > URL: https://issues.apache.org/jira/browse/FINERACT-1321 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Loan >Affects Versions: 1.4.0 >Reporter: TOLBERT DEREk >Assignee: Audrey Ndum >Priority: Critical > Fix For: 1.6.0 > > > Customer Sometimes decides to give clients Loans while deducting the charge > amount from the Loan amount hence disbursing net amount. > This is not possible in mifosx hence customer cannot use system as most > customers cannot pay charges upfront > > any pointers we are stuck -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1321) Create Loan Charges with options to be Deducted from Loan Amount So that Net loan Amount Minus charges is Disbursed
[ https://issues.apache.org/jira/browse/FINERACT-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick reassigned FINERACT-1321: Assignee: Audrey Ndum > Create Loan Charges with options to be Deducted from Loan Amount So that Net > loan Amount Minus charges is Disbursed > --- > > Key: FINERACT-1321 > URL: https://issues.apache.org/jira/browse/FINERACT-1321 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Loan >Affects Versions: 1.4.0 >Reporter: TOLBERT DEREk >Assignee: Audrey Ndum >Priority: Critical > Fix For: 1.6.0 > > > Customer Sometimes decides to give clients Loans while deducting the charge > amount from the Loan amount hence disbursing net amount. > This is not possible in mifosx hence customer cannot use system as most > customers cannot pay charges upfront > > any pointers we are stuck -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1388) Deployment to fineract.dev Server Failures
[ https://issues.apache.org/jira/browse/FINERACT-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick resolved FINERACT-1388. -- Resolution: Fixed > Deployment to fineract.dev Server Failures > -- > > Key: FINERACT-1388 > URL: https://issues.apache.org/jira/browse/FINERACT-1388 > Project: Apache Fineract > Issue Type: Improvement > Components: Deployment, Test >Affects Versions: 1.5.0 >Reporter: Awasum Yannick >Assignee: Michael Vorburger >Priority: Major > Fix For: 1.6.0 > > > As seen here: [https://github.com/apache/fineract/runs/3285155938] the > deployment to the test server provided by [~vorburger] has been failing over > the past few weeks. A dependency on the deployment side may be broken or > needs update or replacement. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1388) Deployment to fineract.dev Server Failures
[ https://issues.apache.org/jira/browse/FINERACT-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1388: - Component/s: Test Deployment > Deployment to fineract.dev Server Failures > -- > > Key: FINERACT-1388 > URL: https://issues.apache.org/jira/browse/FINERACT-1388 > Project: Apache Fineract > Issue Type: Improvement > Components: Deployment, Test >Affects Versions: 1.5.0 >Reporter: Awasum Yannick >Assignee: Michael Vorburger >Priority: Major > Fix For: 1.6.0 > > > As seen here: [https://github.com/apache/fineract/runs/3285155938] the > deployment to the test server provided by [~vorburger] has been failing over > the past few weeks. A dependency on the deployment side may be broken or > needs update or replacement. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1388) Deployment to fineract.dev Server Failures
[ https://issues.apache.org/jira/browse/FINERACT-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick reassigned FINERACT-1388: Assignee: Michael Vorburger > Deployment to fineract.dev Server Failures > -- > > Key: FINERACT-1388 > URL: https://issues.apache.org/jira/browse/FINERACT-1388 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.5.0 >Reporter: Awasum Yannick >Assignee: Michael Vorburger >Priority: Major > Fix For: 1.6.0 > > > As seen here: [https://github.com/apache/fineract/runs/3285155938] the > deployment to the test server provided by [~vorburger] has been failing over > the past few weeks. A dependency on the deployment side may be broken or > needs update or replacement. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1388) Deployment to fineract.dev Server Failures
[ https://issues.apache.org/jira/browse/FINERACT-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17434288#comment-17434288 ] Awasum Yannick commented on FINERACT-1388: -- This is now working again right [~ptuomola] as it seems [~vorburger] fixed it. I am closing this one now. > Deployment to fineract.dev Server Failures > -- > > Key: FINERACT-1388 > URL: https://issues.apache.org/jira/browse/FINERACT-1388 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.5.0 >Reporter: Awasum Yannick >Priority: Major > Fix For: 1.6.0 > > > As seen here: [https://github.com/apache/fineract/runs/3285155938] the > deployment to the test server provided by [~vorburger] has been failing over > the past few weeks. A dependency on the deployment side may be broken or > needs update or replacement. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1406) Upgrade JDK 11 LTS to JDK 17 LTS
[ https://issues.apache.org/jira/browse/FINERACT-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1406: - Labels: tech-debt (was: beginner tech-debt) > Upgrade JDK 11 LTS to JDK 17 LTS > > > Key: FINERACT-1406 > URL: https://issues.apache.org/jira/browse/FINERACT-1406 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.5.0 >Reporter: Victor Romero >Assignee: Victor Romero >Priority: Major > Labels: tech-debt > Fix For: 1.6.0 > > > Upgrade JDK 11 LTS to JDK 17 LTS -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1406) Upgrade JDK 11 LTS to JDK 17 LTS
[ https://issues.apache.org/jira/browse/FINERACT-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17434287#comment-17434287 ] Awasum Yannick commented on FINERACT-1406: -- This should be picked up after Gradle 7.3 GA is released which will support JDK 17. > Upgrade JDK 11 LTS to JDK 17 LTS > > > Key: FINERACT-1406 > URL: https://issues.apache.org/jira/browse/FINERACT-1406 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.5.0 >Reporter: Victor Romero >Assignee: Victor Romero >Priority: Major > Labels: beginner, tech-debt > Fix For: 1.6.0 > > > Upgrade JDK 11 LTS to JDK 17 LTS -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1415) Make sure that using this pseudorandom number generator is safe
[
https://issues.apache.org/jira/browse/FINERACT-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Awasum Yannick resolved FINERACT-1415.
--
Resolution: Fixed
[~victorromero] Thank you for the fix. Closing this now.
> Make sure that using this pseudorandom number generator is safe
> ---
>
> Key: FINERACT-1415
> URL: https://issues.apache.org/jira/browse/FINERACT-1415
> Project: Apache Fineract
> Issue Type: Improvement
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0
>Reporter: Victor Romero
>Assignee: Victor Romero
>Priority: Major
> Labels: tech-debt
> Fix For: 1.6.0
>
>
> [https://sonarcloud.io/project/security_hotspots?id=apache_fineract#]
>
> Using pseudorandom number generators (PRNGs) is security-sensitive. For
> example, it has led in the past to the following vulnerabilities:
> * [CVE-2013-6386|http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6386]
> * [CVE-2006-3419|http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3419]
> * [CVE-2008-4102|http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-4102]
> When software generates predictable values in a context requiring
> unpredictability, it may be possible for an attacker to guess the next value
> that will be generated, and use this guess to impersonate another user or
> access sensitive information.
> As the {{java.util.Random}} class relies on a pseudorandom number generator,
> this class and relating {{java.lang.Math.random()}} method should not be used
> for security-critical applications or for protecting sensitive data. In such
> context, the {{java.security.SecureRandom}} class which relies on a
> cryptographically strong random number generator (RNG) should be used in
> place.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (FINERACT-1414) Fixed deposits are shown in savings account page from Global Search
[ https://issues.apache.org/jira/browse/FINERACT-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick resolved FINERACT-1414. -- Resolution: Fixed Closing this as PR: [https://github.com/apache/fineract/pull/1918] has been merged. > Fixed deposits are shown in savings account page from Global Search > --- > > Key: FINERACT-1414 > URL: https://issues.apache.org/jira/browse/FINERACT-1414 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Shemin Anto >Priority: Minor > Fix For: 1.6.0 > > > When searched from Global Search for a Fixed deposit, and while navigating > to that account it is shown in savings account details page. > Expected: Fixed deposits should navigate to Fixed deposit details page -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1415) Make sure that using this pseudorandom number generator is safe
[
https://issues.apache.org/jira/browse/FINERACT-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Awasum Yannick updated FINERACT-1415:
-
Component/s: Security
> Make sure that using this pseudorandom number generator is safe
> ---
>
> Key: FINERACT-1415
> URL: https://issues.apache.org/jira/browse/FINERACT-1415
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Security
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0
>Reporter: Victor Romero
>Assignee: Victor Romero
>Priority: Major
> Labels: tech-debt
> Fix For: 1.6.0
>
>
> [https://sonarcloud.io/project/security_hotspots?id=apache_fineract#]
>
> Using pseudorandom number generators (PRNGs) is security-sensitive. For
> example, it has led in the past to the following vulnerabilities:
> * [CVE-2013-6386|http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6386]
> * [CVE-2006-3419|http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3419]
> * [CVE-2008-4102|http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-4102]
> When software generates predictable values in a context requiring
> unpredictability, it may be possible for an attacker to guess the next value
> that will be generated, and use this guess to impersonate another user or
> access sensitive information.
> As the {{java.util.Random}} class relies on a pseudorandom number generator,
> this class and relating {{java.lang.Math.random()}} method should not be used
> for security-critical applications or for protecting sensitive data. In such
> context, the {{java.security.SecureRandom}} class which relies on a
> cryptographically strong random number generator (RNG) should be used in
> place.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (FINERACT-1416) Use Azul Zulu JDK11 LTS for Travis Builds
[ https://issues.apache.org/jira/browse/FINERACT-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick resolved FINERACT-1416. -- Resolution: Fixed Resolving this to fixed. Thanks to [~victorromero] for providing the PR. > Use Azul Zulu JDK11 LTS for Travis Builds > - > > Key: FINERACT-1416 > URL: https://issues.apache.org/jira/browse/FINERACT-1416 > Project: Apache Fineract > Issue Type: Improvement > Components: Test >Affects Versions: 1.5.0 >Reporter: Victor Romero >Assignee: Victor Romero >Priority: Major > Labels: beginner > Fix For: 1.6.0 > > > Taking the Awasum's email from the dev list > > "... As a recommendation from the recent ApacheCon FinTech/Fineract Track, > Azul Zulu JDK 11 is probably more efficient than other JDK vendors. > > See talks here: > [https://www.youtube.com/watch?v=sfp7ox3wMKk_channel=TheApacheFoundation] > and > [https://www.youtube.com/watch?v=fn9uhpOWrHk=1083s_channel=TheApacheFoundation] > > .." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1416) Use Azul Zulu JDK11 LTS for Travis Builds
[ https://issues.apache.org/jira/browse/FINERACT-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1416: - Fix Version/s: 1.6.0 > Use Azul Zulu JDK11 LTS for Travis Builds > - > > Key: FINERACT-1416 > URL: https://issues.apache.org/jira/browse/FINERACT-1416 > Project: Apache Fineract > Issue Type: Improvement > Components: Test >Affects Versions: 1.5.0 >Reporter: Victor Romero >Assignee: Victor Romero >Priority: Major > Labels: beginner > Fix For: 1.6.0 > > > Taking the Awasum's email from the dev list > > "... As a recommendation from the recent ApacheCon FinTech/Fineract Track, > Azul Zulu JDK 11 is probably more efficient than other JDK vendors. > > See talks here: > [https://www.youtube.com/watch?v=sfp7ox3wMKk_channel=TheApacheFoundation] > and > [https://www.youtube.com/watch?v=fn9uhpOWrHk=1083s_channel=TheApacheFoundation] > > .." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1416) Use Azul Zulu JDK11 LTS for Travis Builds
[ https://issues.apache.org/jira/browse/FINERACT-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1416: - Labels: beginner (was: ) > Use Azul Zulu JDK11 LTS for Travis Builds > - > > Key: FINERACT-1416 > URL: https://issues.apache.org/jira/browse/FINERACT-1416 > Project: Apache Fineract > Issue Type: Improvement > Components: Test >Affects Versions: 1.5.0 >Reporter: Victor Romero >Assignee: Victor Romero >Priority: Major > Labels: beginner > > Taking the Awasum's email from the dev list > > "... As a recommendation from the recent ApacheCon FinTech/Fineract Track, > Azul Zulu JDK 11 is probably more efficient than other JDK vendors. > > See talks here: > [https://www.youtube.com/watch?v=sfp7ox3wMKk_channel=TheApacheFoundation] > and > [https://www.youtube.com/watch?v=fn9uhpOWrHk=1083s_channel=TheApacheFoundation] > > .." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1416) Use Azul Zulu JDK11 LTS for Travis Builds
[ https://issues.apache.org/jira/browse/FINERACT-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1416: - Component/s: Test > Use Azul Zulu JDK11 LTS for Travis Builds > - > > Key: FINERACT-1416 > URL: https://issues.apache.org/jira/browse/FINERACT-1416 > Project: Apache Fineract > Issue Type: Improvement > Components: Test >Affects Versions: 1.5.0 >Reporter: Victor Romero >Assignee: Victor Romero >Priority: Major > > Taking the Awasum's email from the dev list > > "... As a recommendation from the recent ApacheCon FinTech/Fineract Track, > Azul Zulu JDK 11 is probably more efficient than other JDK vendors. > > See talks here: > [https://www.youtube.com/watch?v=sfp7ox3wMKk_channel=TheApacheFoundation] > and > [https://www.youtube.com/watch?v=fn9uhpOWrHk=1083s_channel=TheApacheFoundation] > > .." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1416) Use Azul Zulu JDK11 LTS
[ https://issues.apache.org/jira/browse/FINERACT-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick reassigned FINERACT-1416: Assignee: Victor Romero > Use Azul Zulu JDK11 LTS > > > Key: FINERACT-1416 > URL: https://issues.apache.org/jira/browse/FINERACT-1416 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.5.0 >Reporter: Victor Romero >Assignee: Victor Romero >Priority: Major > > Taking the Awasum's email from the dev list > > "... As a recommendation from the recent ApacheCon FinTech/Fineract Track, > Azul Zulu JDK 11 is probably more efficient than other JDK vendors. > > See talks here: > [https://www.youtube.com/watch?v=sfp7ox3wMKk_channel=TheApacheFoundation] > and > [https://www.youtube.com/watch?v=fn9uhpOWrHk=1083s_channel=TheApacheFoundation] > > .." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1416) Use Azul Zulu JDK11 LTS for Travis Builds
[ https://issues.apache.org/jira/browse/FINERACT-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1416: - Summary: Use Azul Zulu JDK11 LTS for Travis Builds (was: Use Azul Zulu JDK11 LTS ) > Use Azul Zulu JDK11 LTS for Travis Builds > - > > Key: FINERACT-1416 > URL: https://issues.apache.org/jira/browse/FINERACT-1416 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.5.0 >Reporter: Victor Romero >Assignee: Victor Romero >Priority: Major > > Taking the Awasum's email from the dev list > > "... As a recommendation from the recent ApacheCon FinTech/Fineract Track, > Azul Zulu JDK 11 is probably more efficient than other JDK vendors. > > See talks here: > [https://www.youtube.com/watch?v=sfp7ox3wMKk_channel=TheApacheFoundation] > and > [https://www.youtube.com/watch?v=fn9uhpOWrHk=1083s_channel=TheApacheFoundation] > > .." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1408) Add a unix shell to the Fineract Docker image
[
https://issues.apache.org/jira/browse/FINERACT-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17434205#comment-17434205
]
Awasum Yannick commented on FINERACT-1408:
--
Hi [~kjozsa1], with this PR:
[https://github.com/apache/fineract/pull/1930/files] now on the main branch.
Seems there could be a unix/linux shelled as part of the base image for
Fineract. [~victorromero] and [~ptuomola] is that the case? [~kjozsa1], check
and let us know. This might well have been solved by the above PR.
> Add a unix shell to the Fineract Docker image
> -
>
> Key: FINERACT-1408
> URL: https://issues.apache.org/jira/browse/FINERACT-1408
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: Kristof Jozsa
>Priority: Minor
>
> The current fineract Dockerfile uses {{gcr.io/distroless/java:11}} as the
> base image, which does not seem to have {{bash}} or any other usable shell.
> Having no shell makes it really hard to debug anything _inside_ the docker
> image - eg. I'm putting together a Kubernetes configuration with Configmap
> exporting environment variables, and it's about impossible to see what's
> going on inside the container without a shell.
> Please consider adding a shell, or using a docker base image which has one
> already (eg. the official {{openjdk:11}} image could work just fine).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-1405) Loan Collateral should be Optional while creating loan account
[ https://issues.apache.org/jira/browse/FINERACT-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433307#comment-17433307 ] Awasum Yannick commented on FINERACT-1405: -- Just a reminder. When closing an issue like this... try to provide the affected version and fix version for the issue that way the release notes will contain this fix. You doing Ok [~fynmanoj]. Keep up. > Loan Collateral should be Optional while creating loan account > -- > > Key: FINERACT-1405 > URL: https://issues.apache.org/jira/browse/FINERACT-1405 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Shreyas S Kumar >Priority: Minor > Fix For: 1.6.0 > > > Since there is no configuration option to switch on switch off collateral > from loan product, loan collateral should be non manadatory at loan account > creation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1405) Loan Collateral should be Optional while creating loan account
[ https://issues.apache.org/jira/browse/FINERACT-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1405: - Fix Version/s: 1.6.0 > Loan Collateral should be Optional while creating loan account > -- > > Key: FINERACT-1405 > URL: https://issues.apache.org/jira/browse/FINERACT-1405 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Shreyas S Kumar >Priority: Minor > Fix For: 1.6.0 > > > Since there is no configuration option to switch on switch off collateral > from loan product, loan collateral should be non manadatory at loan account > creation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1405) Loan Collateral should be Optional while creating loan account
[ https://issues.apache.org/jira/browse/FINERACT-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1405: - Component/s: Loan > Loan Collateral should be Optional while creating loan account > -- > > Key: FINERACT-1405 > URL: https://issues.apache.org/jira/browse/FINERACT-1405 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Shreyas S Kumar >Priority: Minor > Fix For: 1.6.0 > > > Since there is no configuration option to switch on switch off collateral > from loan product, loan collateral should be non manadatory at loan account > creation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1405) Loan Collateral should be Optional while creating loan account
[ https://issues.apache.org/jira/browse/FINERACT-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1405: - Affects Version/s: 1.5.0 > Loan Collateral should be Optional while creating loan account > -- > > Key: FINERACT-1405 > URL: https://issues.apache.org/jira/browse/FINERACT-1405 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Shreyas S Kumar >Priority: Minor > > Since there is no configuration option to switch on switch off collateral > from loan product, loan collateral should be non manadatory at loan account > creation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1403) Advance repayment issue after loan rescheduling
[ https://issues.apache.org/jira/browse/FINERACT-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1403: - Fix Version/s: (was: 1.5.1) 1.6.0 > Advance repayment issue after loan rescheduling > --- > > Key: FINERACT-1403 > URL: https://issues.apache.org/jira/browse/FINERACT-1403 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.5.0 >Reporter: bharath gowda >Assignee: Avik Ganguly >Priority: Major > Fix For: 1.6.0 > > Attachments: after advance repayment.png, before advance > repayment.png, product configuration.png > > > The loan repayment schedule is calculating the wrong principal when advance > payment is done after the loan reschedule is done. > > To reproduce, > 1. Create a loan product as per the shared screenshot > 2. Create a loan account and reschedule any installment and make the payment > for the rescheduled date > 3. Make an advance payment for an installment (for any installment after the > rescheduled installment) > Issue > when advance payment is done, the system is changing the principal amount, > and in turn, the installment is still not completely paid > because of this, the loan is considered overdue even if the payment is done > on/before time. > > Please find the example screenshot attached of the issue loan with complete > explanation and expected result > please do let me know if you need any more clarification -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1397) Interest calculation issue when repayment is made on the disbursement day
[ https://issues.apache.org/jira/browse/FINERACT-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1397: - Fix Version/s: (was: 1.5.1) 1.6.0 > Interest calculation issue when repayment is made on the disbursement day > - > > Key: FINERACT-1397 > URL: https://issues.apache.org/jira/browse/FINERACT-1397 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.5.0 >Reporter: bharath gowda >Assignee: Avik Ganguly >Priority: Major > Fix For: 1.6.0 > > Attachments: interest calculation issue.xlsx, product > configuration.png > > > Interest calculation is wrong when repayment is made on the disbursement day > for the daily interest loan product > > To reproduce the issue > 1. Create a loan product with daily interest calculation and interest > recalculation enabled.(have attached the screenshot of the loan product > configuration) > 2. Create/approve/disburse a loan account with a first repayment date of 30 > days gap from the disbursement date. > 3. Make the repayment on the same day of the disbursement date and verify the > interest > > check excel calculation for example issue and expected result. > > Any other date apart from the disbursement date repayment the interest > calculation is happening currently. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1397) Interest calculation issue when repayment is made on the disbursement day
[ https://issues.apache.org/jira/browse/FINERACT-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433302#comment-17433302 ] Awasum Yannick commented on FINERACT-1397: -- External Link is not accessible: [https://stepsai.atlassian.net/browse/CI-1188,] removing it from this issue. > Interest calculation issue when repayment is made on the disbursement day > - > > Key: FINERACT-1397 > URL: https://issues.apache.org/jira/browse/FINERACT-1397 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.5.0 >Reporter: bharath gowda >Assignee: Avik Ganguly >Priority: Major > Fix For: 1.5.1 > > Attachments: interest calculation issue.xlsx, product > configuration.png > > > Interest calculation is wrong when repayment is made on the disbursement day > for the daily interest loan product > > To reproduce the issue > 1. Create a loan product with daily interest calculation and interest > recalculation enabled.(have attached the screenshot of the loan product > configuration) > 2. Create/approve/disburse a loan account with a first repayment date of 30 > days gap from the disbursement date. > 3. Make the repayment on the same day of the disbursement date and verify the > interest > > check excel calculation for example issue and expected result. > > Any other date apart from the disbursement date repayment the interest > calculation is happening currently. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1397) Interest calculation issue when repayment is made on the disbursement day
[ https://issues.apache.org/jira/browse/FINERACT-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1397: - External issue URL: (was: https://stepsai.atlassian.net/browse/CI-1188) > Interest calculation issue when repayment is made on the disbursement day > - > > Key: FINERACT-1397 > URL: https://issues.apache.org/jira/browse/FINERACT-1397 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.5.0 >Reporter: bharath gowda >Assignee: Avik Ganguly >Priority: Major > Fix For: 1.5.1 > > Attachments: interest calculation issue.xlsx, product > configuration.png > > > Interest calculation is wrong when repayment is made on the disbursement day > for the daily interest loan product > > To reproduce the issue > 1. Create a loan product with daily interest calculation and interest > recalculation enabled.(have attached the screenshot of the loan product > configuration) > 2. Create/approve/disburse a loan account with a first repayment date of 30 > days gap from the disbursement date. > 3. Make the repayment on the same day of the disbursement date and verify the > interest > > check excel calculation for example issue and expected result. > > Any other date apart from the disbursement date repayment the interest > calculation is happening currently. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1407) Upgrade Code Coverage Libraries - JaCoco to support JDK 17
[ https://issues.apache.org/jira/browse/FINERACT-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick resolved FINERACT-1407. -- Resolution: Fixed Thanks for the fix: https://github.com/apache/fineract/pull/1892 > Upgrade Code Coverage Libraries - JaCoco to support JDK 17 > -- > > Key: FINERACT-1407 > URL: https://issues.apache.org/jira/browse/FINERACT-1407 > Project: Apache Fineract > Issue Type: Improvement > Components: Test >Affects Versions: 1.5.0 >Reporter: Victor Romero >Assignee: Victor Romero >Priority: Major > Labels: beginner > Fix For: 1.6.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1407) Upgrade Code Coverage Libraries - JaCoco to support JDK 17
[ https://issues.apache.org/jira/browse/FINERACT-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1407: - Component/s: Test > Upgrade Code Coverage Libraries - JaCoco to support JDK 17 > -- > > Key: FINERACT-1407 > URL: https://issues.apache.org/jira/browse/FINERACT-1407 > Project: Apache Fineract > Issue Type: Improvement > Components: Test >Affects Versions: 1.5.0 >Reporter: Victor Romero >Assignee: Victor Romero >Priority: Major > Labels: beginner > Fix For: 1.6.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1273) Trigger Based Client Email Notifications
[ https://issues.apache.org/jira/browse/FINERACT-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick resolved FINERACT-1273. -- Resolution: Fixed Thanks for the fix [~adonay28fiter]. Thanks for reporting this [~jborkenztain], please add more issues which your Devs will be working on. We will be ready to review whatever changes you all give back tot he community. [~ptuomola]. I am resolving this one as fixed. > Trigger Based Client Email Notifications > > > Key: FINERACT-1273 > URL: https://issues.apache.org/jira/browse/FINERACT-1273 > Project: Apache Fineract > Issue Type: New Feature > Components: Organization >Affects Versions: 1.5.0 >Reporter: Javier Borkenztain >Assignee: Adonay Porras >Priority: Major > Fix For: 1.6.0 > > > An SMTP/Email Account configuration is needed for the core; it can be added > in the System External Services section. > Then an Email Campaign option can be created within the Organization section. > This should have a Trigger option to define when the campaign will be sent. > Also, the body of the email should be a Rich Text Editor so parameters can be > included if needed. > Eventually, more specific trigger options can be developed so we could define > things like “Send email X days after the installment due date”. > For this, an email parameter should be included in the client creation form. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1273) Trigger Based Client Email Notifications
[ https://issues.apache.org/jira/browse/FINERACT-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1273: - Affects Version/s: (was: 1.5.1) 1.5.0 > Trigger Based Client Email Notifications > > > Key: FINERACT-1273 > URL: https://issues.apache.org/jira/browse/FINERACT-1273 > Project: Apache Fineract > Issue Type: New Feature > Components: Organization >Affects Versions: 1.5.0 >Reporter: Javier Borkenztain >Assignee: Adonay Porras >Priority: Major > Fix For: 1.6.0 > > > An SMTP/Email Account configuration is needed for the core; it can be added > in the System External Services section. > Then an Email Campaign option can be created within the Organization section. > This should have a Trigger option to define when the campaign will be sent. > Also, the body of the email should be a Rich Text Editor so parameters can be > included if needed. > Eventually, more specific trigger options can be developed so we could define > things like “Send email X days after the installment due date”. > For this, an email parameter should be included in the client creation form. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1273) Trigger Based Client Email Notifications
[ https://issues.apache.org/jira/browse/FINERACT-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433259#comment-17433259 ] Awasum Yannick commented on FINERACT-1273: -- [~al...@imperialcoop.com] do you want to create a new issue for your use case. Sounds important. > Trigger Based Client Email Notifications > > > Key: FINERACT-1273 > URL: https://issues.apache.org/jira/browse/FINERACT-1273 > Project: Apache Fineract > Issue Type: New Feature > Components: Organization >Affects Versions: 1.5.1 >Reporter: Javier Borkenztain >Assignee: Adonay Porras >Priority: Major > Fix For: 1.6.0 > > > An SMTP/Email Account configuration is needed for the core; it can be added > in the System External Services section. > Then an Email Campaign option can be created within the Organization section. > This should have a Trigger option to define when the campaign will be sent. > Also, the body of the email should be a Rich Text Editor so parameters can be > included if needed. > Eventually, more specific trigger options can be developed so we could define > things like “Send email X days after the installment due date”. > For this, an email parameter should be included in the client creation form. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-429) Node aware Scheduler
[
https://issues.apache.org/jira/browse/FINERACT-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Awasum Yannick updated FINERACT-429:
Component/s: Job Scheduler
> Node aware Scheduler
>
>
> Key: FINERACT-429
> URL: https://issues.apache.org/jira/browse/FINERACT-429
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Job Scheduler
>Affects Versions: 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0
>Reporter: Avik Ganguly
>Assignee: Benura Abeywardena
>Priority: Major
> Labels: gsoc, p2
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I believe multiple instances of the same job can be created by keeping the
> same job identifier but having different job keys. Additional parameter
> nodeId can be saved in the job table defaulting to 1. Default this parameter
> for a single-instance app-server to 1.
> If node.id parameter exists in the application yaml while deploying, set that
> system property to configured node id.
> Front-end can pass the configured node-id of the job instance as a query
> parameter.
> This will allow the organization to configure something like let Node 1 do
> all accruals for North zonal office and Node 2 do all accruals for South
> Zonal office.
> System admin can setup the corresponding mapping for node to IPs/URL while
> configuring load balancer. Example :-
> ```
> //Nginx - Default Round Robin Configuration
> http {
> upstream myapp1 {
> server srv1.example.com;
> server srv2.example.com;
> server srv3.example.com;
> }
>map $query_string $srvr {
> default https://myapp1 // If it doesn't match, send to load
> balancer
> node=1 srv1.example.com;
> node=2 srv2.example.com;
> node=3 srv3.example.com;
>}
> server {
> listen 80;
> location / {
> proxy_pass $srvr;
> }
> }
> }
> ```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FINERACT-429) Node aware Scheduler
[
https://issues.apache.org/jira/browse/FINERACT-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Awasum Yannick updated FINERACT-429:
Fix Version/s: 1.6.0
> Node aware Scheduler
>
>
> Key: FINERACT-429
> URL: https://issues.apache.org/jira/browse/FINERACT-429
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Job Scheduler
>Affects Versions: 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0
>Reporter: Avik Ganguly
>Assignee: Benura Abeywardena
>Priority: Major
> Labels: gsoc, p2
> Fix For: 1.6.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I believe multiple instances of the same job can be created by keeping the
> same job identifier but having different job keys. Additional parameter
> nodeId can be saved in the job table defaulting to 1. Default this parameter
> for a single-instance app-server to 1.
> If node.id parameter exists in the application yaml while deploying, set that
> system property to configured node id.
> Front-end can pass the configured node-id of the job instance as a query
> parameter.
> This will allow the organization to configure something like let Node 1 do
> all accruals for North zonal office and Node 2 do all accruals for South
> Zonal office.
> System admin can setup the corresponding mapping for node to IPs/URL while
> configuring load balancer. Example :-
> ```
> //Nginx - Default Round Robin Configuration
> http {
> upstream myapp1 {
> server srv1.example.com;
> server srv2.example.com;
> server srv3.example.com;
> }
>map $query_string $srvr {
> default https://myapp1 // If it doesn't match, send to load
> balancer
> node=1 srv1.example.com;
> node=2 srv2.example.com;
> node=3 srv3.example.com;
>}
> server {
> listen 80;
> location / {
> proxy_pass $srvr;
> }
> }
> }
> ```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (FINERACT-429) Node aware Scheduler
[
https://issues.apache.org/jira/browse/FINERACT-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Awasum Yannick resolved FINERACT-429.
-
Resolution: Fixed
Thanks for the fix [~BLasan]
> Node aware Scheduler
>
>
> Key: FINERACT-429
> URL: https://issues.apache.org/jira/browse/FINERACT-429
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Job Scheduler
>Affects Versions: 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0
>Reporter: Avik Ganguly
>Assignee: Benura Abeywardena
>Priority: Major
> Labels: gsoc, p2
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I believe multiple instances of the same job can be created by keeping the
> same job identifier but having different job keys. Additional parameter
> nodeId can be saved in the job table defaulting to 1. Default this parameter
> for a single-instance app-server to 1.
> If node.id parameter exists in the application yaml while deploying, set that
> system property to configured node id.
> Front-end can pass the configured node-id of the job instance as a query
> parameter.
> This will allow the organization to configure something like let Node 1 do
> all accruals for North zonal office and Node 2 do all accruals for South
> Zonal office.
> System admin can setup the corresponding mapping for node to IPs/URL while
> configuring load balancer. Example :-
> ```
> //Nginx - Default Round Robin Configuration
> http {
> upstream myapp1 {
> server srv1.example.com;
> server srv2.example.com;
> server srv3.example.com;
> }
>map $query_string $srvr {
> default https://myapp1 // If it doesn't match, send to load
> balancer
> node=1 srv1.example.com;
> node=2 srv2.example.com;
> node=3 srv3.example.com;
>}
> server {
> listen 80;
> location / {
> proxy_pass $srvr;
> }
> }
> }
> ```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FINERACT-429) Node aware Scheduler
[
https://issues.apache.org/jira/browse/FINERACT-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Awasum Yannick updated FINERACT-429:
Affects Version/s: 1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
> Node aware Scheduler
>
>
> Key: FINERACT-429
> URL: https://issues.apache.org/jira/browse/FINERACT-429
> Project: Apache Fineract
> Issue Type: Improvement
>Affects Versions: 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0
>Reporter: Avik Ganguly
>Assignee: Benura Abeywardena
>Priority: Major
> Labels: gsoc, p2
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I believe multiple instances of the same job can be created by keeping the
> same job identifier but having different job keys. Additional parameter
> nodeId can be saved in the job table defaulting to 1. Default this parameter
> for a single-instance app-server to 1.
> If node.id parameter exists in the application yaml while deploying, set that
> system property to configured node id.
> Front-end can pass the configured node-id of the job instance as a query
> parameter.
> This will allow the organization to configure something like let Node 1 do
> all accruals for North zonal office and Node 2 do all accruals for South
> Zonal office.
> System admin can setup the corresponding mapping for node to IPs/URL while
> configuring load balancer. Example :-
> ```
> //Nginx - Default Round Robin Configuration
> http {
> upstream myapp1 {
> server srv1.example.com;
> server srv2.example.com;
> server srv3.example.com;
> }
>map $query_string $srvr {
> default https://myapp1 // If it doesn't match, send to load
> balancer
> node=1 srv1.example.com;
> node=2 srv2.example.com;
> node=3 srv3.example.com;
>}
> server {
> listen 80;
> location / {
> proxy_pass $srvr;
> }
> }
> }
> ```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (FINERACT-1136) Backport Two Factor Auth Filter Type Cast Error to release branch 1.4.0
[ https://issues.apache.org/jira/browse/FINERACT-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick resolved FINERACT-1136. -- Resolution: Fixed > Backport Two Factor Auth Filter Type Cast Error to release branch 1.4.0 > > > Key: FINERACT-1136 > URL: https://issues.apache.org/jira/browse/FINERACT-1136 > Project: Apache Fineract > Issue Type: Sub-task > Components: Security >Affects Versions: 1.4.0, 1.6.0 >Reporter: Aleksandar Vidakovic >Assignee: Manoj Mohanan >Priority: Major > Fix For: 1.5.0 > > > Just as a reminder to backport to 1.4.0 as per conversation with [~edcable]. > Thanks [~fynmanoj] for taking care of this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1120) Two Factor Auth Filter Type Cast Error
[
https://issues.apache.org/jira/browse/FINERACT-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Awasum Yannick resolved FINERACT-1120.
--
Resolution: Fixed
> Two Factor Auth Filter Type Cast Error
> --
>
> Key: FINERACT-1120
> URL: https://issues.apache.org/jira/browse/FINERACT-1120
> Project: Apache Fineract
> Issue Type: Bug
> Components: Security
>Affects Versions: 1.3.0
>Reporter: Saransh Sharma
>Assignee: Manoj Mohanan
>Priority: Major
> Labels: beginner
> Fix For: 1.5.0
>
>
> Error :
> java.lang.ClassCastException: class java.lang.String cannot be cast to class
> org.springframework.security.authentication.AnonymousAuthenticationToken
> {code:java}
> // AppUser user = (AppUser) authentication.getPrincipal();
> {code}
> This line has some type casting error exception when running the two factor
> mode.
> To enable two factor mode you need to run with -Psecurity=twofactor
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FINERACT-1120) Two Factor Auth Filter Type Cast Error
[
https://issues.apache.org/jira/browse/FINERACT-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Awasum Yannick updated FINERACT-1120:
-
Labels: beginner (was: )
> Two Factor Auth Filter Type Cast Error
> --
>
> Key: FINERACT-1120
> URL: https://issues.apache.org/jira/browse/FINERACT-1120
> Project: Apache Fineract
> Issue Type: Bug
> Components: Security
>Affects Versions: 1.3.0
>Reporter: Saransh Sharma
>Assignee: Manoj Mohanan
>Priority: Major
> Labels: beginner
> Fix For: 1.5.0
>
>
> Error :
> java.lang.ClassCastException: class java.lang.String cannot be cast to class
> org.springframework.security.authentication.AnonymousAuthenticationToken
> {code:java}
> // AppUser user = (AppUser) authentication.getPrincipal();
> {code}
> This line has some type casting error exception when running the two factor
> mode.
> To enable two factor mode you need to run with -Psecurity=twofactor
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FINERACT-1136) Backport Two Factor Auth Filter Type Cast Error to release branch 1.4.0
[ https://issues.apache.org/jira/browse/FINERACT-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1136: - Fix Version/s: (was: 1.6.0) 1.5.0 > Backport Two Factor Auth Filter Type Cast Error to release branch 1.4.0 > > > Key: FINERACT-1136 > URL: https://issues.apache.org/jira/browse/FINERACT-1136 > Project: Apache Fineract > Issue Type: Sub-task > Components: Security >Affects Versions: 1.4.0, 1.6.0 >Reporter: Aleksandar Vidakovic >Assignee: Manoj Mohanan >Priority: Major > Fix For: 1.5.0 > > > Just as a reminder to backport to 1.4.0 as per conversation with [~edcable]. > Thanks [~fynmanoj] for taking care of this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1120) Two Factor Auth Filter Type Cast Error
[
https://issues.apache.org/jira/browse/FINERACT-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Awasum Yannick updated FINERACT-1120:
-
Component/s: Security
> Two Factor Auth Filter Type Cast Error
> --
>
> Key: FINERACT-1120
> URL: https://issues.apache.org/jira/browse/FINERACT-1120
> Project: Apache Fineract
> Issue Type: Bug
> Components: Security
>Affects Versions: 1.3.0
>Reporter: Saransh Sharma
>Assignee: Manoj Mohanan
>Priority: Major
> Fix For: 1.5.0
>
>
> Error :
> java.lang.ClassCastException: class java.lang.String cannot be cast to class
> org.springframework.security.authentication.AnonymousAuthenticationToken
> {code:java}
> // AppUser user = (AppUser) authentication.getPrincipal();
> {code}
> This line has some type casting error exception when running the two factor
> mode.
> To enable two factor mode you need to run with -Psecurity=twofactor
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FINERACT-1120) Two Factor Auth Filter Type Cast Error
[
https://issues.apache.org/jira/browse/FINERACT-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Awasum Yannick updated FINERACT-1120:
-
Fix Version/s: (was: 1.6.0)
1.5.0
> Two Factor Auth Filter Type Cast Error
> --
>
> Key: FINERACT-1120
> URL: https://issues.apache.org/jira/browse/FINERACT-1120
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Saransh Sharma
>Assignee: Manoj Mohanan
>Priority: Major
> Fix For: 1.5.0
>
>
> Error :
> java.lang.ClassCastException: class java.lang.String cannot be cast to class
> org.springframework.security.authentication.AnonymousAuthenticationToken
> {code:java}
> // AppUser user = (AppUser) authentication.getPrincipal();
> {code}
> This line has some type casting error exception when running the two factor
> mode.
> To enable two factor mode you need to run with -Psecurity=twofactor
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (FINERACT-1151) Multiple Loan Reschedule on the same loan does not consider interest adjustment done by previous rescheduling
[ https://issues.apache.org/jira/browse/FINERACT-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick resolved FINERACT-1151. -- Assignee: Manoj Mohanan (was: Awasum Yannick) Resolution: Fixed Thanks for fixing this [~fynmanoj]. > Multiple Loan Reschedule on the same loan does not consider interest > adjustment done by previous rescheduling > -- > > Key: FINERACT-1151 > URL: https://issues.apache.org/jira/browse/FINERACT-1151 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.2.0, 1.3.0, 1.4.0 >Reporter: Manoj Mohanan >Assignee: Manoj Mohanan >Priority: Major > Labels: hard, tech-debt > Fix For: 1.5.0 > > Attachments: Multiple Rescheduling With Holiday Period (1).xlsx > > > When applying multiple interdependent loan rescheduling involving holiday > period, system is not able to carry the changes applied by the previous > reschedule to the latest reschedule. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1151) Multiple Loan Reschedule on the same loan does not consider interest adjustment done by previous rescheduling
[ https://issues.apache.org/jira/browse/FINERACT-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1151: - Labels: hard tech-debt (was: ) > Multiple Loan Reschedule on the same loan does not consider interest > adjustment done by previous rescheduling > -- > > Key: FINERACT-1151 > URL: https://issues.apache.org/jira/browse/FINERACT-1151 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.2.0, 1.3.0, 1.4.0 >Reporter: Manoj Mohanan >Assignee: Manoj Mohanan >Priority: Major > Labels: hard, tech-debt > Fix For: 1.5.0 > > Attachments: Multiple Rescheduling With Holiday Period (1).xlsx > > > When applying multiple interdependent loan rescheduling involving holiday > period, system is not able to carry the changes applied by the previous > reschedule to the latest reschedule. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1151) Multiple Loan Reschedule on the same loan does not consider interest adjustment done by previous rescheduling
[ https://issues.apache.org/jira/browse/FINERACT-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick reassigned FINERACT-1151: Assignee: Awasum Yannick (was: Manoj Mohanan) > Multiple Loan Reschedule on the same loan does not consider interest > adjustment done by previous rescheduling > -- > > Key: FINERACT-1151 > URL: https://issues.apache.org/jira/browse/FINERACT-1151 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.2.0, 1.3.0, 1.4.0 >Reporter: Manoj Mohanan >Assignee: Awasum Yannick >Priority: Major > Labels: hard, tech-debt > Fix For: 1.5.0 > > Attachments: Multiple Rescheduling With Holiday Period (1).xlsx > > > When applying multiple interdependent loan rescheduling involving holiday > period, system is not able to carry the changes applied by the previous > reschedule to the latest reschedule. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1151) Multiple Loan Reschedule on the same loan does not consider interest adjustment done by previous rescheduling
[ https://issues.apache.org/jira/browse/FINERACT-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1151: - Component/s: Loan > Multiple Loan Reschedule on the same loan does not consider interest > adjustment done by previous rescheduling > -- > > Key: FINERACT-1151 > URL: https://issues.apache.org/jira/browse/FINERACT-1151 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.2.0, 1.3.0, 1.4.0 >Reporter: Manoj Mohanan >Assignee: Manoj Mohanan >Priority: Major > Fix For: 1.5.0 > > Attachments: Multiple Rescheduling With Holiday Period (1).xlsx > > > When applying multiple interdependent loan rescheduling involving holiday > period, system is not able to carry the changes applied by the previous > reschedule to the latest reschedule. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1151) Multiple Loan Reschedule on the same loan does not consider interest adjustment done by previous rescheduling
[ https://issues.apache.org/jira/browse/FINERACT-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1151: - Affects Version/s: 1.2.0 1.3.0 1.4.0 > Multiple Loan Reschedule on the same loan does not consider interest > adjustment done by previous rescheduling > -- > > Key: FINERACT-1151 > URL: https://issues.apache.org/jira/browse/FINERACT-1151 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.2.0, 1.3.0, 1.4.0 >Reporter: Manoj Mohanan >Assignee: Manoj Mohanan >Priority: Major > Attachments: Multiple Rescheduling With Holiday Period (1).xlsx > > > When applying multiple interdependent loan rescheduling involving holiday > period, system is not able to carry the changes applied by the previous > reschedule to the latest reschedule. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1151) Multiple Loan Reschedule on the same loan does not consider interest adjustment done by previous rescheduling
[ https://issues.apache.org/jira/browse/FINERACT-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1151: - Fix Version/s: 1.5.0 > Multiple Loan Reschedule on the same loan does not consider interest > adjustment done by previous rescheduling > -- > > Key: FINERACT-1151 > URL: https://issues.apache.org/jira/browse/FINERACT-1151 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.2.0, 1.3.0, 1.4.0 >Reporter: Manoj Mohanan >Assignee: Manoj Mohanan >Priority: Major > Fix For: 1.5.0 > > Attachments: Multiple Rescheduling With Holiday Period (1).xlsx > > > When applying multiple interdependent loan rescheduling involving holiday > period, system is not able to carry the changes applied by the previous > reschedule to the latest reschedule. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINCN-202) Add functionality to edit loan details
[ https://issues.apache.org/jira/browse/FINCN-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433256#comment-17433256 ] Awasum Yannick commented on FINCN-202: -- What is the status of this one.. Seems no PR was ever sent for this? > Add functionality to edit loan details > -- > > Key: FINCN-202 > URL: https://issues.apache.org/jira/browse/FINCN-202 > Project: Fineract Cloud Native > Issue Type: New Feature > Components: fineract-cn-mobile >Reporter: Ahmad Jawid Muhammadi >Priority: Minor > > Currently, the app does not have the functionality for editing the loan > details. When you click on the edit menu on CustomerLoanDetailsFragment a > pop-up message says it is under construction. > *How to reproduce?* > # on Dashboard -> Click on View Customer button > # Click on any item from Customers -> Click on loan account > # Click on any item from loan accounts -> Click on the edit menu > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1396) Improve bulk import tool
[ https://issues.apache.org/jira/browse/FINERACT-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick resolved FINERACT-1396. -- Resolution: Fixed Thanks for opening and fixing this issue [~Cadreia]. [~ptuomola], I am closing this one given you merged the PR: https://github.com/apache/fineract/pull/1842 > Improve bulk import tool > > > Key: FINERACT-1396 > URL: https://issues.apache.org/jira/browse/FINERACT-1396 > Project: Apache Fineract > Issue Type: Improvement > Components: DataImportTool, Loan >Affects Versions: 1.4.0, 1.5.0 >Reporter: Audrey Ndum >Assignee: Audrey Ndum >Priority: Major > Labels: tech-debt > Fix For: 1.6.0 > > > The bulk import tool is failing some levels where the tool is not really up > to date with all the improvements that have been done so far especially > around loan products. > The idea will be to bring this tool up to standards with the latest code by > improving on the attributes and constraints and validations of the tool. > Another improvement will be to enable multiple charges in the tool as so far > it is only possible to include 1 charge. with imported loans. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1396) Improve bulk import tool
[ https://issues.apache.org/jira/browse/FINERACT-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick reassigned FINERACT-1396: Assignee: Audrey Ndum > Improve bulk import tool > > > Key: FINERACT-1396 > URL: https://issues.apache.org/jira/browse/FINERACT-1396 > Project: Apache Fineract > Issue Type: Improvement > Components: DataImportTool, Loan >Affects Versions: 1.4.0, 1.5.0 >Reporter: Audrey Ndum >Assignee: Audrey Ndum >Priority: Major > Labels: tech-debt > Fix For: 1.6.0 > > > The bulk import tool is failing some levels where the tool is not really up > to date with all the improvements that have been done so far especially > around loan products. > The idea will be to bring this tool up to standards with the latest code by > improving on the attributes and constraints and validations of the tool. > Another improvement will be to enable multiple charges in the tool as so far > it is only possible to include 1 charge. with imported loans. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1396) Improve bulk import tool
[ https://issues.apache.org/jira/browse/FINERACT-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1396: - Component/s: Loan DataImportTool > Improve bulk import tool > > > Key: FINERACT-1396 > URL: https://issues.apache.org/jira/browse/FINERACT-1396 > Project: Apache Fineract > Issue Type: Improvement > Components: DataImportTool, Loan >Affects Versions: 1.4.0, 1.5.0 >Reporter: Audrey Ndum >Priority: Major > > The bulk import tool is failing some levels where the tool is not really up > to date with all the improvements that have been done so far especially > around loan products. > The idea will be to bring this tool up to standards with the latest code by > improving on the attributes and constraints and validations of the tool. > Another improvement will be to enable multiple charges in the tool as so far > it is only possible to include 1 charge. with imported loans. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1396) Improve bulk import tool
[ https://issues.apache.org/jira/browse/FINERACT-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1396: - Labels: tech-debt (was: ) > Improve bulk import tool > > > Key: FINERACT-1396 > URL: https://issues.apache.org/jira/browse/FINERACT-1396 > Project: Apache Fineract > Issue Type: Improvement > Components: DataImportTool, Loan >Affects Versions: 1.4.0, 1.5.0 >Reporter: Audrey Ndum >Priority: Major > Labels: tech-debt > > The bulk import tool is failing some levels where the tool is not really up > to date with all the improvements that have been done so far especially > around loan products. > The idea will be to bring this tool up to standards with the latest code by > improving on the attributes and constraints and validations of the tool. > Another improvement will be to enable multiple charges in the tool as so far > it is only possible to include 1 charge. with imported loans. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1396) Improve bulk import tool
[ https://issues.apache.org/jira/browse/FINERACT-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1396: - Fix Version/s: 1.6.0 > Improve bulk import tool > > > Key: FINERACT-1396 > URL: https://issues.apache.org/jira/browse/FINERACT-1396 > Project: Apache Fineract > Issue Type: Improvement > Components: DataImportTool, Loan >Affects Versions: 1.4.0, 1.5.0 >Reporter: Audrey Ndum >Priority: Major > Labels: tech-debt > Fix For: 1.6.0 > > > The bulk import tool is failing some levels where the tool is not really up > to date with all the improvements that have been done so far especially > around loan products. > The idea will be to bring this tool up to standards with the latest code by > improving on the attributes and constraints and validations of the tool. > Another improvement will be to enable multiple charges in the tool as so far > it is only possible to include 1 charge. with imported loans. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1313) Holiday functianality not working
[ https://issues.apache.org/jira/browse/FINERACT-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1313: - Affects Version/s: 1.5.0 > Holiday functianality not working > - > > Key: FINERACT-1313 > URL: https://issues.apache.org/jira/browse/FINERACT-1313 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Organization >Affects Versions: 1.4.0, 1.5.0 >Reporter: bharath gowda >Assignee: Audrey Ndum >Priority: Critical > Labels: hard, tech-debt > Fix For: 1.6.0 > > > holiday set is not rescheduling the installments of both existing loans(even > after scheduler job runs successfully ) and new loans created > > To reproduce > > 1. Create and activate a holiday > 2. Create/approve/disburse a loan in such a way the installment falls on the > created holiday date. > * expected behavior- the system should have rescheduled the installment as > per the holiday configured, but it doesn't. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1313) Holiday functianality not working
[ https://issues.apache.org/jira/browse/FINERACT-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick resolved FINERACT-1313. -- Resolution: Fixed > Holiday functianality not working > - > > Key: FINERACT-1313 > URL: https://issues.apache.org/jira/browse/FINERACT-1313 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Organization >Affects Versions: 1.4.0, 1.5.0 >Reporter: bharath gowda >Assignee: Audrey Ndum >Priority: Critical > Labels: hard, tech-debt > Fix For: 1.6.0 > > > holiday set is not rescheduling the installments of both existing loans(even > after scheduler job runs successfully ) and new loans created > > To reproduce > > 1. Create and activate a holiday > 2. Create/approve/disburse a loan in such a way the installment falls on the > created holiday date. > * expected behavior- the system should have rescheduled the installment as > per the holiday configured, but it doesn't. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1313) Holiday functianality not working
[ https://issues.apache.org/jira/browse/FINERACT-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1313: - Labels: hard tech-debt (was: ) > Holiday functianality not working > - > > Key: FINERACT-1313 > URL: https://issues.apache.org/jira/browse/FINERACT-1313 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Organization >Affects Versions: 1.4.0 >Reporter: bharath gowda >Assignee: Audrey Ndum >Priority: Critical > Labels: hard, tech-debt > Fix For: 1.6.0 > > > holiday set is not rescheduling the installments of both existing loans(even > after scheduler job runs successfully ) and new loans created > > To reproduce > > 1. Create and activate a holiday > 2. Create/approve/disburse a loan in such a way the installment falls on the > created holiday date. > * expected behavior- the system should have rescheduled the installment as > per the holiday configured, but it doesn't. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1313) Holiday functianality not working
[ https://issues.apache.org/jira/browse/FINERACT-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1313: - Component/s: Loan > Holiday functianality not working > - > > Key: FINERACT-1313 > URL: https://issues.apache.org/jira/browse/FINERACT-1313 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Organization >Affects Versions: 1.4.0 >Reporter: bharath gowda >Assignee: Audrey Ndum >Priority: Critical > Fix For: 1.6.0 > > > holiday set is not rescheduling the installments of both existing loans(even > after scheduler job runs successfully ) and new loans created > > To reproduce > > 1. Create and activate a holiday > 2. Create/approve/disburse a loan in such a way the installment falls on the > created holiday date. > * expected behavior- the system should have rescheduled the installment as > per the holiday configured, but it doesn't. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (FINERACT-1313) Holiday functianality not working
[ https://issues.apache.org/jira/browse/FINERACT-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick reopened FINERACT-1313: -- Assignee: Audrey Ndum Assigning [~Cadreia] to issue. > Holiday functianality not working > - > > Key: FINERACT-1313 > URL: https://issues.apache.org/jira/browse/FINERACT-1313 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Affects Versions: 1.4.0 >Reporter: bharath gowda >Assignee: Audrey Ndum >Priority: Critical > Fix For: 1.6.0 > > > holiday set is not rescheduling the installments of both existing loans(even > after scheduler job runs successfully ) and new loans created > > To reproduce > > 1. Create and activate a holiday > 2. Create/approve/disburse a loan in such a way the installment falls on the > created holiday date. > * expected behavior- the system should have rescheduled the installment as > per the holiday configured, but it doesn't. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1313) Holiday functianality not working
[ https://issues.apache.org/jira/browse/FINERACT-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433253#comment-17433253 ] Awasum Yannick commented on FINERACT-1313: -- [~Cadreia] Did you work on this? I see the PR linked was sent by you. [~bgowda] when closing issues..make sure we always have the author of the PR as the assignee so they can get credit and recognition for their work. > Holiday functianality not working > - > > Key: FINERACT-1313 > URL: https://issues.apache.org/jira/browse/FINERACT-1313 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Affects Versions: 1.4.0 >Reporter: bharath gowda >Priority: Critical > Fix For: 1.6.0 > > > holiday set is not rescheduling the installments of both existing loans(even > after scheduler job runs successfully ) and new loans created > > To reproduce > > 1. Create and activate a holiday > 2. Create/approve/disburse a loan in such a way the installment falls on the > created holiday date. > * expected behavior- the system should have rescheduled the installment as > per the holiday configured, but it doesn't. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1349) Balloon Payment: Reschedule: change Fixed Principal percentage for each installment on active loan
[ https://issues.apache.org/jira/browse/FINERACT-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433249#comment-17433249 ] Awasum Yannick commented on FINERACT-1349: -- Please...look for the PR fixing this issue and if it has been merged..please close this issue. Thanks. Looks like there is one other issue like this... please help us sort them out. > Balloon Payment: Reschedule: change Fixed Principal percentage for each > installment on active loan > -- > > Key: FINERACT-1349 > URL: https://issues.apache.org/jira/browse/FINERACT-1349 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Manoj Mohanan >Assignee: Manoj Mohanan >Priority: Minor > Attachments: Screenshot 2021-04-19 at 17.48.04.png > > > This is part of inventory financing requirement. > Linked feature : https://issues.apache.org/jira/browse/FINERACT-1348 > Add feature to modify the new settings/parameter "fixed principal percentage > per installment " on an active loan. > This can be done as reschedule feature along with other reschedule options. > > post disbursement, go to reschedule loan option to modify the principal > percentage. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1348) Balloon Payment: Fix Principal Portion for each installment to a fixed percentage value
[ https://issues.apache.org/jira/browse/FINERACT-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433248#comment-17433248 ] Awasum Yannick commented on FINERACT-1348: -- Please...look for the PR fixing this issue and if it has been merged..please close this issue. Thanks. > Balloon Payment: Fix Principal Portion for each installment to a fixed > percentage value > --- > > Key: FINERACT-1348 > URL: https://issues.apache.org/jira/browse/FINERACT-1348 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Manoj Mohanan >Assignee: Manoj Mohanan >Priority: Minor > Attachments: Screenshot 2021-04-17 at 22.58.08.png > > > This is part of inventory financing requirement. > To achive Balloon Payment: > For a fixed principal amortization loan, by fixing the Loan term and > principal percentage per installment, the remaining principal is added to the > last installment and thus the last installment becomes balloon payment. > A new settings( parameter) 'fixed principal percentage per installment " to > be introduced to loan product as well as Loan application with CRUD changes > for the same. > fix the principal percentage per installment` in both Flat interest method > and Declining balance method schedule > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1399) Tag /Tag Id is mandatory in Bulk Import for chart of account
[ https://issues.apache.org/jira/browse/FINERACT-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick resolved FINERACT-1399. -- Resolution: Fixed Thank you [~AnkiR] for fixing this. [~ptuomola], [~fynmanoj].. I am closing this issue as fixed. Adjust as you see fit if am wrong. > Tag /Tag Id is mandatory in Bulk Import for chart of account > > > Key: FINERACT-1399 > URL: https://issues.apache.org/jira/browse/FINERACT-1399 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Ankita Ranjan >Priority: Minor > Labels: beginner, tech-debt > Fix For: 1.6.0 > > > While doing Bulk import for chart of accounts, the Tag / Tag Id are mandatory > where as these are not mandatory for creating chart of account. > Expected result: Tag/ Tag Id should not be mandatory for bulk import. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1399) Tag /Tag Id is mandatory in Bulk Import for chart of account
[ https://issues.apache.org/jira/browse/FINERACT-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick reassigned FINERACT-1399: Assignee: Ankita Ranjan (was: Manoj Mohanan) > Tag /Tag Id is mandatory in Bulk Import for chart of account > > > Key: FINERACT-1399 > URL: https://issues.apache.org/jira/browse/FINERACT-1399 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Ankita Ranjan >Priority: Minor > Labels: beginner, tech-debt > Fix For: 1.6.0 > > > While doing Bulk import for chart of accounts, the Tag / Tag Id are mandatory > where as these are not mandatory for creating chart of account. > Expected result: Tag/ Tag Id should not be mandatory for bulk import. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1399) Tag /Tag Id is mandatory in Bulk Import for chart of account
[ https://issues.apache.org/jira/browse/FINERACT-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1399: - Labels: beginner tech-debt (was: ) > Tag /Tag Id is mandatory in Bulk Import for chart of account > > > Key: FINERACT-1399 > URL: https://issues.apache.org/jira/browse/FINERACT-1399 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Manoj Mohanan >Priority: Minor > Labels: beginner, tech-debt > Fix For: 1.6.0 > > > While doing Bulk import for chart of accounts, the Tag / Tag Id are mandatory > where as these are not mandatory for creating chart of account. > Expected result: Tag/ Tag Id should not be mandatory for bulk import. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1399) Tag /Tag Id is mandatory in Bulk Import for chart of account
[ https://issues.apache.org/jira/browse/FINERACT-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433246#comment-17433246 ] Awasum Yannick commented on FINERACT-1399: -- Sorry my mistake..here is the right PR: https://github.com/apache/fineract/pull/1887 > Tag /Tag Id is mandatory in Bulk Import for chart of account > > > Key: FINERACT-1399 > URL: https://issues.apache.org/jira/browse/FINERACT-1399 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Manoj Mohanan >Priority: Minor > Fix For: 1.6.0 > > > While doing Bulk import for chart of accounts, the Tag / Tag Id are mandatory > where as these are not mandatory for creating chart of account. > Expected result: Tag/ Tag Id should not be mandatory for bulk import. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1399) Tag /Tag Id is mandatory in Bulk Import for chart of account
[ https://issues.apache.org/jira/browse/FINERACT-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433245#comment-17433245 ] Awasum Yannick commented on FINERACT-1399: -- [~fynmanoj] which PRs is fixing this issue. Looks like this PR: [https://github.com/apache/fineract/pull/1917/files] attached here is not the right one fixing this issue. [~AnkiR] any ideas? > Tag /Tag Id is mandatory in Bulk Import for chart of account > > > Key: FINERACT-1399 > URL: https://issues.apache.org/jira/browse/FINERACT-1399 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Manoj Mohanan >Priority: Minor > Fix For: 1.6.0 > > > While doing Bulk import for chart of accounts, the Tag / Tag Id are mandatory > where as these are not mandatory for creating chart of account. > Expected result: Tag/ Tag Id should not be mandatory for bulk import. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1410) Allow Payment types to map to all types of Ledgers
[ https://issues.apache.org/jira/browse/FINERACT-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick resolved FINERACT-1410. -- Resolution: Fixed Thanks [~AnkiR]. [~ptuomola], I am closing this one as fixed. Adjust if that is not the case. > Allow Payment types to map to all types of Ledgers > -- > > Key: FINERACT-1410 > URL: https://issues.apache.org/jira/browse/FINERACT-1410 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting, Savings >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Ankita Ranjan >Priority: Minor > Labels: beginner > Fix For: 1.6.0 > > Attachments: image-2021-10-20-14-20-45-594.png, > image-2021-10-20-14-22-28-191.png > > > For Payment types on savings account products, currently only Asset ledger > type is allowed. > Enhane this feature to allow all ledger account types to be allowed. > This feature should be configurable (ON/OFF) based on a configuration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1414) Fixed deposits are shown in savings account page from Global Search
[ https://issues.apache.org/jira/browse/FINERACT-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1414: - Fix Version/s: 1.6.0 > Fixed deposits are shown in savings account page from Global Search > --- > > Key: FINERACT-1414 > URL: https://issues.apache.org/jira/browse/FINERACT-1414 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Shemin Anto >Priority: Minor > Fix For: 1.6.0 > > > When searched from Global Search for a Fixed deposit, and while navigating > to that account it is shown in savings account details page. > Expected: Fixed deposits should navigate to Fixed deposit details page -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1414) Fixed deposits are shown in savings account page from Global Search
[ https://issues.apache.org/jira/browse/FINERACT-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1414: - Affects Version/s: 1.5.0 > Fixed deposits are shown in savings account page from Global Search > --- > > Key: FINERACT-1414 > URL: https://issues.apache.org/jira/browse/FINERACT-1414 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Shemin Anto >Priority: Minor > > When searched from Global Search for a Fixed deposit, and while navigating > to that account it is shown in savings account details page. > Expected: Fixed deposits should navigate to Fixed deposit details page -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1414) Fixed deposits are shown in savings account page from Global Search
[ https://issues.apache.org/jira/browse/FINERACT-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1414: - Component/s: Savings > Fixed deposits are shown in savings account page from Global Search > --- > > Key: FINERACT-1414 > URL: https://issues.apache.org/jira/browse/FINERACT-1414 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Shemin Anto >Priority: Minor > > When searched from Global Search for a Fixed deposit, and while navigating > to that account it is shown in savings account details page. > Expected: Fixed deposits should navigate to Fixed deposit details page -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1400) Bulkimport to import opening balances for Ledgers
[ https://issues.apache.org/jira/browse/FINERACT-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick resolved FINERACT-1400. -- Resolution: Fixed Good work [~AnkiR] > Bulkimport to import opening balances for Ledgers > -- > > Key: FINERACT-1400 > URL: https://issues.apache.org/jira/browse/FINERACT-1400 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Ankita Ranjan >Priority: Minor > Labels: beginner, tech-debt > Fix For: 1.6.0 > > > There is no Bulk import option to import opening balances for Chart of > accounts. This would make migratiosn easier. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1400) Bulkimport to import opening balances for Ledgers
[ https://issues.apache.org/jira/browse/FINERACT-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1400: - Labels: beginner tech-debt (was: ) > Bulkimport to import opening balances for Ledgers > -- > > Key: FINERACT-1400 > URL: https://issues.apache.org/jira/browse/FINERACT-1400 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Ankita Ranjan >Priority: Minor > Labels: beginner, tech-debt > Fix For: 1.6.0 > > > There is no Bulk import option to import opening balances for Chart of > accounts. This would make migratiosn easier. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1400) Bulkimport to import opening balances for Ledgers
[ https://issues.apache.org/jira/browse/FINERACT-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1400: - Fix Version/s: 1.6.0 > Bulkimport to import opening balances for Ledgers > -- > > Key: FINERACT-1400 > URL: https://issues.apache.org/jira/browse/FINERACT-1400 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Ankita Ranjan >Priority: Minor > Fix For: 1.6.0 > > > There is no Bulk import option to import opening balances for Chart of > accounts. This would make migratiosn easier. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1400) Bulkimport to import opening balances for Ledgers
[ https://issues.apache.org/jira/browse/FINERACT-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433239#comment-17433239 ] Awasum Yannick commented on FINERACT-1400: -- According to PR: [https://github.com/apache/fineract/pull/1890] , [~AnkiR] worked on the issue and submitted the PR. So I changed the assignee to this issue. Hope its Ok. Also when a PR is merged,,Please also resolve or close the issue as fixed. CC [~avikganguly010] and [~fynmanoj]. Thanks for the contributions you all. > Bulkimport to import opening balances for Ledgers > -- > > Key: FINERACT-1400 > URL: https://issues.apache.org/jira/browse/FINERACT-1400 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Ankita Ranjan >Priority: Minor > > There is no Bulk import option to import opening balances for Chart of > accounts. This would make migratiosn easier. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1400) Bulkimport to import opening balances for Ledgers
[ https://issues.apache.org/jira/browse/FINERACT-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick reassigned FINERACT-1400: Assignee: Ankita Ranjan (was: Manoj Mohanan) > Bulkimport to import opening balances for Ledgers > -- > > Key: FINERACT-1400 > URL: https://issues.apache.org/jira/browse/FINERACT-1400 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Ankita Ranjan >Priority: Minor > > There is no Bulk import option to import opening balances for Chart of > accounts. This would make migratiosn easier. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1415) Make sure that using this pseudorandom number generator is safe
[
https://issues.apache.org/jira/browse/FINERACT-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17432912#comment-17432912
]
Awasum Yannick commented on FINERACT-1415:
--
[~victorromero], This looks like it was merged and then reverted? I dont know
if we need to close this or leave it open... let us know...
> Make sure that using this pseudorandom number generator is safe
> ---
>
> Key: FINERACT-1415
> URL: https://issues.apache.org/jira/browse/FINERACT-1415
> Project: Apache Fineract
> Issue Type: Improvement
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0
>Reporter: Victor Romero
>Assignee: Victor Romero
>Priority: Major
> Labels: tech-debt
> Fix For: 1.6.0
>
>
> [https://sonarcloud.io/project/security_hotspots?id=apache_fineract#]
>
> Using pseudorandom number generators (PRNGs) is security-sensitive. For
> example, it has led in the past to the following vulnerabilities:
> * [CVE-2013-6386|http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6386]
> * [CVE-2006-3419|http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3419]
> * [CVE-2008-4102|http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-4102]
> When software generates predictable values in a context requiring
> unpredictability, it may be possible for an attacker to guess the next value
> that will be generated, and use this guess to impersonate another user or
> access sensitive information.
> As the {{java.util.Random}} class relies on a pseudorandom number generator,
> this class and relating {{java.lang.Math.random()}} method should not be used
> for security-critical applications or for protecting sensitive data. In such
> context, the {{java.security.SecureRandom}} class which relies on a
> cryptographically strong random number generator (RNG) should be used in
> place.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (FINERACT-1409) SonarQube Analysis for Automated as part of improvement on QA
[ https://issues.apache.org/jira/browse/FINERACT-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick resolved FINERACT-1409. -- Resolution: Fixed Good work.. Thanks very much [~victorromero] > SonarQube Analysis for Automated as part of improvement on QA > - > > Key: FINERACT-1409 > URL: https://issues.apache.org/jira/browse/FINERACT-1409 > Project: Apache Fineract > Issue Type: Task >Affects Versions: 1.5.0 >Reporter: Victor Romero >Assignee: Victor Romero >Priority: Major > Labels: tech-debt > Fix For: 1.6.0 > > > SonarQube® is an automatic code review tool to detect bugs, vulnerabilities, > and code smells in your code. It can integrate with your existing workflow to > enable continuous code inspection across your project branches and pull > requests. The results will be available at > [https://sonarcloud.io/project/configuration?id=apache_fineract] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1411) Allow charges to map to all types of Ledgers
[ https://issues.apache.org/jira/browse/FINERACT-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1411: - Labels: beginner (was: ) > Allow charges to map to all types of Ledgers > > > Key: FINERACT-1411 > URL: https://issues.apache.org/jira/browse/FINERACT-1411 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan, Savings >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Ankita Ranjan >Priority: Minor > Labels: beginner > > For charges on savings account products, currently only Income legder type is > allowed. > Enhane this feature to allow all ledger account types to be allowed. > This feature should be configurable (ON/OFF) based on a configuration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1411) Allow charges to map to all types of Ledgers
[ https://issues.apache.org/jira/browse/FINERACT-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1411: - Fix Version/s: 1.6.0 > Allow charges to map to all types of Ledgers > > > Key: FINERACT-1411 > URL: https://issues.apache.org/jira/browse/FINERACT-1411 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan, Savings >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Ankita Ranjan >Priority: Minor > Labels: beginner > Fix For: 1.6.0 > > > For charges on savings account products, currently only Income legder type is > allowed. > Enhane this feature to allow all ledger account types to be allowed. > This feature should be configurable (ON/OFF) based on a configuration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1411) Allow charges to map to all types of Ledgers
[ https://issues.apache.org/jira/browse/FINERACT-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1411: - Component/s: Savings Loan > Allow charges to map to all types of Ledgers > > > Key: FINERACT-1411 > URL: https://issues.apache.org/jira/browse/FINERACT-1411 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan, Savings >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Ankita Ranjan >Priority: Minor > > For charges on savings account products, currently only Income legder type is > allowed. > Enhane this feature to allow all ledger account types to be allowed. > This feature should be configurable (ON/OFF) based on a configuration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1411) Allow charges to map to all types of Ledgers
[ https://issues.apache.org/jira/browse/FINERACT-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-1411: - Affects Version/s: 1.5.0 > Allow charges to map to all types of Ledgers > > > Key: FINERACT-1411 > URL: https://issues.apache.org/jira/browse/FINERACT-1411 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.5.0 >Reporter: Manoj Mohanan >Assignee: Ankita Ranjan >Priority: Minor > > For charges on savings account products, currently only Income legder type is > allowed. > Enhane this feature to allow all ledger account types to be allowed. > This feature should be configurable (ON/OFF) based on a configuration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
