[jira] [Updated] (FINERACT-670) Transaction 'Notes' should be displayed in summary of transaction
[ https://issues.apache.org/jira/browse/FINERACT-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-670: -- Labels: gci gsoc p1 (was: GCI gsoc p1) > Transaction 'Notes' should be displayed in summary of transaction > - > > Key: FINERACT-670 > URL: https://issues.apache.org/jira/browse/FINERACT-670 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.2.0 >Reporter: Santosh Math >Assignee: Santosh Math >Priority: Major > Labels: gci, gsoc, p1 > Fix For: 1.3.0 > > > Whenever we make Transactions like Loan Repayments, we can capture Notes. But > currently, after transaction is done ,these notes can be seen in Loan > Account tab rather than in Transaction Details. This makes it difficult to > determine which transaction the note applied to. > Expected: Notes should be shown in Transaction details page. Likewise, this > notes field should be part of the fields that would get displayed in a > transaction details report. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (FINERACT-26) Allow a Logo (for Organization) to be set, which will be displayed on the header
[ https://issues.apache.org/jira/browse/FINERACT-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713133#comment-16713133 ] Abhay Chawla edited comment on FINERACT-26 at 12/7/18 5:54 PM: --- Reference: https://issues.apache.org/jira/browse/FINERACT-638 1) Support for saving and retrieving the Name of the Organisation, Description, Summary, Default Language, Default Date Format 2) Support for saving and retrieving images including Favicon, Cover Image, Organisation Logo, Organisation Logo with Name 3) Support for saving and retrieving Default theme and font to be used within the application 4) Support for saving and retrieving contact information including website, email, contact no (multiple if required) App configuration for the new web app will be based on the Tenant, the following things can be saved or modified by the permitted administrators within the organization only from the available user interface once they are logged in (when authenticated), however, everything will be retrievable without the need of authentication from the login page itself based on the Tenant so that it can be shown there as well. If need and as mentioned here, we can specify the dimensions of the specific logo/images as well to ensure it looks the best when used. was (Author: abhaychawla): Reference: https://issues.apache.org/jira/browse/FINERACT-638?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=16712351#comment-16712351 1) Support for saving and retrieving the Name of the Organisation, Description, Summary, Default Language, Default Date Format 2) Support for saving and retrieving images including Favicon, Cover Image, Organisation Logo, Organisation Logo with Name 3) Support for saving and retrieving Default theme and font to be used within the application 4) Support for saving and retrieving contact information including website, email, contact no (multiple if required) App configuration for the new web app will be based on the Tenant, the following things can be saved or modified by the permitted administrators within the organization only from the available user interface once they are logged in (when authenticated), however, everything will be retrievable without the need of authentication from the login page itself based on the Tenant so that it can be shown there as well. If need and as mentioned here, we can specify the dimensions of the specific logo/images as well to ensure it looks the best when used. > Allow a Logo (for Organization) to be set, which will be displayed on the > header > > > Key: FINERACT-26 > URL: https://issues.apache.org/jira/browse/FINERACT-26 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p1 > Fix For: 1.3.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2511 > As a Implementation Specialist, I wish to setup a logo (for the organization) > which will be displayed before the Mifos logo > As a first step : there is no user interface needed for uploading the logo. > As a second step : we can provide user interface for logo-upload > Logo can be different for different tenants (in a multi-tenant setup). > Logo should be same size as Mifos X logo - to maintain aesthetics of the > header band. > Part 2 ] While we are at it, we should probably also allow themes to be > picked on on a per tenant basis -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (FINERACT-26) Allow a Logo (for Organization) to be set, which will be displayed on the header
[ https://issues.apache.org/jira/browse/FINERACT-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713133#comment-16713133 ] Abhay Chawla edited comment on FINERACT-26 at 12/7/18 5:55 PM: --- Reference: https://issues.apache.org/jira/browse/FINERACT-638 1) Support for saving and retrieving the Name of the Organisation, Description, Summary, Default Language, Default Date Format 2) Support for saving and retrieving images including Favicon, Cover Image, Organisation Logo, Organisation Logo with Name 3) Support for saving and retrieving Default theme and font to be used within the application 4) Support for saving and retrieving contact information including website, email, contact no (multiple if required) App configuration for the new web app will be based on the Tenant, the following things can be saved or modified by the permitted administrators within the organization only from the available user interface once they are logged in (when authenticated), however, everything will be retrievable without the need of authentication from the login page itself based on the Tenant so that it can be shown there as well. By default information related to Mifos will be visible. If needed as mentioned here, we can specify the dimensions of the specific logo/images as well to ensure it looks the best when used. was (Author: abhaychawla): Reference: https://issues.apache.org/jira/browse/FINERACT-638 1) Support for saving and retrieving the Name of the Organisation, Description, Summary, Default Language, Default Date Format 2) Support for saving and retrieving images including Favicon, Cover Image, Organisation Logo, Organisation Logo with Name 3) Support for saving and retrieving Default theme and font to be used within the application 4) Support for saving and retrieving contact information including website, email, contact no (multiple if required) App configuration for the new web app will be based on the Tenant, the following things can be saved or modified by the permitted administrators within the organization only from the available user interface once they are logged in (when authenticated), however, everything will be retrievable without the need of authentication from the login page itself based on the Tenant so that it can be shown there as well. If need and as mentioned here, we can specify the dimensions of the specific logo/images as well to ensure it looks the best when used. > Allow a Logo (for Organization) to be set, which will be displayed on the > header > > > Key: FINERACT-26 > URL: https://issues.apache.org/jira/browse/FINERACT-26 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p1 > Fix For: 1.3.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2511 > As a Implementation Specialist, I wish to setup a logo (for the organization) > which will be displayed before the Mifos logo > As a first step : there is no user interface needed for uploading the logo. > As a second step : we can provide user interface for logo-upload > Logo can be different for different tenants (in a multi-tenant setup). > Logo should be same size as Mifos X logo - to maintain aesthetics of the > header band. > Part 2 ] While we are at it, we should probably also allow themes to be > picked on on a per tenant basis -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-670) Transaction 'Notes' should be displayed in summary of transaction
[ https://issues.apache.org/jira/browse/FINERACT-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-670: -- Fix Version/s: (was: 1.4.0) 1.3.0 > Transaction 'Notes' should be displayed in summary of transaction > - > > Key: FINERACT-670 > URL: https://issues.apache.org/jira/browse/FINERACT-670 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.2.0 >Reporter: Santosh Math >Assignee: Santosh Math >Priority: Major > Labels: GCI, gsoc, p1 > Fix For: 1.3.0 > > > Whenever we make Transactions like Loan Repayments, we can capture Notes. But > currently, after transaction is done ,these notes can be seen in Loan > Account tab rather than in Transaction Details. This makes it difficult to > determine which transaction the note applied to. > Expected: Notes should be shown in Transaction details page. Likewise, this > notes field should be part of the fields that would get displayed in a > transaction details report. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-518) Share Transaction doesn't capture user ID
[ https://issues.apache.org/jira/browse/FINERACT-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-518: -- Labels: Volunteer gci p1 (was: gci p1) > Share Transaction doesn't capture user ID > - > > Key: FINERACT-518 > URL: https://issues.apache.org/jira/browse/FINERACT-518 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Critical > Labels: Volunteer, gci, p1 > Fix For: 1.3.0 > > > In m_share_account_transactions table there is no column for appuser_id for > capturing the user id of whose so ever has done a transaction, be it Share > purchase, Share Redeem hence auditing share transactions is hard -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-597) mifos -- splitting savings into member and donor(sponsor) for a single saving stream
[ https://issues.apache.org/jira/browse/FINERACT-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R reassigned FINERACT-597: - Assignee: Shruthi M R (was: Markus Geiss) > mifos -- splitting savings into member and donor(sponsor) for a single saving > stream > > > Key: FINERACT-597 > URL: https://issues.apache.org/jira/browse/FINERACT-597 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.0.0 > Environment: software(cloud) >Reporter: Simon Peter Mulima >Assignee: Shruthi M R >Priority: Major > Labels: gsoc, p2 > Fix For: 1.4.0 > > > Hello it would be good to split accounts(saving stream) within an > individual's saving account such that u can separate saving money streams > from for example ( if parents were contributing for their child) a father , > mother and the child *OR* if an individual is receiving topup contributions > from an association which are dependent on themselves making a saving( the > association will give you a saving only if u also contribute and it is > necessary to show what each party has contributed) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-348) Issues when doing a "Close-As-Rescheduled" on a loan
[ https://issues.apache.org/jira/browse/FINERACT-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-348: -- Labels: gsoc p2 (was: gsoc p1) > Issues when doing a "Close-As-Rescheduled" on a loan > - > > Key: FINERACT-348 > URL: https://issues.apache.org/jira/browse/FINERACT-348 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Critical > Labels: gsoc, p2 > Fix For: 1.4.0 > > > Reported by Binny at https://mifosforge.jira.com/browse/MIFOSX-1205 > Original Description: > When closing a loan using the "Close (as Rescheduled)" button, the loan > account is closed, but there are no transactions or accounting entries made > for this closure. This not correct. > The following should be done: > 1) A new transaction should be visible to user under transactions to show > that the loan was closed as rescheduled rather than leaving the loan as is > without any changes. This means that Mifos X should mkae a new entry > m_loan_transaction table - with transaction_type_enum = 7 and amount as the > total outstanding amount (principal + interest + fees). > 2) Ensure that the right accounting entries are made when closing the loan as > "closed (as rescheduled)". This involves: > For loan products: capturing another General Ledger account head under > “Rescheduled in Suspense” – for example: “Rescheduled Loans Suspense Account” > When closing as loan as rescheduled, passing the following entries: > a) For Cash Accounting: > Debit: Rescheduled Loan Suspense Account (with only principal outstanding > amount) > Credit: Loan portfolio > b) For Accrual (upfront): > Debit: Rescheduled Loan Suspense Account (sum of outstanding principal + > interest + fees + penalties) > Credit: Loan portfolio (with principal outstanding amount) > Credit: Interest Receivable (with interest outstanding amount) > Credit: Fees Receivable (with fees outstanding amount) > Credit: Penalties Receivable (with penalties outstanding amount) > c) For Accrual (periodic): > Debit: Rescheduled Loan Suspense Account (sum of outstanding principal + > interest receivable accounted + fees receivable accounted + penalties > receivable accounted) > Credit: Loan portfolio (with principal outstanding amount) > Credit: Interest Receivable (with interest receivable accounted) > Credit: Fees Receivable (with fees receivable accounted) > Credit: Penalties Receivable (with penalties receivable accounted) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-670) Transaction 'Notes' should be displayed in summary of transaction
[ https://issues.apache.org/jira/browse/FINERACT-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-670: -- Fix Version/s: (was: 1.3.0) 1.4.0 > Transaction 'Notes' should be displayed in summary of transaction > - > > Key: FINERACT-670 > URL: https://issues.apache.org/jira/browse/FINERACT-670 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.2.0 >Reporter: Santosh Math >Assignee: Santosh Math >Priority: Major > Labels: GCI, gsoc, p1 > Fix For: 1.3.0 > > > Whenever we make Transactions like Loan Repayments, we can capture Notes. But > currently, after transaction is done ,these notes can be seen in Loan > Account tab rather than in Transaction Details. This makes it difficult to > determine which transaction the note applied to. > Expected: Notes should be shown in Transaction details page. Likewise, this > notes field should be part of the fields that would get displayed in a > transaction details report. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-528) After taking survey for a client, Survey is displaying score of each question in stead of total score of each survey
[ https://issues.apache.org/jira/browse/FINERACT-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-528: -- Labels: Volunteer gsoc p1 (was: gsoc p1) > After taking survey for a client, Survey is displaying score of each question > in stead of total score of each survey > > > Key: FINERACT-528 > URL: https://issues.apache.org/jira/browse/FINERACT-528 > Project: Apache Fineract > Issue Type: Improvement > Components: Client, Surveys >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: Volunteer, gsoc, p1 > Fix For: 1.4.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-616) Apply Penalty for loans scheduler job not running automatically; only running by manually.
[ https://issues.apache.org/jira/browse/FINERACT-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R updated FINERACT-616: -- Remaining Estimate: 12h Original Estimate: 12h > Apply Penalty for loans scheduler job not running automatically; only > running by manually. > -- > > Key: FINERACT-616 > URL: https://issues.apache.org/jira/browse/FINERACT-616 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: gsoc, p1 > Fix For: 1.3.0 > > Original Estimate: 12h > Remaining Estimate: 12h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-641) Withdrawal fee support for overdrawing account
[ https://issues.apache.org/jira/browse/FINERACT-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R updated FINERACT-641: -- Remaining Estimate: 72h Original Estimate: 72h > Withdrawal fee support for overdrawing account > --- > > Key: FINERACT-641 > URL: https://issues.apache.org/jira/browse/FINERACT-641 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Major > Labels: Volunteer, gsoc, p1 > Fix For: 1.3.0 > > Original Estimate: 72h > Remaining Estimate: 72h > > Currently, Savings Withdrawal fee only applicable if withdrawal is done when > balance is greater than zero. > If try to overdraw from savings account, withdrawal fee won't support and > it's throwing the error. > Expected: Withdrawal fee should support overdrawn account . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-643) Journal Entries are not filterable by type of entry: system
[ https://issues.apache.org/jira/browse/FINERACT-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-643: -- Fix Version/s: (was: 1.3.0) 1.4.0 > Journal Entries are not filterable by type of entry: system > --- > > Key: FINERACT-643 > URL: https://issues.apache.org/jira/browse/FINERACT-643 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Major > Labels: Volunteer, gci, gsoc, p1 > Fix For: 1.4.0 > > > Related Front -End Issue: > https://github.com/openMF/web-app/issues/236 > As a developer, I am unable to implement the filter for Journal Entries by > type of entry: system, as the only parameter available to filter entries by > type is manualEntriesOnly which filters manual entries (as clear from its > name). There is no way to filter system entries from server-side. > (similar issue in community-app) > Due to a large number of entries in database (over 8), its essential to > implement it from server-side because the default implementation of sending a > HTTP request to get all the entries at once and implementing the logic on > client-side will be too costly for people with slow internet connections. > > Refer: [https://demo.openmf.org/api-docs/apiLive.htm#journalentries_list] > Expected Behaviour: > Journal Entries should be filterable by type of entry: system apart from the > manual as well from the server-side so that it can be implemented on the > client side. > h2. Actual Behaviour > Journal Entries are not filterable by type of entry: system from the > server-side due to which filter by type of entry cannot be implemented > properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-652) Deliver status is not getting updated to 'Delivered' (status:300) even message is delivered to the mobile
[ https://issues.apache.org/jira/browse/FINERACT-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-652: -- Labels: Volunteer p1 (was: p1) > Deliver status is not getting updated to 'Delivered' (status:300) even > message is delivered to the mobile > -- > > Key: FINERACT-652 > URL: https://issues.apache.org/jira/browse/FINERACT-652 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: Volunteer, p1 > Fix For: 1.3.0 > > > The following are the sms status: > Pending: 100 > Waiting for Delivery Report: 150 > Sent sms: 200 > Delivered sms: 300 > Failed sms: 400 > Even sms is delivered to given mobile number the status in the database is > not getting updating from 150 to 300. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-536) Report categories are inconsistent and causing reports to go missing in the drop-down
[ https://issues.apache.org/jira/browse/FINERACT-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712823#comment-16712823 ] Mexina Daniel commented on FINERACT-536: [~Shruthi M R] when i said "source codes to change the category of the report" i thought the category of the report was coded on the platform source codes and so was asking for the file to edit since they can't be edited in the community-app. > Report categories are inconsistent and causing reports to go missing in the > drop-down > - > > Key: FINERACT-536 > URL: https://issues.apache.org/jira/browse/FINERACT-536 > Project: Apache Fineract > Issue Type: Improvement > Components: System >Affects Versions: 1.0.0 >Reporter: thynn win >Assignee: Shruthi M R >Priority: Minor > Labels: gci, gsoc, p1 > Fix For: 1.3.0 > > Attachments: Untitled.gif > > > Currently in Mifos, if you go to Reports menu and use the drop down to see > "Clients" or "Loans", we notice that some reports are not showing up in the > proper list. > For instance, if you pick Reports>Clients , some client reports such as > "Client Listing" will not show up. This is because the category is 'Clients' > while the expected category value for "Clients" drop down is "Client". > The same issue presents for other category such as Loans. In this case, some > loan reports are created with category "Loan" not "Loans" and then they are > not showing up. It's confusing to end users. > To solve this, review all the report categories and make sure they are > consistent with the expected value from the drop down (be it Client or > Loans). > Acceptance criteria: > All the report categories are cleaned up and consistent and they should all > show up under right drop-down. > The end result is a sql script for the next release that fixes it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-616) Apply Penalty for loans scheduler job not running automatically; only running by manually.
[ https://issues.apache.org/jira/browse/FINERACT-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R reassigned FINERACT-616: - Assignee: Shruthi M R > Apply Penalty for loans scheduler job not running automatically; only > running by manually. > -- > > Key: FINERACT-616 > URL: https://issues.apache.org/jira/browse/FINERACT-616 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: gsoc, p1 > Fix For: 1.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-336) Fund Mapping page Points to Advanced Search page
[ https://issues.apache.org/jira/browse/FINERACT-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R reassigned FINERACT-336: - Assignee: Shruthi M R (was: Edward Cable) > Fund Mapping page Points to Advanced Search page > > > Key: FINERACT-336 > URL: https://issues.apache.org/jira/browse/FINERACT-336 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: gsoc, p1 > Fix For: 1.3.0 > > Attachments: fundmapping.png > > > Reported by Ed Cable at https://mifosforge.jira.com/browse/MIFOSX-2795 > Original Description: > Hi all, > I think this bug has been existent for several months now as we actually > documented it as intended functionality at > https://mifosforge.jira.com/wiki/display/docs/Fund+Mapping > If you got to Admin >> Organization >> Fund Mapping, clicking the link takes > you to > https://demo4.openmf.org/#/advsearch > rather than the intended page on fund mapping (i'm not sure which it is). > On a similar note, I don't think this advance search link is accessible from > the search menu although it should be there or in the quick links. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-276) Job scheduler timezones not handled correctly
[ https://issues.apache.org/jira/browse/FINERACT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-276: -- Fix Version/s: (was: 1.3.0) 1.4.0 > Job scheduler timezones not handled correctly > - > > Key: FINERACT-276 > URL: https://issues.apache.org/jira/browse/FINERACT-276 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Major > Labels: p1 > Fix For: 1.4.0 > > > Reported by Sander at https://mifosforge.jira.com/browse/MIFOSX-1269 > Original Description: > When investigating some issues with the overdue loan portfolio we found out > that the current way the jobs are handled can cause differences in the > figures for tenants by not picking up the correct date. > The server has the timezone set to UTC/GMT. When a cronjob is added with a > cron entry to run at 0:01 every day, the java scheduler converts this into > the timezone of the tenant (UTC+3 in this example). In this case this results > in the actual schedule to be kicked off at 21:01 the day before. > When the job then triggers it on 21:01 on 01-06-2014 it uses the mysql > CURDATE() feature to decide on the current date, but this returns in UTC, > therefore reporting everything against 01-06-2014, instead of 02-06-2014 > which was the expected (based on timezone UTC+3). > In this case the arrears are updated incorrectly, but same applies to > prepayments and all other jobs that happen in the gap between UTC and the > tenant timezone. > Workaround: Update the cronjob entry to run at 03:01 (UTC+3) by default, this > then gets converted into 0:01 (UTC) and therefore it uses 02-06-2014 as the > date. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-276) Job scheduler timezones not handled correctly
[ https://issues.apache.org/jira/browse/FINERACT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R reassigned FINERACT-276: - Assignee: Shruthi M R (was: Markus Geiss) > Job scheduler timezones not handled correctly > - > > Key: FINERACT-276 > URL: https://issues.apache.org/jira/browse/FINERACT-276 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > > Reported by Sander at https://mifosforge.jira.com/browse/MIFOSX-1269 > Original Description: > When investigating some issues with the overdue loan portfolio we found out > that the current way the jobs are handled can cause differences in the > figures for tenants by not picking up the correct date. > The server has the timezone set to UTC/GMT. When a cronjob is added with a > cron entry to run at 0:01 every day, the java scheduler converts this into > the timezone of the tenant (UTC+3 in this example). In this case this results > in the actual schedule to be kicked off at 21:01 the day before. > When the job then triggers it on 21:01 on 01-06-2014 it uses the mysql > CURDATE() feature to decide on the current date, but this returns in UTC, > therefore reporting everything against 01-06-2014, instead of 02-06-2014 > which was the expected (based on timezone UTC+3). > In this case the arrears are updated incorrectly, but same applies to > prepayments and all other jobs that happen in the gap between UTC and the > tenant timezone. > Workaround: Update the cronjob entry to run at 03:01 (UTC+3) by default, this > then gets converted into 0:01 (UTC) and therefore it uses 02-06-2014 as the > date. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-532) Issue in Address section of Client creation page
[ https://issues.apache.org/jira/browse/FINERACT-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712765#comment-16712765 ] Santosh Math commented on FINERACT-532: --- [~Shruthi M R] , let me reproduce this issue . > Issue in Address section of Client creation page > > > Key: FINERACT-532 > URL: https://issues.apache.org/jira/browse/FINERACT-532 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.0.0 >Reporter: Chanda Aparna >Assignee: Markus Geiss >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > Attachments: Address Issue.png > > > Multiple addresses are created during client creation. Please try to get > validation error during client creation. It will create multiple addresses. > Client (Test Client 12334 Client #: 03272) created in Demo site has 4 > times Address created. > This issue is from the current version of demo site (Version > 17.07.01.RELEASE). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-229) As admin of the system, I should be able to reset password for other users
[ https://issues.apache.org/jira/browse/FINERACT-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712728#comment-16712728 ] Santosh Math commented on FINERACT-229: --- [~Ippez] , Just tested on staging and found that superuser can reset the password. Are you expecting some other requirement? > As admin of the system, I should be able to reset password for other users > -- > > Key: FINERACT-229 > URL: https://issues.apache.org/jira/browse/FINERACT-229 > Project: Apache Fineract > Issue Type: Improvement > Components: User Management >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p1 > Fix For: Backlog > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-600) Advanced Accounting Rule
[ https://issues.apache.org/jira/browse/FINERACT-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-600: -- Fix Version/s: (was: 1.3.0) > Advanced Accounting Rule > > > Key: FINERACT-600 > URL: https://issues.apache.org/jira/browse/FINERACT-600 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Loan >Affects Versions: 1.1.0 >Reporter: Nang Hkam >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p2 > Attachments: image-2018-02-06-16-52-56-083.png > > > There is an issue in Advanced Accounting Rule. > In the loan product setting, two charges (e.g., Servie charge and Loan Fees) > are applied. One of the charges is linked to Accounts Payable (by using > Advanced Accounting Rule). > When we run Balance Sheet/Trial Balance, the amount doesn't show up in the > respective COA (Accounts Payable). But, the expected amount is showing in > other COA (which is Fee Income in my example). > !image-2018-02-06-16-52-56-083.png! > > This is loan product setting : > [https://demo.openmf.org/#/viewloanproduct/673] > > Below is Loan Fees : > [https://demo.openmf.org/#/viewcharge/266] > > Below is Service Charge : > [https://demo.openmf.org/#/viewcharge/265] > [|https://demo.openmf.org/#/viewcharge/266] > [|https://demo.openmf.org/#/viewloanproduct/673] > Below is disbursed loan account: > [https://demo.openmf.org/#/viewloanaccount/2237] > > Below is Trial Balance report > !w9GXoyr9HS7AgBJRU5ErkJggg==|id=img301725! > [|https://demo.openmf.org/#/viewloanaccount/2237] > According to the product setting, Fee Income should be only 2000 credited. > Another 2000 should be credited to Accounts Payable. > > [|https://demo.openmf.org/#/viewloanproduct/673] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-647) Allow rescheduling of loan with recalculation of interest enabled
[ https://issues.apache.org/jira/browse/FINERACT-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712742#comment-16712742 ] Shruthi M R commented on FINERACT-647: --- [~edcable] 60 Hrs of dev + internal testing 20 Hrs testing. > Allow rescheduling of loan with recalculation of interest enabled > - > > Key: FINERACT-647 > URL: https://issues.apache.org/jira/browse/FINERACT-647 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.1.0 >Reporter: Mexina Daniel >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > > There is a need of allowing the loan which has enabled interest recalculation > to be rescheduled once needed. > for now the system does not allow that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-534) Want to Group Wise and Center Wise Accounting
[ https://issues.apache.org/jira/browse/FINERACT-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-534. - Resolution: Invalid > Want to Group Wise and Center Wise Accounting > -- > > Key: FINERACT-534 > URL: https://issues.apache.org/jira/browse/FINERACT-534 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.0.0 >Reporter: Rakesh Tomar >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-534) Want to Group Wise and Center Wise Accounting
[ https://issues.apache.org/jira/browse/FINERACT-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-534: -- Fix Version/s: (was: 1.4.0) > Want to Group Wise and Center Wise Accounting > -- > > Key: FINERACT-534 > URL: https://issues.apache.org/jira/browse/FINERACT-534 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.0.0 >Reporter: Rakesh Tomar >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-534) Want to Group Wise and Center Wise Accounting
[ https://issues.apache.org/jira/browse/FINERACT-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712735#comment-16712735 ] Santosh Math commented on FINERACT-534: --- [~raakeshtomar] , As this is related to development of report , closed here and moved to https://github.com/openMF/community-app/issues/3057 > Want to Group Wise and Center Wise Accounting > -- > > Key: FINERACT-534 > URL: https://issues.apache.org/jira/browse/FINERACT-534 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.0.0 >Reporter: Rakesh Tomar >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-505) Loan Tranche Details should be captured in Bulk JLG loan application.
[ https://issues.apache.org/jira/browse/FINERACT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712709#comment-16712709 ] Shruthi M R commented on FINERACT-505: --- [~edcable] 3-4 days > Loan Tranche Details should be captured in Bulk JLG loan application. > - > > Key: FINERACT-505 > URL: https://issues.apache.org/jira/browse/FINERACT-505 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > Fix For: Backlog > > > Presently, there is no fields to capture multi-tranche details in 'Bulk JLG > loan application' . Therefore, Bulk JLG loan application doesn't support > multi-tranche loan products. The current temperory fix is, the loan products > with multi-tranche aren't displaying in drop-down menu of 'Bulk JLG loan > application'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-336) Fund Mapping page Points to Advanced Search page
[ https://issues.apache.org/jira/browse/FINERACT-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712718#comment-16712718 ] Shruthi M R commented on FINERACT-336: --- [~edcable] sure will update the shortcuts > Fund Mapping page Points to Advanced Search page > > > Key: FINERACT-336 > URL: https://issues.apache.org/jira/browse/FINERACT-336 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Reporter: Santosh Math >Assignee: Edward Cable >Priority: Critical > Labels: gsoc, p1 > Fix For: 1.3.0 > > Attachments: fundmapping.png > > > Reported by Ed Cable at https://mifosforge.jira.com/browse/MIFOSX-2795 > Original Description: > Hi all, > I think this bug has been existent for several months now as we actually > documented it as intended functionality at > https://mifosforge.jira.com/wiki/display/docs/Fund+Mapping > If you got to Admin >> Organization >> Fund Mapping, clicking the link takes > you to > https://demo4.openmf.org/#/advsearch > rather than the intended page on fund mapping (i'm not sure which it is). > On a similar note, I don't think this advance search link is accessible from > the search menu although it should be there or in the quick links. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-478) Savings overdraft fee with charge time type 'overdraft fee' and charge calculation '%amount' is not working
[ https://issues.apache.org/jira/browse/FINERACT-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712705#comment-16712705 ] Shruthi M R commented on FINERACT-478: --- [~santoshmath] as discussed kindly share the exact scenario > Savings overdraft fee with charge time type 'overdraft fee' and charge > calculation '%amount' is not working > --- > > Key: FINERACT-478 > URL: https://issues.apache.org/jira/browse/FINERACT-478 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Savings >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: gsoc, p1 > Fix For: 1.3.0 > > > 1. Go to charges and select charge applied to 'Savings and deposits' > 2. Fill other required inputs with > Charge Time type: overdraft fee > Charge calculation : % amount. > Amount : 1 > > After submission , it is throwing error: > > "validation.msg.charges.charge.calculation.type.percentage.allowed.only.for.withdrawal.or.noactivity" > Expected: > 1.This feature of overdraft fee with charge calculation as % amount need to > be implemented. > 2. Until the feature is implemented, the following proper error message > should be thrown in stead of above mentioned: > ""validation.msg: > charge.calculation.type.percentage.allowed.only.for.withdrawal.or.noactivityand > yet to be implemented for overdraft fee" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-505) Loan Tranche Details should be captured in Bulk JLG loan application.
[ https://issues.apache.org/jira/browse/FINERACT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712702#comment-16712702 ] Shruthi M R commented on FINERACT-505: --- [~edcable] it has front-end change as well. So it requires 3-4 working days. > Loan Tranche Details should be captured in Bulk JLG loan application. > - > > Key: FINERACT-505 > URL: https://issues.apache.org/jira/browse/FINERACT-505 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > Fix For: Backlog > > > Presently, there is no fields to capture multi-tranche details in 'Bulk JLG > loan application' . Therefore, Bulk JLG loan application doesn't support > multi-tranche loan products. The current temperory fix is, the loan products > with multi-tranche aren't displaying in drop-down menu of 'Bulk JLG loan > application'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-536) Report categories are inconsistent and causing reports to go missing in the drop-down
[ https://issues.apache.org/jira/browse/FINERACT-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712682#comment-16712682 ] Shruthi M R commented on FINERACT-536: --- [~mexina] can you elaborate on the 'source codes to change the category of the report'. And for the Pentaho are you saying the design of the Pentaho which is created using Pentaho designer? If yes, then yes if you want to make changes to the existing Pentaho report, it needs to deployed on the server and then user can user it. And I will give the migration script for the existing records. > Report categories are inconsistent and causing reports to go missing in the > drop-down > - > > Key: FINERACT-536 > URL: https://issues.apache.org/jira/browse/FINERACT-536 > Project: Apache Fineract > Issue Type: Improvement > Components: System >Affects Versions: 1.0.0 >Reporter: thynn win >Assignee: Shruthi M R >Priority: Minor > Labels: gci, gsoc, p1 > Fix For: 1.3.0 > > Attachments: Untitled.gif > > > Currently in Mifos, if you go to Reports menu and use the drop down to see > "Clients" or "Loans", we notice that some reports are not showing up in the > proper list. > For instance, if you pick Reports>Clients , some client reports such as > "Client Listing" will not show up. This is because the category is 'Clients' > while the expected category value for "Clients" drop down is "Client". > The same issue presents for other category such as Loans. In this case, some > loan reports are created with category "Loan" not "Loans" and then they are > not showing up. It's confusing to end users. > To solve this, review all the report categories and make sure they are > consistent with the expected value from the drop down (be it Client or > Loans). > Acceptance criteria: > All the report categories are cleaned up and consistent and they should all > show up under right drop-down. > The end result is a sql script for the next release that fixes it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-285) For Savings account Deposits and Withdrawals are not working if the "Start interest calculation date" is defined
[ https://issues.apache.org/jira/browse/FINERACT-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-285. - Resolution: Cannot Reproduce Not able to reproduce in recent version. > For Savings account Deposits and Withdrawals are not working if the "Start > interest calculation date" is defined > - > > Key: FINERACT-285 > URL: https://issues.apache.org/jira/browse/FINERACT-285 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: confirm, p1 > Attachments: scr1.png, scr2.jpeg > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1560 > Original Description: > 1. Create a Savings product and assign it to a client on 01 July 2014 -> > Approve and activate the account on same date. > 2. In Database - m_savings_account table enter date as 10 August 2014 in > start_interest_calculation_date column for the same account. > > After attaching the start interest calculation date application is not > > allowing to do any deposits and withdrawals (before and after start > > interest calculation date) displayed error message as "Savings account > > transaction incorrect start interest calculation date". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-285) For Savings account Deposits and Withdrawals are not working if the "Start interest calculation date" is defined
[ https://issues.apache.org/jira/browse/FINERACT-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-285: -- Fix Version/s: (was: 1.3.0) > For Savings account Deposits and Withdrawals are not working if the "Start > interest calculation date" is defined > - > > Key: FINERACT-285 > URL: https://issues.apache.org/jira/browse/FINERACT-285 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: confirm, p1 > Attachments: scr1.png, scr2.jpeg > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1560 > Original Description: > 1. Create a Savings product and assign it to a client on 01 July 2014 -> > Approve and activate the account on same date. > 2. In Database - m_savings_account table enter date as 10 August 2014 in > start_interest_calculation_date column for the same account. > > After attaching the start interest calculation date application is not > > allowing to do any deposits and withdrawals (before and after start > > interest calculation date) displayed error message as "Savings account > > transaction incorrect start interest calculation date". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-466) For the loans without Interest Recalculation, Prepay Loan is collecting all installment Fees in stead of collecting installment fees until the prepay date
[ https://issues.apache.org/jira/browse/FINERACT-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-466. - Resolution: Invalid > For the loans without Interest Recalculation, Prepay Loan is collecting all > installment Fees in stead of collecting installment fees until the prepay date > -- > > Key: FINERACT-466 > URL: https://issues.apache.org/jira/browse/FINERACT-466 > Project: Apache Fineract > Issue Type: Bug > Components: Charges, Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p1 > > 1. Create a loan product without Interest recalculation,monthly repayment, > Equal Installments, Declining balance and 12 repayments with installment fee > 100((flat, monthly) attached. > 2. Disburse the loan on 01 January 2017. > 3 Prepay the loan on 15 February 2017. > > Expected Result: The installment fee should be collected: 100 > >Actual Result: The installment fee getting collected: 1200(all installment > >fees) > P.S: This issue doesn't exist with loans having interest recalculation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-466) For the loans without Interest Recalculation, Prepay Loan is collecting all installment Fees in stead of collecting installment fees until the prepay date
[ https://issues.apache.org/jira/browse/FINERACT-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712670#comment-16712670 ] Santosh Math commented on FINERACT-466: --- Loans with Interest recalculation must be used with 'Prepay Loan' & Loans without Interest Recalculation should be used with 'Foreclosure Loan'. So, this ticket is invalid and closing it. > For the loans without Interest Recalculation, Prepay Loan is collecting all > installment Fees in stead of collecting installment fees until the prepay date > -- > > Key: FINERACT-466 > URL: https://issues.apache.org/jira/browse/FINERACT-466 > Project: Apache Fineract > Issue Type: Bug > Components: Charges, Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p1 > > 1. Create a loan product without Interest recalculation,monthly repayment, > Equal Installments, Declining balance and 12 repayments with installment fee > 100((flat, monthly) attached. > 2. Disburse the loan on 01 January 2017. > 3 Prepay the loan on 15 February 2017. > > Expected Result: The installment fee should be collected: 100 > >Actual Result: The installment fee getting collected: 1200(all installment > >fees) > P.S: This issue doesn't exist with loans having interest recalculation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-534) Want to Group Wise and Center Wise Accounting
[ https://issues.apache.org/jira/browse/FINERACT-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712669#comment-16712669 ] Rakesh Tomar commented on FINERACT-534: --- Sir Thanks for response i want center wise and group wise balance sheet and trial balance > Want to Group Wise and Center Wise Accounting > -- > > Key: FINERACT-534 > URL: https://issues.apache.org/jira/browse/FINERACT-534 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.0.0 >Reporter: Rakesh Tomar >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > Fix For: 1.4.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-536) Report categories are inconsistent and causing reports to go missing in the drop-down
[ https://issues.apache.org/jira/browse/FINERACT-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R reassigned FINERACT-536: - Assignee: Shruthi M R (was: Markus Geiss) > Report categories are inconsistent and causing reports to go missing in the > drop-down > - > > Key: FINERACT-536 > URL: https://issues.apache.org/jira/browse/FINERACT-536 > Project: Apache Fineract > Issue Type: Improvement > Components: System >Affects Versions: 1.0.0 >Reporter: thynn win >Assignee: Shruthi M R >Priority: Minor > Labels: gci, gsoc, p1 > Fix For: 1.3.0 > > Attachments: Untitled.gif > > > Currently in Mifos, if you go to Reports menu and use the drop down to see > "Clients" or "Loans", we notice that some reports are not showing up in the > proper list. > For instance, if you pick Reports>Clients , some client reports such as > "Client Listing" will not show up. This is because the category is 'Clients' > while the expected category value for "Clients" drop down is "Client". > The same issue presents for other category such as Loans. In this case, some > loan reports are created with category "Loan" not "Loans" and then they are > not showing up. It's confusing to end users. > To solve this, review all the report categories and make sure they are > consistent with the expected value from the drop down (be it Client or > Loans). > Acceptance criteria: > All the report categories are cleaned up and consistent and they should all > show up under right drop-down. > The end result is a sql script for the next release that fixes it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (FINERACT-616) Apply Penalty for loans scheduler job not running automatically; only running by manually.
[ https://issues.apache.org/jira/browse/FINERACT-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712638#comment-16712638 ] Shruthi M R edited comment on FINERACT-616 at 12/7/18 10:44 AM: - [~edcable] maximum of 12 hr is required to analyze and to develop was (Author: shruthi m r): [~edcable] maximum of 16 hr is required to analyze and to develop > Apply Penalty for loans scheduler job not running automatically; only > running by manually. > -- > > Key: FINERACT-616 > URL: https://issues.apache.org/jira/browse/FINERACT-616 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Critical > Labels: gsoc, p1 > Fix For: 1.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-547) Indian Currency Symbol and other currency symbols are wrong
[ https://issues.apache.org/jira/browse/FINERACT-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712645#comment-16712645 ] Santosh Math commented on FINERACT-547: --- [~luckyman000786], Closed this ticket as you mentioned it's database issue. > Indian Currency Symbol and other currency symbols are wrong > --- > > Key: FINERACT-547 > URL: https://issues.apache.org/jira/browse/FINERACT-547 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Reporter: Chirag Gupta >Assignee: Markus Geiss >Priority: Major > Labels: gci, important, p1 > > Currently, Indian Currency Symbol and other currency symbols are wrong and > they should be fixed. Fixing this will improve User Experience. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-547) Indian Currency Symbol and other currency symbols are wrong
[ https://issues.apache.org/jira/browse/FINERACT-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-547. - Resolution: Cannot Reproduce > Indian Currency Symbol and other currency symbols are wrong > --- > > Key: FINERACT-547 > URL: https://issues.apache.org/jira/browse/FINERACT-547 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Reporter: Chirag Gupta >Assignee: Markus Geiss >Priority: Major > Labels: gci, important, p1 > > Currently, Indian Currency Symbol and other currency symbols are wrong and > they should be fixed. Fixing this will improve User Experience. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-547) Indian Currency Symbol and other currency symbols are wrong
[ https://issues.apache.org/jira/browse/FINERACT-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-547: -- Fix Version/s: (was: 1.3.0) > Indian Currency Symbol and other currency symbols are wrong > --- > > Key: FINERACT-547 > URL: https://issues.apache.org/jira/browse/FINERACT-547 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Reporter: Chirag Gupta >Assignee: Markus Geiss >Priority: Major > Labels: gci, important, p1 > > Currently, Indian Currency Symbol and other currency symbols are wrong and > they should be fixed. Fixing this will improve User Experience. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-616) Apply Penalty for loans scheduler job not running automatically; only running by manually.
[ https://issues.apache.org/jira/browse/FINERACT-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712638#comment-16712638 ] Shruthi M R commented on FINERACT-616: --- [~edcable] maximum of 16 hr is required to analyze and to develop > Apply Penalty for loans scheduler job not running automatically; only > running by manually. > -- > > Key: FINERACT-616 > URL: https://issues.apache.org/jira/browse/FINERACT-616 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Critical > Labels: gsoc, p1 > Fix For: 1.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (FINERACT-478) Savings overdraft fee with charge time type 'overdraft fee' and charge calculation '%amount' is not working
[ https://issues.apache.org/jira/browse/FINERACT-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-478: -- Comment: was deleted (was: [~edcable], Are you trying to mention another ticket in stead of 478 in your comment? ) > Savings overdraft fee with charge time type 'overdraft fee' and charge > calculation '%amount' is not working > --- > > Key: FINERACT-478 > URL: https://issues.apache.org/jira/browse/FINERACT-478 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Savings >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: gsoc, p1 > Fix For: 1.3.0 > > > 1. Go to charges and select charge applied to 'Savings and deposits' > 2. Fill other required inputs with > Charge Time type: overdraft fee > Charge calculation : % amount. > Amount : 1 > > After submission , it is throwing error: > > "validation.msg.charges.charge.calculation.type.percentage.allowed.only.for.withdrawal.or.noactivity" > Expected: > 1.This feature of overdraft fee with charge calculation as % amount need to > be implemented. > 2. Until the feature is implemented, the following proper error message > should be thrown in stead of above mentioned: > ""validation.msg: > charge.calculation.type.percentage.allowed.only.for.withdrawal.or.noactivityand > yet to be implemented for overdraft fee" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-276) Job scheduler timezones not handled correctly
[ https://issues.apache.org/jira/browse/FINERACT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712610#comment-16712610 ] Santosh Math commented on FINERACT-276: --- [~Shruthi M R] , Markus Geiss is working on Fineract CN only. > Job scheduler timezones not handled correctly > - > > Key: FINERACT-276 > URL: https://issues.apache.org/jira/browse/FINERACT-276 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > > Reported by Sander at https://mifosforge.jira.com/browse/MIFOSX-1269 > Original Description: > When investigating some issues with the overdue loan portfolio we found out > that the current way the jobs are handled can cause differences in the > figures for tenants by not picking up the correct date. > The server has the timezone set to UTC/GMT. When a cronjob is added with a > cron entry to run at 0:01 every day, the java scheduler converts this into > the timezone of the tenant (UTC+3 in this example). In this case this results > in the actual schedule to be kicked off at 21:01 the day before. > When the job then triggers it on 21:01 on 01-06-2014 it uses the mysql > CURDATE() feature to decide on the current date, but this returns in UTC, > therefore reporting everything against 01-06-2014, instead of 02-06-2014 > which was the expected (based on timezone UTC+3). > In this case the arrears are updated incorrectly, but same applies to > prepayments and all other jobs that happen in the gap between UTC and the > tenant timezone. > Workaround: Update the cronjob entry to run at 03:01 (UTC+3) by default, this > then gets converted into 0:01 (UTC) and therefore it uses 02-06-2014 as the > date. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-284) Collection Sheet as a tool for collecting savings
[ https://issues.apache.org/jira/browse/FINERACT-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-284: -- Fix Version/s: (was: 1.3.0) > Collection Sheet as a tool for collecting savings > - > > Key: FINERACT-284 > URL: https://issues.apache.org/jira/browse/FINERACT-284 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p1 > > Reported by Okeleke Mike at https://mifosforge.jira.com/browse/MIFOSX-1558 > Original Description: > I have long been an advocate of the collection sheet, I love the concept and > the idea but I still wonder why it’s only use as always been on loans > collection. I think with the inclusion of Mandatory Deposit (fixed & > recurrent savings) into the MifosX platform it can also easily collect > savings contribution -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-284) Collection Sheet as a tool for collecting savings
[ https://issues.apache.org/jira/browse/FINERACT-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-284. - Resolution: Invalid > Collection Sheet as a tool for collecting savings > - > > Key: FINERACT-284 > URL: https://issues.apache.org/jira/browse/FINERACT-284 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p1 > > Reported by Okeleke Mike at https://mifosforge.jira.com/browse/MIFOSX-1558 > Original Description: > I have long been an advocate of the collection sheet, I love the concept and > the idea but I still wonder why it’s only use as always been on loans > collection. I think with the inclusion of Mandatory Deposit (fixed & > recurrent savings) into the MifosX platform it can also easily collect > savings contribution -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-528) After taking survey for a client, Survey is displaying score of each question in stead of total score of each survey
[ https://issues.apache.org/jira/browse/FINERACT-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712604#comment-16712604 ] Santosh Math commented on FINERACT-528: --- Ed, It's tested on Staging. > After taking survey for a client, Survey is displaying score of each question > in stead of total score of each survey > > > Key: FINERACT-528 > URL: https://issues.apache.org/jira/browse/FINERACT-528 > Project: Apache Fineract > Issue Type: Improvement > Components: Client, Surveys >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: gsoc, p1 > Fix For: 1.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-281) Periodic accrual on a particular day is not calculating as expected
[ https://issues.apache.org/jira/browse/FINERACT-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-281. - Resolution: Cannot Reproduce > Periodic accrual on a particular day is not calculating as expected > --- > > Key: FINERACT-281 > URL: https://issues.apache.org/jira/browse/FINERACT-281 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, confirm, p1 > Attachments: Scr-339.png, Scr-340.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1487 > Original Description: > If Loan disbursed on 05 june 2014, first repayment falls on 19 june 2014 and > If periodic accrual on a particular day ie on 30 june 2014 is run then > accrued interest between 19 june 2014 to 30 june 2014 should be calculated > and displayed instead it is displaying accrued interest from 05 june 2014 to > 30 june 2014. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-281) Periodic accrual on a particular day is not calculating as expected
[ https://issues.apache.org/jira/browse/FINERACT-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-281: -- Fix Version/s: (was: 1.3.0) > Periodic accrual on a particular day is not calculating as expected > --- > > Key: FINERACT-281 > URL: https://issues.apache.org/jira/browse/FINERACT-281 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, confirm, p1 > Attachments: Scr-339.png, Scr-340.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1487 > Original Description: > If Loan disbursed on 05 june 2014, first repayment falls on 19 june 2014 and > If periodic accrual on a particular day ie on 30 june 2014 is run then > accrued interest between 19 june 2014 to 30 june 2014 should be calculated > and displayed instead it is displaying accrued interest from 05 june 2014 to > 30 june 2014. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-665) While editing Center, the new activation date is not getting validated with Submitted date.
[ https://issues.apache.org/jira/browse/FINERACT-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-665. - Tested on staging. Fixed. > While editing Center, the new activation date is not getting validated with > Submitted date. > > > Key: FINERACT-665 > URL: https://issues.apache.org/jira/browse/FINERACT-665 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Major > Labels: gci, gsoc, p1 > Fix For: 1.3.0 > > > 1) Create a center with current submitted and activation date. > 2) Then edit center and provide activation date prior to submitted date. > >Able to change activation date prior to submitted date. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-274) Not able to create the same datatable which was rejected by the maker checker before
[ https://issues.apache.org/jira/browse/FINERACT-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-274: -- Labels: Volunteer confirm p2 (was: Volunteer confirm p1) > Not able to create the same datatable which was rejected by the maker checker > before > > > Key: FINERACT-274 > URL: https://issues.apache.org/jira/browse/FINERACT-274 > Project: Apache Fineract > Issue Type: Bug > Components: Data Tables >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, confirm, p2 > Fix For: 1.3.0 > > > Posted by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1246 > Original Description: > 1. Click on Admin ->System - enable maker-checker. > 2. Click on Admin ->System - Configure maker-checker tasks -> select check > box for create, update and delete data tables. > 3. Click on the Admin -> System -> Manage data tables -> Create data table - > and create data table for client. > 4. The navigated page displays "Waiting For Checker Approval" -> Click on > details -> Click on reject button in "View Checker Inbox" -> click on confirm > in confirmation page. > With the above action in UI the data table will not appear, but in the > database the table is still exist. > > Again try to create datable with the same name as above, which displays > > error message as the data table already exists, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (FINERACT-19) On time loan payment, Overdue Charge should be principal ony
[ https://issues.apache.org/jira/browse/FINERACT-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math reopened FINERACT-19: -- > On time loan payment, Overdue Charge should be principal ony > > > Key: FINERACT-19 > URL: https://issues.apache.org/jira/browse/FINERACT-19 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p1 > > https://mifosforge.jira.com/browse/MIFOSX-2400 - see for attachments > 1. Create a simple loan product with with monthly repayment and overdue > charge as flat 100 attached. > 2. Create a client and submit new loan application for a client on 01 > September 2015 approve and disburse on same date. > 3. Execute scheduler job "Apply penalty for overdue loans". > 4. Now overdue charge got applied for 01 October 2015, 01 November 2015 and > 01 December 2015 repayments. > 5. Make back dated repayment with the amount displayed in repayment schedule > on 01 October 2015. > Expected behavior: > .Since the repayment is done on time the extra amount ie 100 paid should go > to the principal only. > Actual behavior: > The extra amount 100 is getting collected as advance payment for the > immediate next repayment. > Also for the 1st of January the penalty displayed wrongly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-271) Not able to Writeoff the loan if the writeoff date = any repayment date in periodic accrual
[ https://issues.apache.org/jira/browse/FINERACT-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-271: -- Fix Version/s: (was: 1.3.0) > Not able to Writeoff the loan if the writeoff date = any repayment date in > periodic accrual > --- > > Key: FINERACT-271 > URL: https://issues.apache.org/jira/browse/FINERACT-271 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: fineract-gci, p1 > Attachments: 1.png, 2.png > > > As reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1152. > Original Description: > 1. Create a loan product with periodic accrual accounting. > 2. Create a client and attach the above mentioned loan product to that client. > 3. Submit a new loan application on 02 April 2014 approve and disburse on the > same date. > 4. Click on system -> Scheduler job -> Run the job " Add Accrual > Transactions". > 5. In the above mentioned loan account page click on the Transactions - in > which accrual accounting with respect to each repayment is displayed. > 6. Click on "More" tab and click on Writeoff button. > 7. In loan writeoff page enter date as latest repayment date. (As displayed > in Transactions page) and click on submit button. > Expected result: > After the loan disbursement is done on any point of time it should allow to > writeoff the loan after last Transaction happened.(Here no transaction > happened after disbursement) > Actual Result: > Not able to writeoff the Loan since displayed error message as "The date of > the writeoff transaction must occur after the last transaction made against > this loan." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-271) Not able to Writeoff the loan if the writeoff date = any repayment date in periodic accrual
[ https://issues.apache.org/jira/browse/FINERACT-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-271. - > Not able to Writeoff the loan if the writeoff date = any repayment date in > periodic accrual > --- > > Key: FINERACT-271 > URL: https://issues.apache.org/jira/browse/FINERACT-271 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: fineract-gci, p1 > Attachments: 1.png, 2.png > > > As reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1152. > Original Description: > 1. Create a loan product with periodic accrual accounting. > 2. Create a client and attach the above mentioned loan product to that client. > 3. Submit a new loan application on 02 April 2014 approve and disburse on the > same date. > 4. Click on system -> Scheduler job -> Run the job " Add Accrual > Transactions". > 5. In the above mentioned loan account page click on the Transactions - in > which accrual accounting with respect to each repayment is displayed. > 6. Click on "More" tab and click on Writeoff button. > 7. In loan writeoff page enter date as latest repayment date. (As displayed > in Transactions page) and click on submit button. > Expected result: > After the loan disbursement is done on any point of time it should allow to > writeoff the loan after last Transaction happened.(Here no transaction > happened after disbursement) > Actual Result: > Not able to writeoff the Loan since displayed error message as "The date of > the writeoff transaction must occur after the last transaction made against > this loan." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-270) Unable to waive all Loan charges
[ https://issues.apache.org/jira/browse/FINERACT-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-270. - > Unable to waive all Loan charges > > > Key: FINERACT-270 > URL: https://issues.apache.org/jira/browse/FINERACT-270 > Project: Apache Fineract > Issue Type: Bug > Components: Loan > Environment: Reproducible on demo.openmf.org. > Create new client Loan with FINERACT_7-MIFOS_2495 >Reporter: Abdul Aziz Ali >Assignee: Shaik Nazeer Hussain >Priority: Trivial > Labels: p1 > Fix For: 1.0.0 > > Attachments: pruned_catalina.log > > > Create Loan and Charge similar to FINERACT-7 > > (verbatim from FINERACT-7) > 1. Create Installment fee for a loan as 100-Flat-Regular. > 2. Create loan product with following datasets and attache above installment > fee to that. > Terms vary based on loan cycle : FALSE > Principal:10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max > Repay Every: 1 Months > Nominal Interest Rate:1 ( Min: , Max Per month > Minimum days between disbursal and first repayment date > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Repayment StrategyOverdue/Due Fee/Int,Principal > Account moves out of NPA only after all arrears have been cleared?No > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Allow fixing of the installment amountNo > Interest Recalculation > Recalculate Interest Yes > Advance payments adjustment type Reduce number of installments > Pre-closure interest calculation rule Calculate till pre closure date > Interest recalculation compounding on None > Frequency for recalculate Outstanding Principal Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01-Jan-15 > Is Arrears recognization based on original schedule:No. > 3. Submit new loan application on 01 October 2015. Approve and disburse loan > on same date. > 4. Click on waive charge and select for 1st repayment. > 5. Repayment schedule generated after waive charge is not proper > >Waive charge is happening not for first installment instead for other > >installment it is happening. > 6. For first repayment the due is getting displayed. > > 7. Keep waiving all charges until the last one > The last one does not get waived nor does the Exception get raised to the UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-146) In Demo version loans awaiting for approval is not getting displayed properly under Checker in box and tasks
[ https://issues.apache.org/jira/browse/FINERACT-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-146. - Resolution: Cannot Reproduce Not able to reproduce in recent version. > In Demo version loans awaiting for approval is not getting displayed properly > under Checker in box and tasks > > > Key: FINERACT-146 > URL: https://issues.apache.org/jira/browse/FINERACT-146 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Markus Geiss >Priority: Major > Labels: p1 > Attachments: Mifos X Client 2016-04-29 04-17-41.png, Mifos X Client > 2016-04-29 04-19-11.png > > > In demo version after clicking on the checker inbox and tasks, the recently > submitted loan awaiting for approval is not getting displayed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-146) In Demo version loans awaiting for approval is not getting displayed properly under Checker in box and tasks
[ https://issues.apache.org/jira/browse/FINERACT-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-146: -- Fix Version/s: (was: 1.3.0) > In Demo version loans awaiting for approval is not getting displayed properly > under Checker in box and tasks > > > Key: FINERACT-146 > URL: https://issues.apache.org/jira/browse/FINERACT-146 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Markus Geiss >Priority: Major > Labels: p1 > Attachments: Mifos X Client 2016-04-29 04-17-41.png, Mifos X Client > 2016-04-29 04-19-11.png > > > In demo version after clicking on the checker inbox and tasks, the recently > submitted loan awaiting for approval is not getting displayed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-19) On time loan payment, Overdue Charge should be principal ony
[ https://issues.apache.org/jira/browse/FINERACT-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-19: - Fix Version/s: (was: 1.3.0) > On time loan payment, Overdue Charge should be principal ony > > > Key: FINERACT-19 > URL: https://issues.apache.org/jira/browse/FINERACT-19 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p1 > > https://mifosforge.jira.com/browse/MIFOSX-2400 - see for attachments > 1. Create a simple loan product with with monthly repayment and overdue > charge as flat 100 attached. > 2. Create a client and submit new loan application for a client on 01 > September 2015 approve and disburse on same date. > 3. Execute scheduler job "Apply penalty for overdue loans". > 4. Now overdue charge got applied for 01 October 2015, 01 November 2015 and > 01 December 2015 repayments. > 5. Make back dated repayment with the amount displayed in repayment schedule > on 01 October 2015. > Expected behavior: > .Since the repayment is done on time the extra amount ie 100 paid should go > to the principal only. > Actual behavior: > The extra amount 100 is getting collected as advance payment for the > immediate next repayment. > Also for the 1st of January the penalty displayed wrongly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-19) On time loan payment, Overdue Charge should be principal ony
[ https://issues.apache.org/jira/browse/FINERACT-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-19. Resolution: Cannot Reproduce > On time loan payment, Overdue Charge should be principal ony > > > Key: FINERACT-19 > URL: https://issues.apache.org/jira/browse/FINERACT-19 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p1 > > https://mifosforge.jira.com/browse/MIFOSX-2400 - see for attachments > 1. Create a simple loan product with with monthly repayment and overdue > charge as flat 100 attached. > 2. Create a client and submit new loan application for a client on 01 > September 2015 approve and disburse on same date. > 3. Execute scheduler job "Apply penalty for overdue loans". > 4. Now overdue charge got applied for 01 October 2015, 01 November 2015 and > 01 December 2015 repayments. > 5. Make back dated repayment with the amount displayed in repayment schedule > on 01 October 2015. > Expected behavior: > .Since the repayment is done on time the extra amount ie 100 paid should go > to the principal only. > Actual behavior: > The extra amount 100 is getting collected as advance payment for the > immediate next repayment. > Also for the 1st of January the penalty displayed wrongly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-19) On time loan payment, Overdue Charge should be principal ony
[ https://issues.apache.org/jira/browse/FINERACT-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-19. Resolution: Cannot Reproduce Not able to reproduce this issue. > On time loan payment, Overdue Charge should be principal ony > > > Key: FINERACT-19 > URL: https://issues.apache.org/jira/browse/FINERACT-19 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p1 > Fix For: 1.3.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2400 - see for attachments > 1. Create a simple loan product with with monthly repayment and overdue > charge as flat 100 attached. > 2. Create a client and submit new loan application for a client on 01 > September 2015 approve and disburse on same date. > 3. Execute scheduler job "Apply penalty for overdue loans". > 4. Now overdue charge got applied for 01 October 2015, 01 November 2015 and > 01 December 2015 repayments. > 5. Make back dated repayment with the amount displayed in repayment schedule > on 01 October 2015. > Expected behavior: > .Since the repayment is done on time the extra amount ie 100 paid should go > to the principal only. > Actual behavior: > The extra amount 100 is getting collected as advance payment for the > immediate next repayment. > Also for the 1st of January the penalty displayed wrongly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
