[jira] [Resolved] (FINCN-157) Travis CI after_failure to output rat reports
[ https://issues.apache.org/jira/browse/FINCN-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ebenezer Graham resolved FINCN-157. --- Resolution: Fixed > Travis CI after_failure to output rat reports > - > > Key: FINCN-157 > URL: https://issues.apache.org/jira/browse/FINCN-157 > Project: Fineract Cloud Native > Issue Type: Improvement >Reporter: Ebenezer Graham >Assignee: Ebenezer Graham >Priority: Minor > > This is an improvement suggestion to issue > [https://issues.apache.org/jira/browse/FINCN-148] > All error can be viewed from the travis-ci web interface except the rat > report. Hence a procedure should be made for rat checks as well. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-677) Hide Sensitive contents in xml files and logs
[ https://issues.apache.org/jira/browse/FINERACT-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854329#comment-16854329 ] ApacheSF User commented on FINERACT-677: Noted Sir! Thank you. Regards, > Hide Sensitive contents in xml files and logs > - > > Key: FINERACT-677 > URL: https://issues.apache.org/jira/browse/FINERACT-677 > Project: Apache Fineract > Issue Type: Bug > Environment: All environments, Linux/Unix and Windows. >Reporter: ApacheSF User >Priority: Major > Labels: 2019-mifos-gsoc, p1 > Fix For: 1.4.0 > > > This is an issue explaining about hiding sensitive issues in xml files. > These files include. > Usernames & passwords in: > tomcat/conf/server.xml > Mifos system username and password are visible in : > tomcat/logs/localhost_access_log.2018-12-07 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-391) Fund Management-Delete Enhancement
[ https://issues.apache.org/jira/browse/FINERACT-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854254#comment-16854254 ] Mexina Daniel commented on FINERACT-391: [~edcable] We have not yet implemented the feature, the features was not requested by our clients but our QA Agness Meena saw the need of having the ability to delete a fund once it is created (If it is not linkend to any active loan product ) to remove un-needed funds which does not used anymore. > Fund Management-Delete Enhancement > -- > > Key: FINERACT-391 > URL: https://issues.apache.org/jira/browse/FINERACT-391 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p3 > Fix For: 1.5.0 > > > Reported by Agness Meena at https://mifosforge.jira.com/browse/MIFOSX-2822 > Go to Admin > Organization > Manage Fund > Once you create a new fund you can only edit it but not deleting it. > Need a Delete button to delete existing fund. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-690) Global configuration to disallow the change of overdue charges on a loan product to affect the already created loans.
[ https://issues.apache.org/jira/browse/FINERACT-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854251#comment-16854251 ] Mexina Daniel commented on FINERACT-690: [~edcable] The requirement is, for some of the MFI when a client take a loan with the agreement of no penalty, when the MFI come to introduce the penalty before they have completed their loans, the changes of loan product should not affect the already applied loans. My suggestion on implementation was to have a global configuration that will allow a MFI to either allow the already applied loans to be affected with the changes or to disallow that. > Global configuration to disallow the change of overdue charges on a loan > product to affect the already created loans. > - > > Key: FINERACT-690 > URL: https://issues.apache.org/jira/browse/FINERACT-690 > Project: Apache Fineract > Issue Type: New Feature > Components: Charges, Loan >Reporter: Mexina Daniel >Priority: Major > Labels: 2019-mifos-gsoc, GSoC > Fix For: 1.5.0 > > > For now when you attach an overdue charge to a loan product which did not > have previously, it affect the active loans that were created without a > penalty. > Am suggesting for the system to have a configuration to allow are disallow > this feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
