[jira] [Created] (FINERACT-606) Not able to delete groups which are assigned to center
Santosh Math created FINERACT-606: - Summary: Not able to delete groups which are assigned to center Key: FINERACT-606 URL: https://issues.apache.org/jira/browse/FINERACT-606 Project: Apache Fineract Issue Type: Bug Reporter: Santosh Math Assignee: Myrle Krantz # Create a new center. # Add existing group to the center using 'Manage groups' option under center. # Again go to 'Manage Groups' and try to remove group from center. >throwing validation: field is required error.msg.group.not.in.center - [https://staging.openmf.org/#/managegroupmembers/3] mifos/password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-200) Separate Current Accounts from Savings Accounts
[ https://issues.apache.org/jira/browse/FINERACT-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-200: -- Labels: gsoc p3 (was: p3) > Separate Current Accounts from Savings Accounts > --- > > Key: FINERACT-200 > URL: https://issues.apache.org/jira/browse/FINERACT-200 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p3 > > https://mifosforge.jira.com/browse/MIFOSX-1361 > Current Accounts and Savings accounts are two different category of deposit > products. At least at the User Interface, these should be treated as two > different products. At the platform level, we should have a field that > differentiate these (perhaps m_savings.product.deposit_type_enum and > m_savings_account.account_type_enum) > Savings accounts should not allow overdraft and hence the parameters > associated to overdraft can be defaulted to null. > Current accounts allow overdraft and overdraft limits and charges/interest > for overdrafts. Also they usually have zero interest rate, but we should > retain the interest rate fields for current account. > Fees - should be separated out for current accounts and savings accounts. > Also, need to be evaluated how this will impact savings reports. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-17) Community App does not load on very slow 2g internet connections
[ https://issues.apache.org/jira/browse/FINERACT-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-17: - Labels: gsoc p3 (was: p3) > Community App does not load on very slow 2g internet connections > > > Key: FINERACT-17 > URL: https://issues.apache.org/jira/browse/FINERACT-17 > Project: Apache Fineract > Issue Type: Improvement > Components: System >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Blocker > Labels: gsoc, p3 > > https://mifosforge.jira.com/browse/MIFOSX-2164 > The community app does not load on very slow 2g internet connections. > You should be able to reproduce the same by using a tool like > http://www.netlimiter.com/ and throttling the speed to less than 40 kb/ps . > You would need to do this after clearing your cache or on a private tab to > ensure that the community app is not already cached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-210) Database Tampering and Detection of Data Fraud by Using the Forensic Scrutiny Technique
[ https://issues.apache.org/jira/browse/FINERACT-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-210: -- Labels: gsoc p3 (was: p3) > Database Tampering and Detection of Data Fraud by Using the Forensic Scrutiny > Technique > --- > > Key: FINERACT-210 > URL: https://issues.apache.org/jira/browse/FINERACT-210 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p3 > > Abstract > Database Tampering and the Data Fiddle is one of the important role in > Database Management System (DBMS).To Provide the security to the Data Storage > Has Become Requirement of our time. The Main Objective of this is to choose > among different techniques the best and detection of different Places in > Database. We could use the cryptographic hash > algorithm to discover the tampering of a Database. Consequently the Tiled > Bitmap Forensic analysis algorithm helps to find at what time and possibly > finally who and why Tamper the Database. This algorithm establish the concept > of applicant places (possible places of spot tampering) and prevent the > intruder, the computing of the candidate set is > also presented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-224) Linked account for topup loans should be displayed in both "from" and "to" Account details apge
[ https://issues.apache.org/jira/browse/FINERACT-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-224: -- Labels: gsoc p3 (was: p3) > Linked account for topup loans should be displayed in both "from" and "to" > Account details apge > --- > > Key: FINERACT-224 > URL: https://issues.apache.org/jira/browse/FINERACT-224 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: subramanyasn >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p3 > > Currently if the top up loan is disbursed, in the account details page of the > new loan, the closed loan account ID is getting displayed, it would be better > if the ID of the new loan (because of which the loan account closed) should > be displayed in the closed loan also. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-232) Ability to Post General Ledger Entries Directly to Customer Account
[ https://issues.apache.org/jira/browse/FINERACT-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-232: -- Labels: gsoc p3 (was: p3) > Ability to Post General Ledger Entries Directly to Customer Account > --- > > Key: FINERACT-232 > URL: https://issues.apache.org/jira/browse/FINERACT-232 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p3 > Attachments: Complete New UI Mock up for Journal Entry Screen.png, > Enhancements for Journal Entry.pdf > > > https://mifosforge.jira.com/browse/MIFOSX-2182 > From MIFOS X: As an accountant, i would like to be able to make a transfer > from a client's account (Savings Account or Loan Account) to a GL Account and > also be able to make transfer from a GL Account (e.g Cash at Hand) to > Client's Account (e.g Savings Account or Loan Account) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-236) Savings product configuration changes should affect existing accounts
[ https://issues.apache.org/jira/browse/FINERACT-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-236: -- Labels: gsoc p3 requirements (was: p3 requirements) > Savings product configuration changes should affect existing accounts > - > > Key: FINERACT-236 > URL: https://issues.apache.org/jira/browse/FINERACT-236 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p3, requirements > > https://mifosforge.jira.com/browse/MIFOSX-2510 > If an institution changes a configuration in either a particular loans or > savings product, this change should be applied to already existing accounts > created. > E.g if during savings product creation, MFI sets Min Balance as 5,000 and > after some time decided to change it 10,000 then i think this should not be > applied to new accounts created after this change but rather cut across any > other existing account. This should apply to loan product configurations. > These are some of the ways this can be achieved:- > # This product configuration account values like Min Balance, Interest rate > etc should not be stored in the account table but rather a pointer can be set > to them > # When a change is made to a product configuration, in the respective > accounts table i.e loan account table or savings account table depending on > the product type being modified, changes must be updated accounting like if > interest rate or min balance value is change, query should be include when > submitting these changes to effect them in the account table, some time like > select * from m_savings_account where product_id = (product id being > modified), then update the necessary values in the table > This should be for :- > * Savings Product > * Recurring Deposit > * Fixed Deposit > * Charges -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-239) Ability to adjust Principal and Interest as a super user
[ https://issues.apache.org/jira/browse/FINERACT-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-239: -- Labels: gsoc p3 (was: p3) > Ability to adjust Principal and Interest as a super user > > > Key: FINERACT-239 > URL: https://issues.apache.org/jira/browse/FINERACT-239 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p3 > > https://mifosforge.jira.com/browse/MIFOSX-2518 > This should allow you to make adjustments on the principal and/or interest > balances of a loan account for correction purposes. The adjustment process > should always be a voucher transaction not cash and should be fixed by > default. > *Credit Principal*. This allows you to correct an erroneous posting of > disbursement, whether a wrong amount was posted for the disbursement or it > was posted to a wrong account. > *Debit Principal*. This allows you to correct an erroneous posting of a > repayment, whether a wrong amount was posted or it was posted to a wrong > account. > *Credit Accrual. *This allows you to correct erroneous posting of loan > accruals—interest, penalties and charges—to an account or to waive penalties. > This is also used to reduce accruals whenever there was a delay in the > posting of a repayment. > *Debit Accrual.* This allows you to apply loan accruals—interest, penalties > and charges—to an account in cases of repayment cancellation. This is > particularly necessary if the cancellation occurred after the day that the > repayment was posted -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-255) Customer Complaint Handling
[ https://issues.apache.org/jira/browse/FINERACT-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-255: -- Labels: gsoc p3 (was: p3) > Customer Complaint Handling > --- > > Key: FINERACT-255 > URL: https://issues.apache.org/jira/browse/FINERACT-255 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Edward Cable >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p3 > > Moved over from https://mifosforge.jira.com/browse/MIFOSX-2299 > This is an oft-requested feature and the specification needs to be developed > based on community requirements. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-240) System User Administrations
[ https://issues.apache.org/jira/browse/FINERACT-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-240: -- Labels: gsoc p3 (was: p3) > System User Administrations > > > Key: FINERACT-240 > URL: https://issues.apache.org/jira/browse/FINERACT-240 > Project: Apache Fineract > Issue Type: Wish > Components: System >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p3 > > https://mifosforge.jira.com/browse/MIFOSX-2185 > As a system administrator, I would like to be able to:- > * see which user is logged or not logged into Mifos X. > ||User Name||Status|| > |mifos|Connected| > |admin|Connected| > |robert|Not Connected| > * forcefully logout a logged in user remotely > * not be able to edit user credentials plus assigning a role when a user is > logged in > * see which machine the user is logged in from > * restrict users from logging in from multiple computer/devices > simultaneously i.e if user A is logged in from PC1, and if he tries to login > from PC2, Mifos X should be able to tell the user that he is already login > from PC1 and should reject this login unless he logout from PC1 then he can > proceed with this login session > * enable audit trail to track PC/Device names with user name against any > action the user performs in Mifos X e.g Creating a client. a column can be > added (pc_name) for this. > All this can make administration and tracking of any errors perfect -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-250) Plance Guarantor Funds On Hold
[ https://issues.apache.org/jira/browse/FINERACT-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-250: -- Labels: gsoc p3 (was: confirm p3) > Plance Guarantor Funds On Hold > -- > > Key: FINERACT-250 > URL: https://issues.apache.org/jira/browse/FINERACT-250 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p3 > > Functional Spec: > https://cwiki.apache.org/confluence/display/FINERACT/Blocking+Funds+in+Guarantor+Account -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-253) Charge time type on Client Charges
[ https://issues.apache.org/jira/browse/FINERACT-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-253: -- Labels: gsoc p3 (was: p3) > Charge time type on Client Charges > -- > > Key: FINERACT-253 > URL: https://issues.apache.org/jira/browse/FINERACT-253 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p3 > > https://mifosforge.jira.com/browse/MIFOSX-2315 > Currently client charges can only be created for a Specified Due Date. > This poses a challenge to organizations which charges their members periodic > fees e.g. Welfare Groups which charges monthly subscription fee which is an > income to the organization or MFIs which does Annual Membership Renewal Fee. > Charge time type for Client Charges to be extended to also include the > following: > * Daily - For those who would wish to charge daily fee. > * Weekly - For those who would wish to charge Weekly fee > * Monthly - For those who would wish to charge Monthly fee > * Annual - For those who would wish to charge Annual fee. > When any of the above option is selected, then a new option to specify > frequency must appear so that the Admin can input number of Repeats for that > particular fee (annual fee not really necessary as the charge should be for 1 > year. > ADDITIONAL COMMENT: > Client Level Fee was partially implemented in V15.09. Membership fee > functionality is missing to allow for customized drop down (see attached > image). The only option is "specified date" I do not see this feature in > Manage Code list, so I see no area where additional options can be added for > this drop down field. There should be an option for "at client creation" so > that the work flow can follow as described in: > https://mifosforge.jira.com/wiki/x/eICDBQ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-246) To add new tenants with active scheduler jobs without restarting the server.
[ https://issues.apache.org/jira/browse/FINERACT-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-246: -- Labels: gsoc p3 (was: p3) > To add new tenants with active scheduler jobs without restarting the server. > > > Key: FINERACT-246 > URL: https://issues.apache.org/jira/browse/FINERACT-246 > Project: Apache Fineract > Issue Type: Improvement > Components: System >Reporter: shreyaank >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p3 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-388) Improvement in the characters allowed in the column names of Data tables
[ https://issues.apache.org/jira/browse/FINERACT-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-388: -- Labels: gsoc p3 volunteers (was: p3 volunteers) > Improvement in the characters allowed in the column names of Data tables > > > Key: FINERACT-388 > URL: https://issues.apache.org/jira/browse/FINERACT-388 > Project: Apache Fineract > Issue Type: Improvement > Components: Data Tables >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p3, volunteers > Attachments: Datatable.png > > > Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2826. > Original Description: > The system when configuring Data tables, in the field of column name it does > not allow some of the characters which it could be better to be allowed. For > instance when you want to call your column "Guarantor's phone number" or "A/C > No" the system through an error because of character ' and / > I would suggest for the system to be able to allow other characters rather > than alpha-numeric only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-305) Dropdowns are using values directly from API instead of using translation
[ https://issues.apache.org/jira/browse/FINERACT-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-305: -- Labels: gsoc p3 (was: p3) > Dropdowns are using values directly from API instead of using translation > - > > Key: FINERACT-305 > URL: https://issues.apache.org/jira/browse/FINERACT-305 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p3 > > Reported by Chandrika at https://mifosforge.jira.com/browse/MIFOSX-2081 > Original Description: > For example, the below dropdown uses documenttype.name from API (which is by > default in English language).Instead we should use > translate(documenttype.name) so that the values will be in sync with the > respective language selected by user. > ng-options="documenttype.id as documenttype.name for documenttype in > documenttypes" value="documenttype.id" required="required" > class="form-control"> -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-290) Additional collateral options. (pawn shop support)
[ https://issues.apache.org/jira/browse/FINERACT-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-290: -- Labels: gsoc p3 (was: p3) > Additional collateral options. (pawn shop support) > -- > > Key: FINERACT-290 > URL: https://issues.apache.org/jira/browse/FINERACT-290 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p3 > > Reported by MIFOS@FINA at https://mifosforge.jira.com/browse/MIFOSX-1734 > Original Description: > In order to implement Mifos in Georgia and post-soviet region, we need > additional pawn shop collateral support. For example functionality to bind a > car to a loan, with all the details of the car. Also is we want to bind a > house with a price 100 000$ to a loan, and the loan is only 10 000$, we must > be able to bind the house to another loan ( up to 90 000$ ). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-395) Add datatables to Staff
[ https://issues.apache.org/jira/browse/FINERACT-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-395: -- Labels: gsoc p3 (was: p3) > Add datatables to Staff > --- > > Key: FINERACT-395 > URL: https://issues.apache.org/jira/browse/FINERACT-395 > Project: Apache Fineract > Issue Type: Improvement > Components: Data Tables >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p3 > > Reported by Swapnil at https://mifosforge.jira.com/browse/MIFOSX-2344 > If Datatables can be linked to Staff it will help to maintain different > parameters like Attendance, Office assignment history, HR profile etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-277) No option to writeoff Overdraft account in Client savings account page
[ https://issues.apache.org/jira/browse/FINERACT-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-277: -- Labels: gsoc p3 (was: p3) > No option to writeoff Overdraft account in Client savings account page > -- > > Key: FINERACT-277 > URL: https://issues.apache.org/jira/browse/FINERACT-277 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p3 > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1363 > Original Description: > Write off option in overdraft account (in savings) is not present. It should > be implemented. > In Saving product creation page for cash based accounting writeoff is > introduced under Expense heading -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-408) When closing Savings account and Withdraw Balance option is enabled, only cash withdrawal is possible, not able to withdraw to a GL Account by Voucher
[ https://issues.apache.org/jira/browse/FINERACT-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-408: -- Labels: fineract-2.0 gsoc p3 (was: confirm fineract-2.0 p3) > When closing Savings account and Withdraw Balance option is enabled, only > cash withdrawal is possible, not able to withdraw to a GL Account by Voucher > -- > > Key: FINERACT-408 > URL: https://issues.apache.org/jira/browse/FINERACT-408 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Critical > Labels: fineract-2.0, gsoc, p3 > > As a system admin, i should be able to close a savings account and make > Balance withdrawal to a GL Account (Contra Account) and payment type for this > should be restricted to by Voucher only. > If Withdraw Balance is not to a GL Account then Cash Payment Type. > Extend this functionality of Withdraw Balance to Share Accounts too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-396) Append the word 'datatable' in the code value to avoid name collision during upgrades
[ https://issues.apache.org/jira/browse/FINERACT-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-396: -- Labels: gsoc p3 (was: p3) > Append the word 'datatable' in the code value to avoid name collision during > upgrades > - > > Key: FINERACT-396 > URL: https://issues.apache.org/jira/browse/FINERACT-396 > Project: Apache Fineract > Issue Type: Improvement > Components: Data Tables >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p3 > > Reported by Thynn Winn at https://mifosforge.jira.com/browse/MIFOSX-2812 > Original Description: > There is a unique constraint on m_permission.code. > During our upgrade from 16.03.03 to 16.11.01, we had a code value collision > and couldn't execute the permission section of upgrade script V316. We had a > datatable entry with 'Address' and the code for permission was already > created with grouping = datatable. > When this script V316 makes entries to m_permission with the same code > values, it's erroring out. > Since users can create any values in datatable, we should either append > 'datatable' in the code value as part of data table creation process or make > the unique key on both columns – grouping and code (not just code alone). The > former is safer for those who are using the application heavily. > This will eliminate the chance of colliding user data table values and the > enhancements the community make in the upgrade scripts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-403) Intergrate a chat system where other system users can chat with the system admin
[ https://issues.apache.org/jira/browse/FINERACT-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-403: -- Labels: fineract-2.0 gsoc p3 (was: fineract-2.0 p3) > Intergrate a chat system where other system users can chat with the system > admin > > > Key: FINERACT-403 > URL: https://issues.apache.org/jira/browse/FINERACT-403 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: fineract-2.0, gsoc, p3 > > As a user at one branch of an MFI which can be in a different country, i > should be able to have an inbuilt chat system with Fineract to interact with > my IT Officer at the head officer to trouble should any problem > As systems users at institutional level (different MFIs have a common chat > room), we should be able to have open chat (group chat) or private chat with > system developers especially one that handles users and have troubleshot > discussion -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-391) Fund Management-Delete Enhancement
[ https://issues.apache.org/jira/browse/FINERACT-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-391: -- Labels: gsoc p3 (was: p3) > Fund Management-Delete Enhancement > -- > > Key: FINERACT-391 > URL: https://issues.apache.org/jira/browse/FINERACT-391 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p3 > > Reported by Agness Meena at https://mifosforge.jira.com/browse/MIFOSX-2822 > Go to Admin > Organization > Manage Fund > Once you create a new fund you can only edit it but not deleting it. > Need a Delete button to delete existing fund. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-409) Improvement to min_required_balance: Make minimum balance for all savings accounts global
[ https://issues.apache.org/jira/browse/FINERACT-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-409: -- Labels: gsoc p3 volunteers (was: p3 volunteers) > Improvement to min_required_balance: Make minimum balance for all savings > accounts global > - > > Key: FINERACT-409 > URL: https://issues.apache.org/jira/browse/FINERACT-409 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p3, volunteers > > Currently when you have created savings account for a product, the minimum > balance for that product is one capture and entered in min_required_balance > for this savings account. Now if you change the minimum balance for this > product, accounts already created are not affected by this changes i.e > min_required_balance is not updated for the accounts in existence. > Any changes in min required balance should affect all accounts of that > product i.e those accounts already created and those yet to be created. This > will make sense and will be fair to all clients -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-404) Send SMS with custom text to every staff in an Office manually from UI
[ https://issues.apache.org/jira/browse/FINERACT-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-404: -- Labels: gsoc p3 (was: p3) > Send SMS with custom text to every staff in an Office manually from UI > -- > > Key: FINERACT-404 > URL: https://issues.apache.org/jira/browse/FINERACT-404 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Trivial > Labels: gsoc, p3 > > Reported by [~vorburger] at https://mifosforge.jira.com/browse/MIFOSX-776 > Original Description: > (Based on https://mifosforge.jira.com/browse/MIFOSX-775) > The goal of this issue is to offer an end-user a UI to send a manual SMS > message to a all Staff in an Office. > I'm not sure exactly where in the new AngularJS-based community-app such an > action would be made available - others should comment. > I'd expect that the looping over all staff, given an office ID, would happen > on the server side via a new REST API (although theoretically you could do > this in JS on the client-side as well). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-407) Ability to Re-open closed Accounts (especially Savings and Share Accounts)
[ https://issues.apache.org/jira/browse/FINERACT-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-407: -- Labels: fineract-2.0 gsoc p3 (was: confirm fineract-2.0 p3) > Ability to Re-open closed Accounts (especially Savings and Share Accounts) > -- > > Key: FINERACT-407 > URL: https://issues.apache.org/jira/browse/FINERACT-407 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: fineract-2.0, gsoc, p3 > > When a client has not make transactions for many years for example, the MFI > may not know if the client is alive or dead so the MFI can decide to close > this client's Accounts (Savings and Share Accounts). The balances of this > account can be transferred to a GL Account. > Client - GL Transfer: DR Client Accounts and CR. GL Account e.g Share Transfer > After some time, the client surfaces and would like to make transactions on > his accounts. > As a system admin, i should be able to re-open these closed accounts and be > able to transfer the balances from the contra Account back to client's > Savings Account either automatically or manually through batch/journal > Entries where you DR. GL Accounts affected (where the balances are > transferred) and Credit Clients Savings and Share Accounts with the balances > at closure. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-424) SELF-SERVICE: store 4 digit pin on back-end
[ https://issues.apache.org/jira/browse/FINERACT-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-424: -- Labels: gsoc p3 (was: p3) > SELF-SERVICE: store 4 digit pin on back-end > --- > > Key: FINERACT-424 > URL: https://issues.apache.org/jira/browse/FINERACT-424 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Edward Cable >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p3 > > First off, in order to make it easier for a user to log in and not have to > fully authenticate themselves each time they leave the self-service app, we > wanted to enable a 4 digit pin code that could be used to log in to the app > (once fully authenticated for a first time). This is pretty standard practice > in banking apps. > We didn't want to store that locally since it wouldn't be secure on phones > that are rooted. > With that constraint, we need to be able to store this pin on the back-end - > then it can also be shared across phones as well. > See https://github.com/openMF/self-service-app/issues/115 and > https://github.com/openMF/self-service-app/issues/132 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-227) Option For Creating Loan Loss provisioning for total principle outstanding or total outstanding
[ https://issues.apache.org/jira/browse/FINERACT-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-227: -- Labels: gsoc p2 (was: p2) > Option For Creating Loan Loss provisioning for total principle outstanding or > total outstanding > --- > > Key: FINERACT-227 > URL: https://issues.apache.org/jira/browse/FINERACT-227 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: venkat Ganesh >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-251) Ability to set Maximum withdrawal amount per day
[ https://issues.apache.org/jira/browse/FINERACT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-251: -- Labels: gsoc p2 (was: p2) > Ability to set Maximum withdrawal amount per day > > > Key: FINERACT-251 > URL: https://issues.apache.org/jira/browse/FINERACT-251 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > > https://mifosforge.jira.com/browse/MIFOSX-1873 > There should be a limit for Client withdrawal from a savings amount. Say the > MFI can Set 700,000 as withdrawal limit on any savings product. A client can > withdrawal several times in a day as long as the limit is not exceeded. But > when that limit is reached, the system should reject account withdrawal till > the following day which normally starts at Mid-Night. This is also importance > in the future where ATM functionality is introduced in Mifos. > This should be set during Savings Product creation only. > Also on the view savings page there should be two type of balances: > 1. Current or Actual Balance, this show the balance in the savings account. > 2. Available balance (= Current or Actual Balance minus Minimum Balance > Required) i.e the amount that can not be withdrawn from the account is > enforce Min. balance is set to true. This is good for quick reference to tell > a client what amount he/she can withdraw from the savings account, saves time > of manual calculation. > See Screen mockup > Options -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-238) Account Entry Closure
[ https://issues.apache.org/jira/browse/FINERACT-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-238: -- Labels: gsoc p2 (was: p2) > Account Entry Closure > - > > Key: FINERACT-238 > URL: https://issues.apache.org/jira/browse/FINERACT-238 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Critical > Labels: gsoc, p2 > > https://mifosforge.jira.com/browse/MIFOSX-2644 > When making account closure for a day, the system should reject closing > entries if there are some users logged into the system. It should only allow > one user with rights to make closing entry to do this else should throw error > that users are still logged into the system hence can not close books of > accounts. > This can be used to make End of days. At this point it should check all wrong > journal entry posting and generated reports accounting especially GL Accounts > balances against Customer Account balances - Totals should be the same e.g > Voluntary Savings GL total = Voluntary Customer Savings total etc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-322) Rewarding Early Repayment
[ https://issues.apache.org/jira/browse/FINERACT-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-322: -- Labels: gsoc p2 (was: p2) > Rewarding Early Repayment > - > > Key: FINERACT-322 > URL: https://issues.apache.org/jira/browse/FINERACT-322 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p2 > > Reported by Shepard Chihoro at https://mifosforge.jira.com/browse/MIFOSX-2520 > Original Description: > MIFOSX does not reward customers who make early repayments on a flat interest > calculation method.My normal client contract is has a maximum repayment > period of 6 months and a minimum repayment period of 3 months.On > disbursement,MIFOSX calculates the interest for the entire 6 months and makes > principal and interest for 6 months outstanding.In the event that the > customer repays the full principal in 3 months,the customer`s account remains > with 3 months interest due.I would like to see interest outstanding being > stopped once the principal has been repaid in full. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-362) Configure Penalty Charge depending on loan's interest rate
[ https://issues.apache.org/jira/browse/FINERACT-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-362: -- Labels: gsoc p2 (was: p2) > Configure Penalty Charge depending on loan's interest rate > -- > > Key: FINERACT-362 > URL: https://issues.apache.org/jira/browse/FINERACT-362 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Lionel Raymundi >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > > Our business requirement is to charge penalties for unpaid overdued > installments as follows: > "Every overdue day, charge (installment capital) * (daily interest rate * > 1.5)" > In other words, this means to penalize the overdue by charging a 50% more of > the agreed interest over the due capital. > To solve this, a new Charge Calculation type could be created. It should be > something like "% Amount of the installment * Annual nominal interest rate / > 100". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-269) Add Info Base on Clients Account - Loans, Shares, Fixed Deposit, Loans and Recuring Deposit Account
[ https://issues.apache.org/jira/browse/FINERACT-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-269: -- Labels: gsoc p2 (was: p2) > Add Info Base on Clients Account - Loans, Shares, Fixed Deposit, Loans and > Recuring Deposit Account > --- > > Key: FINERACT-269 > URL: https://issues.apache.org/jira/browse/FINERACT-269 > Project: Apache Fineract > Issue Type: Improvement > Components: Client >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > Attachments: Infobase.pdf > > > Infobase > This allows you to add free-form descriptions or notes to certain accounts. > These notes can be unlimited in size and can be used to provide all kind of > additional information about any account or its owner. > Later then whenever this account will be accessed this information will be > displayed on the screen as in following example. > See attachment for visual explanation > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-254) Password Email Notice
[ https://issues.apache.org/jira/browse/FINERACT-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-254: -- Labels: Volunteer gsoc p2 (was: Volunteer p2) > Password Email Notice > - > > Key: FINERACT-254 > URL: https://issues.apache.org/jira/browse/FINERACT-254 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > > While requesting documentation be written to describe how an organization can > customize the outgoing message to the user that provides their password, it > was discovered that this is hard coded. > https://mifosforge.jira.com/browse/MXD-107 > The expected result is that an organization can enter their own subject line, > and edit the message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-256) Fixed Asset Register
[ https://issues.apache.org/jira/browse/FINERACT-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-256: -- Labels: gsoc p2 volunteers (was: p2 volunteers) > Fixed Asset Register > > > Key: FINERACT-256 > URL: https://issues.apache.org/jira/browse/FINERACT-256 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Edward Cable >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2, volunteers > > Migrated over from https://mifosforge.jira.com/browse/MIFOSX-2330 > Need requirements from the community to drive forward. Please contribute to > specification at linked URL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-398) Loan write-off option add
[ https://issues.apache.org/jira/browse/FINERACT-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-398: -- Labels: gsoc p2 (was: p2) > Loan write-off option add > - > > Key: FINERACT-398 > URL: https://issues.apache.org/jira/browse/FINERACT-398 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p2 > > Reported by Joe at https://mifosforge.jira.com/browse/MIFOSX-2306 > Original Description: > In Mifos when you write off a loan the system takes the loss off all the > interest and principal due that would of accrued over the course of the WHOLE > loan term. When we write off a loan we need the option to have the system > take the write off from that exact date of the write off. So the loss would > onlt show/post the interest and principal that have accrued to that exact > point of write off. > OptionsAttachments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-400) Manage Funds Enhancement
[ https://issues.apache.org/jira/browse/FINERACT-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-400: -- Labels: gsoc p2 (was: p2) > Manage Funds Enhancement > > > Key: FINERACT-400 > URL: https://issues.apache.org/jira/browse/FINERACT-400 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p2 > > Reported by Dayna Harp at https://mifosforge.jira.com/browse/MIFOSX-2239 > Original Description: > For those organizations that receive donor funds that are intended to be used > for specific loan programs, there should be the ability to indicate the > amount of money in the fund. As loans for that fund type are made, the > available remaining funds should decline. There should also be the feature to > alert the loan officer when loans from that fund are gone. > For example: https://demo2.openmf.org/preview/#/managefunds/ Add fields to > indicate amount of fund, date of origination, end date (if applicable), > description field > This fund maps to GL > When loan is made, system automatically makes entry to decrease the fund. > If loan is approved for $5000 and only $3500 left in fund, Loan Officer gets > an alert and system allows $3500 from fund then requests a secondary source > for remaining approved balance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-390) Reactivate of a group after being closed
[ https://issues.apache.org/jira/browse/FINERACT-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-390: -- Labels: gsoc p2 (was: p2) > Reactivate of a group after being closed > > > Key: FINERACT-390 > URL: https://issues.apache.org/jira/browse/FINERACT-390 > Project: Apache Fineract > Issue Type: Improvement > Components: Groups >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p2 > > Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2823 > Original Description: > When the closed group wants again to apply for a loan, in Mifos X now you > have to create another new group > For better group management, i request for new feature of be able to > reactivate a group once it has been closed. This can help to reduce many > closed groups -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-394) Ability to link savings account to loan after submission of loan application
[ https://issues.apache.org/jira/browse/FINERACT-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-394: -- Labels: gsoc p2 (was: p2) > Ability to link savings account to loan after submission of loan application > > > Key: FINERACT-394 > URL: https://issues.apache.org/jira/browse/FINERACT-394 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan, Savings >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p2 > > Reported by Sangamesh at https://mifosforge.jira.com/browse/MIFOSX-2359 > Original Description: > With the existing behaviour of linking savings account, it allows to link > loan while submitting the New loan application. > Enhancement: > It should allow linking savings account at the following state also:- > 1. Submitted and pending approval, > 2. Approved, > 3. Active. > Enhancement should also support linking of loan charges from a savings > account. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-393) Separate Application table name should be provided for a client as Entity while creating the datatable
[ https://issues.apache.org/jira/browse/FINERACT-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-393: -- Labels: gsoc p2 (was: p2) > Separate Application table name should be provided for a client as Entity > while creating the datatable > -- > > Key: FINERACT-393 > URL: https://issues.apache.org/jira/browse/FINERACT-393 > Project: Apache Fineract > Issue Type: Improvement > Components: Data Tables >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p2 > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2491 > Original Description: > Now in community app the data table created for a client is getting displayed > under "Clients" created as client or Entity. But some of the data tables > created for a client is not useful for Entity. > Eg. Create a data table as Spouse details for a client, which is useful for a > client but not for entity. > So it would be better to have separate Application table name for Entity so > as to avoid confusion between Client and Entity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-384) Product Mix - for Saving Accounts
[ https://issues.apache.org/jira/browse/FINERACT-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-384: -- Labels: gsoc p2 (was: p2) > Product Mix - for Saving Accounts > - > > Key: FINERACT-384 > URL: https://issues.apache.org/jira/browse/FINERACT-384 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > > The Product mix for Loan Accounts needs to be added to cater for Savings > Products as some MFI have a policy to restrict a client from opening some > savings product together by the same client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-405) Client/Staff SMS phone number back-end validation, incl. default country code
[ https://issues.apache.org/jira/browse/FINERACT-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-405: -- Labels: gsoc p2 (was: p2) > Client/Staff SMS phone number back-end validation, incl. default country code > - > > Key: FINERACT-405 > URL: https://issues.apache.org/jira/browse/FINERACT-405 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Trivial > Labels: gsoc, p2 > > Reported by [~vorburger] at https://mifosforge.jira.com/browse/MIFOSX-779 > Original Description: > We'll likely start with just using String / VARCHAR as type for SMS phone > numbers in client/staff, but in order get serious about SMS support, the > "data quality" of those will quickly be fairly import. > Therefore, it would probably be very useful if the platform technically > enforced that such phone numbers are always represented and stored in the > database including country code prefix (using the +91 ... notation). > The should also have some validation logic in the UI enforcing this > (FrontlineSMS says: "This number is not in international format. This may > cause problems matching messages to contacts."). > The UI could assist in making it easier to capture phone numbers and propose > a default country code saved in some System Administration configuration > somewhere when entering new phone numbers. > The Java back-end could use some proper strongly typed self validating > PhoneNumber value object type, instead of just passing around String? May be > something like this exists already? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-414) Ability for every tenant to know the sms credit balance they have
[ https://issues.apache.org/jira/browse/FINERACT-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-414: -- Labels: fineract-2.0 gsoc p2 (was: fineract-2.0 p2) > Ability for every tenant to know the sms credit balance they have > - > > Key: FINERACT-414 > URL: https://issues.apache.org/jira/browse/FINERACT-414 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: fineract-2.0, gsoc, p2 > > As a system, admin, the system should be able to query my sms Credits balance > from my provider and alert me when credit is running low or zero so that i > can buy more credits other than be caught in a situation where you think you > have credits and yet you don't and sms are not being sent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-426) Filter to optionally compress response with gzip
[
https://issues.apache.org/jira/browse/FINERACT-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santosh Math updated FINERACT-426:
--
Labels: easyfix gsoc newbie p2 performance (was: easyfix newbie p2
performance)
> Filter to optionally compress response with gzip
>
>
> Key: FINERACT-426
> URL: https://issues.apache.org/jira/browse/FINERACT-426
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: Avik Ganguly
>Assignee: Markus Geiss
>Priority: Minor
> Labels: easyfix, gsoc, newbie, p2, performance
>
> Accept a query parameter like isCompressionRequired. If this query param is
> present, compress the response using gzip. This will ensure less bandwidth
> usage if field apps are using mobile data.
> Sample Code for response filter :-
> Inside filter method :-
> if
> (request.getRequestHeaders().getFirst(HttpHeaders.ACCEPT_ENCODING).contains("gzip"))
> {
>
> response.getHttpHeaders().add(HttpHeaders.CONTENT_ENCODING, "gzip");
> response.setContainerResponseWriter(
> new
> Adapter(response.getContainerResponseWriter()));
> }
> private static final class Adapter implements ContainerResponseWriter {
> private final ContainerResponseWriter crw;
> private GZIPOutputStream gos;
> Adapter(ContainerResponseWriter crw) {
> this.crw = crw;
> }
>
> public OutputStream writeStatusAndHeaders(long contentLength,
> ContainerResponse response) throws IOException {
>gos = new GZIPOutputStream(crw.writeStatusAndHeaders(-1,
> response));
>return gos;
> }
> public void finish() throws IOException {
> gos.finish();
> crw.finish();
> }
> }
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FINERACT-401) when assigning a a loan officer to a client. Can we add and optional parameter called "inhertClientActiveAccounts" . This is similar to the one we have on assigning a l
[ https://issues.apache.org/jira/browse/FINERACT-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-401: -- Labels: gsoc p2 (was: p2) > when assigning a a loan officer to a client. Can we add and optional > parameter called "inhertClientActiveAccounts" . This is similar to the one we > have on assigning a loan officer to a group > -- > > Key: FINERACT-401 > URL: https://issues.apache.org/jira/browse/FINERACT-401 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p2 > > Reported by Andrew at https://mifosforge.jira.com/browse/MIFOSX-2115 > Original Description: > when assigning a a loan officer to a client. Can we add and optional > parameter called "inhertClientActiveAccounts" . This is similar to the one we > have on assigning a loan officer to a group. > I know the proposeAndAccept Transfer can do this but a lot of our clients > make mistakes while making payments before transferring clients to differrent > loan officer in the same office . Due to this they cannot adjust the > transaction or undo disbursal since the client has been transferred. Adding > this functionality will avoid them using the proposeAndAcceptTransfer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-410) Ability to remove On-Hold flag and make the amount available for the client (loan gurantor) for withdrawal
[ https://issues.apache.org/jira/browse/FINERACT-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-410: -- Labels: Volunteer gsoc p2 (was: Volunteer p2) > Ability to remove On-Hold flag and make the amount available for the client > (loan gurantor) for withdrawal > -- > > Key: FINERACT-410 > URL: https://issues.apache.org/jira/browse/FINERACT-410 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > > When a client guarantees a loan and some amount of his/her savings is put > onHold, he/she can not withdraw this amount till the loan client finishes > his/her loan. NB: I stand to be corrected if i understood his wrongly. > As a manager, i should be able to remove the onhold flag and make the client > to withdraw the amount onHold. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-425) Jobs configurable by loans / savings product and office.
[ https://issues.apache.org/jira/browse/FINERACT-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-425: -- Labels: features gsoc p2 performance (was: features p2 performance) > Jobs configurable by loans / savings product and office. > > > Key: FINERACT-425 > URL: https://issues.apache.org/jira/browse/FINERACT-425 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Reporter: Avik Ganguly >Assignee: Markus Geiss >Priority: Major > Labels: features, gsoc, p2, performance > > Allow saving key-value pairs against each job. Key populated in front-end can > be a free text field or an enum consisting of Loan Product / Savings Product > / Office. If pre-defined key is selected, populate corresponding list of > existing loan product / savings product / office in value field's dropdown. > The jobs can receive this key-value pair as a function parameter by setting > arguments on the jobDetailFactoryBean created in the function > createJobDetail(ScheduledJobDetail) in the class JobRegisterServiceImpl. > If the following jobs has above parameters passed to it, it should add > corresponding office/product filter where clause to its read query. > Add Accrual Transactions > Add Periodic Accrual Transactions > Add Accrual Transactions For Loans With Income Posted As Transactions > Generate Loan Loss Provisioning > Post Interest for Savings > Update Loan Summary > This feature can be made more useful with node-aware scheduler as different > nodes can be configured to perform the job for different products/offices > resulting in distribution of load. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-431) Should not allow more than expected loan term based on 'number of repayments' and 'Repaid every' values.
[ https://issues.apache.org/jira/browse/FINERACT-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-431: -- Labels: gsoc p2 (was: p2) > Should not allow more than expected loan term based on 'number of > repayments' and 'Repaid every' values. > - > > Key: FINERACT-431 > URL: https://issues.apache.org/jira/browse/FINERACT-431 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Mexina Daniel >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p2 > > In loan application, the frequency of the loan term has to be the same with > the frequency of repaid every (days/weeks/months/years), by this : loan term > = number of repayment x repaid every. > e.g > 1. Create a loan product and fill the necessary requirements (put default > number of repayment = 6, repaid every = 1 month) > 2. Create a loan account to an active client and fill all necessary > requirement ( put loan term = 8 months), leave the number of repayment to 6. > The system is allowing the loan term to be greater than (number of repayments > x repaid every) and provide the repayment schedule based on 'number of > repayments' and 'repaid every' values > It should deny the submission and through an error like when you provide loan > term less than (number of repayments x repaid every) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-442) Add Note/Comment fields to Share Account Transactions
[ https://issues.apache.org/jira/browse/FINERACT-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-442: -- Labels: Volunteer gsoc p2 (was: Volunteer p2) > Add Note/Comment fields to Share Account Transactions > - > > Key: FINERACT-442 > URL: https://issues.apache.org/jira/browse/FINERACT-442 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > > As a cashier at a teller, i would like to add custom transaction description > to share account transactions e.g Share Dep - Robert -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-428) Parallelization of Jobs
[
https://issues.apache.org/jira/browse/FINERACT-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santosh Math updated FINERACT-428:
--
Labels: gsoc p2 performance (was: p2 performance)
> Parallelization of Jobs
> ---
>
> Key: FINERACT-428
> URL: https://issues.apache.org/jira/browse/FINERACT-428
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Loan, Savings
>Reporter: Avik Ganguly
>Assignee: Markus Geiss
>Priority: Major
> Labels: gsoc, p2, performance
>
> For starters, it will be useful to have some technical configuration added as
> job parameter for each of the below jobs, that is batch size and thread pool
> size for executor service so this has a dependency on FINERACT-425.
> Add migration script to add those 2 configurations to each of the following
> jobs with the value of batch size being 500 and thread pool size being 16 :-
> Add Accrual Transactions
> Add Periodic Accrual Transactions
> Add Accrual Transactions For Loans With Income Posted As Transactions
> Generate Loan Loss Provisioning
> Post Interest for Savings
> Update Loan Summary
> This would require separation of core functionality to a separate class.
> Simplified example :-
> ```
> final ExecutorService executor = Executors.newFixedThreadPool(threadPoolSize);
>
> final LocalDate dueDate = DateUtils.getLocalDateOfTenant();
> final Collection loansToBeRepaidData =
> this.loanReadPlatformService
> .retrieveLoansToBeRepaidFromAdvancePayment(dueDate);
> Iterable> loansToBeRepaid =
> Iterables.partition(loansToBeRepaidData, batchSize);
> final Authentication authentication =
> SecurityContextHolder.getContext().getAuthentication();
> List> advancePaymentPosters = new
> ArrayList>();
>
> for (List subList : loansToBeRepaid) {
> AdvancePaymentPoster poster = (AdvancePaymentPoster)
> this.applicationContext.getBean("advancePaymentPoster");
> poster.setLoans(subList);
> poster.setTenant(ThreadLocalContextUtil.getTenant());
> poster.setAuthentication(authentication);
> poster.setCommandService(commandService);
> advancePaymentPosters.add(Executors.callable(poster));
> }
> try {
> List> responses =
> executor.invokeAll(advancePaymentPosters);
> for(Future f : responses) {
> f.get();
> }
> } catch (InterruptedException e1) {
> e1.printStackTrace();
> }
>
> executor.shutdown();
> ```
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FINERACT-429) Node aware Scheduler
[
https://issues.apache.org/jira/browse/FINERACT-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santosh Math updated FINERACT-429:
--
Labels: gsoc p2 (was: p2)
> Node aware Scheduler
>
>
> Key: FINERACT-429
> URL: https://issues.apache.org/jira/browse/FINERACT-429
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: Avik Ganguly
>Assignee: Markus Geiss
>Priority: Major
> Labels: gsoc, p2
>
> 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
(v7.6.3#76005)
[jira] [Updated] (FINERACT-440) Include runningBalance, appUser in m_share_account_transactions table.
[ https://issues.apache.org/jira/browse/FINERACT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-440: -- Labels: Volunteer gsoc p2 (was: Volunteer p2) > Include runningBalance, appUser in m_share_account_transactions table. > -- > > Key: FINERACT-440 > URL: https://issues.apache.org/jira/browse/FINERACT-440 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > > Include the two parameters runningBalance, appUser in > m_share_account_transactions to be used to generate Share Transaction > Statement. Currently its not posible to generate standard statement since > runningBalance is missing and kind of hard to determine it from current Share > Transaction table -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-427) Paginate input queries for jobs.
[ https://issues.apache.org/jira/browse/FINERACT-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-427: -- Labels: gsoc p2 performance (was: p2 performance) > Paginate input queries for jobs. > > > Key: FINERACT-427 > URL: https://issues.apache.org/jira/browse/FINERACT-427 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Avik Ganguly >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p2, performance > > Paginate read queries for following jobs : > Add Accrual Transactions > Add Periodic Accrual Transactions > Add Accrual Transactions For Loans With Income Posted As Transactions > Generate Loan Loss Provisioning > Post Interest for Savings > Update Loan Summary > Add arbitrary page size (32000) for now which can be later replaced by the > product of two configurations (batch size * thread count for that executor > service pool) when jobs are made concurrent. > If paginating the query outside can split a loan across pages, paginate the > primary entity, i.e. loans or savings. > Ex :- If accrual read query will fetch 3 rows for same loan (3 repayment > schedule entries for which accrual is pending) and page size is 2, loan will > get split across 2 pages. Avoid this by paginating the loan entity inside the > query. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-441) Ability to Related Accounts i.e Loan Accounts with Guarantors in Client Profile
[ https://issues.apache.org/jira/browse/FINERACT-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-441: -- Labels: Volunteer gsoc p2 (was: Volunteer p2) > Ability to Related Accounts i.e Loan Accounts with Guarantors in Client > Profile > --- > > Key: FINERACT-441 > URL: https://issues.apache.org/jira/browse/FINERACT-441 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > > As a Loan Officer, i would like to easy know all accounts related to a client > in client profile with clearly defined relation. > E.g > If an account belongs to a client, the Relationship will be "Principal Owner" > If a client guarantees a loan, the account is shown on his/her profile but > the Relationship will be "Guarantor" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-471) Preview feature for uploaded document
[ https://issues.apache.org/jira/browse/FINERACT-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-471: -- Labels: gsoc p2 (was: p2) > Preview feature for uploaded document > - > > Key: FINERACT-471 > URL: https://issues.apache.org/jira/browse/FINERACT-471 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization, System >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > > Enhance Request by Boniphace Fredrick > Original Description: > Currently the system allows to upload a document and once you want to view it > again there is only one option ie, to download it. > This act can probably violate client's privacy( ie, client information > vulnerability) for example if a user(eg. Loan officer) uses somebody computer > to access system, so there is possibility he/she can download a document and > forget to delete if from that local machine > Therefore I suggest there should first an option to preview the document fist > maybe as a pdf and then a user can choose either to download, print or just > view it only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-462) Need an option to filter provisioning entries by date
[ https://issues.apache.org/jira/browse/FINERACT-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-462: -- Labels: gsoc p2 (was: gsoc2017 p2) > Need an option to filter provisioning entries by date > - > > Key: FINERACT-462 > URL: https://issues.apache.org/jira/browse/FINERACT-462 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > > Go to Accounting>Provisioning Entries > There is no option to filter provisioning entries by date. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-483) Sorting Feature fo Clients, Groups and Centers.
[ https://issues.apache.org/jira/browse/FINERACT-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-483: -- Labels: gsoc p2 (was: p2) > Sorting Feature fo Clients, Groups and Centers. > --- > > Key: FINERACT-483 > URL: https://issues.apache.org/jira/browse/FINERACT-483 > Project: Apache Fineract > Issue Type: New Feature > Components: Client, Groups >Reporter: Boniphace Fredrick >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > Attachments: Screenshot from 2017-06-23 12-44-19.png > > > Hallow, > I'm requesting for a new feature for Sorting clients, Groups and Centers > This feature will serve as a tool for easily navigation through client or > group or center listing Also it can be useful to suspect duplicate entries. > I suggest sorting criteria to base on the following inputs. > # For client listing it should be sorted by these attributes > Date (ie Activation date) > Client Name > Assigned Staff > Client ID (ie, Client #) > External Id > # For Group and Centers should be sorted regarding > Name > Assigned Staff > Group/Center ID (ie, Account #) > External Id > Also I suggest the sorting button should appear at the right top as proposed > in the screenshot > bellow. > !Screenshot from 2017-06-23 12-44-19.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-493) Repayment method by Post Dated Checks
[ https://issues.apache.org/jira/browse/FINERACT-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-493: -- Labels: feature gsoc p2 (was: feature p2) > Repayment method by Post Dated Checks > - > > Key: FINERACT-493 > URL: https://issues.apache.org/jira/browse/FINERACT-493 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan >Reporter: Justine Nam >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: feature, gsoc, p2 > > Repayment by Post Dated Checks > In Current updated MifosX, there is no convenient features for Post dated > checks Repayment. > Our company normally require Post Dated Checks to the client as repayment > method when their loan is approved. > If the term is 6 month, we asked them to provide 6 pcs Post Dated Checks for > repayment. > So, If it's possiblewhen we create the loan application for > individuals, make one more optional procedures to encode(input) the Post > Dated Checks details during Disburse Loan application > Normally, Check numbers are increased by 1... > example) > Name of BankDue Date Account No. Check No. Amount > Citi Bank 1/1/2017 230016 *11 1000 > Citi Bank 1/2/2017 230016*12 1000 > Citi Bank 1/3/2017 230016 *13 1000 > Citi Bank 1/4/2017 230016 *14 1000 > Citi Bank 1/5/2017 230016 *15 1000 > Citi Bank 1/6/2017230016*16 1000 > So, When we input the Postdated checks details. > 1. It should automatically generate the rows based on the term(get this data > from Loan application) > - if the term is 6 months, it should generate 6 rows for encoding of Checks > Info. > 2. For Check No. field, when we input first check No. , it should > automatically generate Check no. increased by 1 > 3. This data table is linked with Repayment Schedule. > When we see the repayment schedule , Check No. must be showed (If that data > is encoded) > 4. when we see the collection sheet, those information(like check no, bank > name) will automatically appear and can be edited as well...Also, It can be > cleared(make payment) in Collection Sheet > In current MifosX system, we need to encode one by one whenever there is > due-payment. > Collection Sheet -> Add payment detail -> input the Check detail. > If we have a few post dated checks, it's ok .But If there are many checks > to encode the datails for checks.this is time consuming works. > I hope someone work on this matter.. > thank you -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-461) Need of setting Minimum, Default and Maximum values of principal values as zero in loan product level
[ https://issues.apache.org/jira/browse/FINERACT-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-461: -- Labels: gsoc p2 (was: gsoc2017 p2) > Need of setting Minimum, Default and Maximum values of principal values as > zero in loan product level > - > > Key: FINERACT-461 > URL: https://issues.apache.org/jira/browse/FINERACT-461 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p2 > > Currently(with latest Mifos 12.01.RELEASE), you can set Principal > values(min,default,max) greater than zero. The zero values for principal > value s in product level should be acceptable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-525) Search for a Member by ID when adding to Group
[ https://issues.apache.org/jira/browse/FINERACT-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-525: -- Labels: gsoc p2 (was: p2) > Search for a Member by ID when adding to Group > -- > > Key: FINERACT-525 > URL: https://issues.apache.org/jira/browse/FINERACT-525 > Project: Apache Fineract > Issue Type: Improvement > Components: Client, Groups >Reporter: May Myint >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p2 > > When associating new Clients to a Group through Manage Members, clients can > only be searched by name. The issue is that it is possible for there to be > many clients with the same name. Thus the user will have to select the > clients one by one to get the right person. > Allowing for the client to be searched by Client # would be more efficient. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-516) Add current password field to prevent unauthorized users from changing password of the current user #2428
[ https://issues.apache.org/jira/browse/FINERACT-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-516: -- Labels: gsoc p2 (was: p2) > Add current password field to prevent unauthorized users from changing > password of the current user #2428 > - > > Key: FINERACT-516 > URL: https://issues.apache.org/jira/browse/FINERACT-516 > Project: Apache Fineract > Issue Type: Improvement > Components: User Management >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > Attachments: 29419719-81d3d36a-8378-11e7-9ad4-20074c6627cd.png > > > Reported by Nenge1 > Link, > Mifos dropdown->profile>change password (check the screenshot) > Allowing user to enter only new password increase vulnerability because the > username is visible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-519) Ability to delete an employee
[ https://issues.apache.org/jira/browse/FINERACT-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-519: -- Labels: gsoc p2 (was: p2) > Ability to delete an employee > - > > Key: FINERACT-519 > URL: https://issues.apache.org/jira/browse/FINERACT-519 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization, User Management >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > > Reported by [~mexina], > For now when you create an employee through navigating Admin -> Organization > -> Manage Employees > The employee is created and there is only the option to edit him/her. > What if an employee leaves the organization? there should be also the button > to delete him. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-500) If holiday is defined and active for specific date or specific date range , application should not allow to define another holiday for the same date or date range
[ https://issues.apache.org/jira/browse/FINERACT-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-500: -- Labels: gsoc p2 (was: p2) > If holiday is defined and active for specific date or specific date range , > application should not allow to define another holiday for the same date or > date range > -- > > Key: FINERACT-500 > URL: https://issues.apache.org/jira/browse/FINERACT-500 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Minor > Labels: gsoc, p2 > > Presently the application is allowing to define two holidays for same date. > The validation error should be thrown -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-522) System ignore cases in username field in the login page
[ https://issues.apache.org/jira/browse/FINERACT-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-522: -- Labels: gsoc p2 (was: p2) > System ignore cases in username field in the login page > --- > > Key: FINERACT-522 > URL: https://issues.apache.org/jira/browse/FINERACT-522 > Project: Apache Fineract > Issue Type: Improvement > Components: User Management >Reporter: Nenge Masoya >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p2 > > * Try to login in the system > * For this case, username: mifos and password: password. The system allow > username: MIFOS as valid username. > * In my suggestion, It is not a good practice as this is a credential, not > the name of the user. Thus, the system should test the exact username without > ignoring cases -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-502) 'Working Days' has higher preference over holidays
[ https://issues.apache.org/jira/browse/FINERACT-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-502: -- Labels: gsoc p2 (was: p2) > 'Working Days' has higher preference over holidays > -- > > Key: FINERACT-502 > URL: https://issues.apache.org/jira/browse/FINERACT-502 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: gsoc, p2 > > In working days(Organization>Working Days) , define Sunday as non-working day > and payment due for non working days move to next working day or previous > working day. > Then define Sunday as 'holiday' (Organization>Manage Holidays) and move > repayments to next due date. As expected, repayment schedule for that day > should be moved next due date extending repayment schedule, but here , it is > moving to next workng day(as defined in working days) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-537) Audit log in and log out
[ https://issues.apache.org/jira/browse/FINERACT-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-537: -- Labels: gsoc p2 (was: gci2017 p2) > Audit log in and log out > > > Key: FINERACT-537 > URL: https://issues.apache.org/jira/browse/FINERACT-537 > Project: Apache Fineract > Issue Type: Improvement > Components: User Management >Affects Versions: 1.0.0 >Reporter: thynn win >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > > Currently there is an audit table and code base for logging other activities > but sign in and sign out. > We have had a couple of clients requesting audit for who is currently logged > in or at least to be able to view who logged in and logged out when. > Acceptance criteria: > Whenever a user login or logout, an entry should be made to audit table with > timestamp and username. It'd be great if you can record IP address also. -- 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: -- Labels: gsoc p2 (was: p2) > 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.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-542) Add to dashboard - Outstanding Amount of Loans
[ https://issues.apache.org/jira/browse/FINERACT-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-542: -- Labels: dashboard gsoc p2 (was: dashboard gci2017 p2) > Add to dashboard - Outstanding Amount of Loans > -- > > Key: FINERACT-542 > URL: https://issues.apache.org/jira/browse/FINERACT-542 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: May Myint >Assignee: Markus Geiss >Priority: Minor > Labels: dashboard, gsoc, p2 > Attachments: MifosX-Dashboard-Spec.docx > > > Add 'Outstanding Amount of Loans' widget to dashboard. > Description: It will display total outstanding principal amount of loans. > Data will be presented in bar chart. X-axis will show time scale. Y-axis will > show the outstanding amount (in number). It needs to show the amount value > label on each bar for easier reading. Data will be presented for selected > branch and time scale > Presentation: Data displays for different branches. Data displays in > different time scales (daily, weekly, monthly). Data displays in bar chart. > X-axis is for time scale. Y-axis is for amount. Information and data will be > presented in the form of charts and graphs. > User permission: The display of data is based on user login id. The dashboard > contents will be unique to each user. What will you see depends on job > responsibilities and user’s recent/frequent activities. > Specification sheet attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-540) Add to dashboard - Saving balance
[ https://issues.apache.org/jira/browse/FINERACT-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-540: -- Labels: dashboard gsoc p2 (was: dashboard gci2017 p2) > Add to dashboard - Saving balance > - > > Key: FINERACT-540 > URL: https://issues.apache.org/jira/browse/FINERACT-540 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: May Myint >Assignee: Markus Geiss >Priority: Minor > Labels: dashboard, gsoc, p2 > Attachments: MifosX-Dashboard-Spec.docx > > > Add Saving Balance widget to dashboard. > Description: Display total savings balance. Data will be presented in bar > chart. X-axis will show time scale. Y-axis will show amount (in number). Data > will be presented based on selected branch and time scale. It needs to show > the amount value labels (in number) on each bar for easy reading. > Presentation: Data displays for different branches. Data displays in > different time scales (daily, weekly, monthly). Data displays in bar chart. > X-axis is for time scale. Y-axis is for amount. Information and data will be > presented in the form of charts and graphs. > User permission: The display of data is based on user login id. The dashboard > contents will be unique to each user. What will you see depends on job > responsibilities and user’s recent/frequent activities. > Specification sheet attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-541) Add to dashboard - Number of active clients
[ https://issues.apache.org/jira/browse/FINERACT-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-541: -- Labels: dashboard gsoc p2 (was: dashboard gci2017 p2) > Add to dashboard - Number of active clients > --- > > Key: FINERACT-541 > URL: https://issues.apache.org/jira/browse/FINERACT-541 > Project: Apache Fineract > Issue Type: Improvement > Components: Client >Reporter: May Myint >Assignee: Markus Geiss >Priority: Minor > Labels: dashboard, gsoc, p2 > Attachments: MifosX-Dashboard-Spec.docx > > > Add 'Number of active clients' widget to dashboard. > Description: It will display total number of active clients. Data will be > presented in bar chart. X-axis will show time scale. Y-axis will show the > number of clients. Based on selected branch and time scale, data will be > presented with labels on each bar. > Presentation: Data displays for different branches. Data displays in > different time scales (daily, weekly, monthly). Data displays in bar chart. > X-axis is for time scale. Y-axis is for amount. Information and data will be > presented in the form of charts and graphs. > User permission: The display of data is based on user login id. The dashboard > contents will be unique to each user. What will you see depends on job > responsibilities and user’s recent/frequent activities. > Specification sheet attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-551) Once holiday is deleted it should not be displayed on holidays list even with 'Deleted' Status
[ https://issues.apache.org/jira/browse/FINERACT-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-551: -- Labels: gsoc p2 (was: GCI2017 p2) > Once holiday is deleted it should not be displayed on holidays list even with > 'Deleted' Status > -- > > Key: FINERACT-551 > URL: https://issues.apache.org/jira/browse/FINERACT-551 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: gsoc, p2 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-543) Edit Client Signature
[ https://issues.apache.org/jira/browse/FINERACT-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-543: -- Labels: gsoc p2 (was: gci2017 p2) > Edit Client Signature > - > > Key: FINERACT-543 > URL: https://issues.apache.org/jira/browse/FINERACT-543 > Project: Apache Fineract > Issue Type: New Feature > Components: Client >Reporter: Mexina Daniel >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > > As in client image were you can upload the image and come back to replace it > by uploading another one when you want, i would suggest to have the same > functionality in client signature. > When client signature is uploaded, the system to allow the signature to be > replaced with another in case it was wrong signature uploaded. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-544) Delete Client Signature
[ https://issues.apache.org/jira/browse/FINERACT-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-544: -- Labels: gsoc p2 (was: gci2017 p2) > Delete Client Signature > --- > > Key: FINERACT-544 > URL: https://issues.apache.org/jira/browse/FINERACT-544 > Project: Apache Fineract > Issue Type: New Feature > Components: Client >Reporter: Mexina Daniel >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > > As in client image were you can upload the image and delete it when you want > to remove it, i would suggest to have the same functionality in client > signature. > When client signature is uploaded, the system should allow the signature to > be deleted -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-579) Template - improvement
[ https://issues.apache.org/jira/browse/FINERACT-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-579: -- Labels: gsoc p2 (was: p2) > Template - improvement > --- > > Key: FINERACT-579 > URL: https://issues.apache.org/jira/browse/FINERACT-579 > Project: Apache Fineract > Issue Type: Improvement >Reporter: sangamesh >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > > Template - Should also pickup values provided for created Data tables- With > existing Template feature - It only picks up the existing loan and client > mentioned Should also pickup values provided for created Data table. -- 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: -- Labels: gsoc p1 (was: gsoc2018 p1) > 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 > Fix For: 1.3.0 > > > 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] [Updated] (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:all-tabpanel ] Santosh Math updated FINERACT-229: -- Labels: gsoc p1 (was: gsoc2018 p1) > 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: gsoc, p1 > Fix For: 1.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-26) Allow a Logo (for Organization) to be set, which will be displayed on the header
[ https://issues.apache.org/jira/browse/FINERACT-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-26: - Labels: gsoc p1 (was: gsoc2018 p1) > Allow a Logo (for Organization) to be set, which will be displayed on the > header > > > Key: FINERACT-26 > URL: https://issues.apache.org/jira/browse/FINERACT-26 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Minor > Labels: 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-186) optimising the Post Interest For Savings batch job using pagination
[ https://issues.apache.org/jira/browse/FINERACT-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-186: -- Labels: gsoc p1 (was: gsoc2018 p1) > optimising the Post Interest For Savings batch job using pagination > --- > > Key: FINERACT-186 > URL: https://issues.apache.org/jira/browse/FINERACT-186 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: venkat Ganesh >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p1 > Fix For: 1.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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 ] Santosh Math updated FINERACT-336: -- Labels: gsoc p1 (was: gsoc2018 p1) > 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] [Updated] (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 updated FINERACT-466: -- Labels: gsoc p1 (was: gsoc2018 p1) > 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: Improvement > Components: Charges, Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p1 > Fix For: 1.3.0 > > > 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] [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 ] Santosh Math updated FINERACT-348: -- Labels: gsoc p1 (was: gsoc2018 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, p1 > Fix For: 1.3.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-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: -- Labels: gsoc p1 (was: gsoc2018 p1) > Savings overdraft fee with charge time type 'overdraft fee' and charge > calculation '%amount' is not working > --- > > Key: FINERACT-478 > URL: https://issues.apache.org/jira/browse/FINERACT-478 > Project: Apache Fineract > Issue Type: 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] [Updated] (FINERACT-504) Support of rescheduling of loan for the loan products with Interest Recalculation enabled
[ https://issues.apache.org/jira/browse/FINERACT-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-504: -- Labels: gsoc p1 (was: gsoc2018 p1) > Support of rescheduling of loan for the loan products with Interest > Recalculation enabled > - > > Key: FINERACT-504 > URL: https://issues.apache.org/jira/browse/FINERACT-504 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p1 > Fix For: 1.3.0 > > > Currently loans with interest recalculation enabled, can not be rescheduled. > The support for the same needed in near future. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-416) Interest to be calculated for the whole loan term given
[ https://issues.apache.org/jira/browse/FINERACT-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-416: -- Labels: gsoc p1 (was: gsoc2018 p1) > Interest to be calculated for the whole loan term given > --- > > Key: FINERACT-416 > URL: https://issues.apache.org/jira/browse/FINERACT-416 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Mexina Daniel >Assignee: Markus Geiss >Priority: Critical > Labels: gsoc, p1 > Fix For: 1.3.0 > > > As for some of the MFI practise here in our country, they specify the > interest for the whole loan term given, i.e their loan product have the > interest for the whole loan term regardless of the frequency of repayment () > To accomplish this in mifos, a user has to do calculation of finding an > interest of a month/year with respect of the loan term of that specific > client. This is a very tiresome work as for a day a user can have apply many > loans and the task of calculation make the work even harder. > I was suggesting improvement in the loan product, to be able to allow the > interest rate of the whole loan term. > Example: > Loan product - Development Loan > Amount - Min: 100,000, Max:1,000,000 > Interest - 20% > Loan term - From 3months to 6months > -- This means the interest given is for any loan term the client will want to > take the loan. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-535) Allow the same name of teller if its from different branchs
[ https://issues.apache.org/jira/browse/FINERACT-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-535: -- Labels: features gsoc p1 (was: features gsoc2018 p1) > Allow the same name of teller if its from different branchs > --- > > Key: FINERACT-535 > URL: https://issues.apache.org/jira/browse/FINERACT-535 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Reporter: Mexina Daniel >Assignee: Markus Geiss >Priority: Major > Labels: features, gsoc, p1 > Fix For: 1.3.0 > > > For now when you create a teller with the name which already exist even from > another branch it gives an error of duplicate name > Think of the institution which have the same format of naming its tellers > like Teller1, Teller2, etc > and it has two branches. > The system should allow to create Teller1 of branch1 and Teller1 of branch2. -- 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 ] Santosh Math updated FINERACT-528: -- Labels: gsoc p1 (was: gsoc2018 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: gsoc, p1 > Fix For: 1.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-513) Reverse Overdue Charges Application
[ https://issues.apache.org/jira/browse/FINERACT-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-513: -- Labels: gsoc p1 (was: gsoc2018 p1) > Reverse Overdue Charges Application > --- > > Key: FINERACT-513 > URL: https://issues.apache.org/jira/browse/FINERACT-513 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Loan, System >Affects Versions: 1.0.0 >Reporter: Adriana Pinto >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p1 > Fix For: 1.3.0 > > Attachments: FINERACT-513.pdf > > > We've been working on having a complete functionality of our approach, but we > got an issue at the moment of applying overdue charges when running the job: > Is there any workaround to reverse the overdue charges application? > This is necessary, because the overdue charges are being applied daily, but > if the repayment is made before applying the charges, but it is not > registered at the system, we need to reverse the calculation and "remove" > this charges from the final outstanding. > +*Current Business behaviour*+: When the client makes a repayment, it might > not be registered in the system until some days or weeks later, then the > overdue charges if are applied daily, have to be reversed from de current > date until the date the repayment was done. > Then, it is the approach we are looking for. > We had already figured out the "Waiving charges" process, but it would work > better if there was a job doing the contrary process of applying overdue > charges, like "Reverse overdue charges" by date or any moment in a specified > time. > **The attachment (FINERACT-513.pdf) shows the funtionality in a more specific > way. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-505) Loan Tranche Details should be captured in Bulk JLG loan application.
[ https://issues.apache.org/jira/browse/FINERACT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-505: -- Labels: gsoc p1 (was: gsoc2018 p1) > 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: gsoc, p1 > Fix For: 1.3.0 > > > Presently, there is no fields to capture multi-tranche details in 'Bulk JLG > loan application' . Therefore, Bulk JLG loan application doesn't support > multi-tranche loan products. The current temperory fix is, the loan products > with multi-tranche aren't displaying in drop-down menu of 'Bulk JLG loan > application'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-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 ] Santosh Math updated FINERACT-536: -- Labels: gsoc p1 (was: gsoc2018 p1) > 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: Markus Geiss >Priority: Minor > Labels: 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] [Updated] (FINERACT-595) Should allow user to specify an account nickname
[ https://issues.apache.org/jira/browse/FINERACT-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-595: -- Labels: Volunteer confirm gsoc patch (was: Volunteer gsoc patch) > Should allow user to specify an account nickname > > > Key: FINERACT-595 > URL: https://issues.apache.org/jira/browse/FINERACT-595 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan, Savings >Affects Versions: 1.1.0 >Reporter: Rajan Maurya >Assignee: Shaik Nazeer Hussain >Priority: Minor > Labels: Volunteer, confirm, gsoc, patch > Fix For: 1.1.0 > > > *Summary:* > For users to be able to quickly identify their accounts when doing transfers > or payments, we should allow them to specify an account nickname. > We would have to decide if the account nickname is just stored locally in the > app on the device or if the account nickname would be stored at the platform > level for Apache Fineract. > Storing it the Apache Fineract level, would allow the user to have account > nickname persist across the mobile and online banking apps. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-595) Should allow user to specify an account nickname
[ https://issues.apache.org/jira/browse/FINERACT-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-595: -- Labels: Volunteer gsoc patch (was: Volunteer gsoc2018 patch) > Should allow user to specify an account nickname > > > Key: FINERACT-595 > URL: https://issues.apache.org/jira/browse/FINERACT-595 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan, Savings >Affects Versions: 1.1.0 >Reporter: Rajan Maurya >Assignee: Shaik Nazeer Hussain >Priority: Minor > Labels: Volunteer, confirm, gsoc, patch > Fix For: 1.1.0 > > > *Summary:* > For users to be able to quickly identify their accounts when doing transfers > or payments, we should allow them to specify an account nickname. > We would have to decide if the account nickname is just stored locally in the > app on the device or if the account nickname would be stored at the platform > level for Apache Fineract. > Storing it the Apache Fineract level, would allow the user to have account > nickname persist across the mobile and online banking apps. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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 ] Santosh Math updated FINERACT-597: -- Labels: gsoc p2 (was: gsoc2018 p2) > 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: Markus Geiss >Priority: Major > Labels: gsoc, p2 > Fix For: 1.3.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-598) Bulk upload codes from file
[ https://issues.apache.org/jira/browse/FINERACT-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-598: -- Labels: confirm gsoc (was: confirm gsoc2018) > Bulk upload codes from file > --- > > Key: FINERACT-598 > URL: https://issues.apache.org/jira/browse/FINERACT-598 > Project: Apache Fineract > Issue Type: Wish >Affects Versions: 1.0.0 >Reporter: Javier Borkenztain >Assignee: Markus Geiss >Priority: Minor > Labels: confirm, gsoc > Attachments: Captura de pantalla 2018-02-05 a la(s) 21.36.13.png > > > As a user with the credentials to configure code names bellow System > Configuration, Below "Manage Codes", sometimes I will need to create a long > table of codes (cities of a country, regions of a country, postal codes, > etc), and doing it one by one is lots of work. > it will be a nice to have feature that allows the user to upload a file that > creates the entire set of codes. A simple CSV file with the four fields > needed for the code creation > * Name > * Description > * Position > * Active -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-604) Support for MySQL 5.7
[ https://issues.apache.org/jira/browse/FINERACT-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-604: -- Labels: gsoc p1 (was: gsoc2018 p1) > Support for MySQL 5.7 > - > > Key: FINERACT-604 > URL: https://issues.apache.org/jira/browse/FINERACT-604 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.0.0 > Environment: MySQL version 5.7.5 or higher >Reporter: Steve Conrad >Assignee: Myrle Krantz >Priority: Major > Labels: gsoc, p1 > Fix For: 1.2.0 > > > Provide support for MySQL 5.7. This includes all migrations scripts, services > code, and reports. The core issue is support for strict mode in MySQL > (ONLY_FULL_GROUP_BY enabled). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-603) GSIM and GLIM support
[ https://issues.apache.org/jira/browse/FINERACT-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-603: -- Labels: gsoc p1 (was: gsoc2018 p1) > GSIM and GLIM support > - > > Key: FINERACT-603 > URL: https://issues.apache.org/jira/browse/FINERACT-603 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan, Savings >Reporter: Edward Cable >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: gsoc, p1 > Fix For: 1.2.0 > > > Support for Group Loans with Individual Monitoring and Group Savings with > Individual Monitoring added by Nikhil Pawar with use cases and support from > iDT Labs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-596) Expose self-service share detail API
[ https://issues.apache.org/jira/browse/FINERACT-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391778#comment-16391778 ] Edward Cable commented on FINERACT-596: --- [~santoshmath] As far as I know, no. > Expose self-service share detail API > - > > Key: FINERACT-596 > URL: https://issues.apache.org/jira/browse/FINERACT-596 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Affects Versions: 1.1.0 >Reporter: Rajan Maurya >Assignee: Markus Geiss >Priority: Minor > Fix For: 1.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINCN-8) Web UI for Microfinance Institutions Practicing Group Lending
[ https://issues.apache.org/jira/browse/FINCN-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391331#comment-16391331 ] Myrle Krantz commented on FINCN-8: -- How does this ticket relate to FINCN-3? > Web UI for Microfinance Institutions Practicing Group Lending > - > > Key: FINCN-8 > URL: https://issues.apache.org/jira/browse/FINCN-8 > Project: Fineract Cloud Native > Issue Type: New Feature >Reporter: Edward Cable >Priority: Major > Labels: gsoc2018 > > While the current Mifos X stack caters to one operational methodology and has > one distinct user interface and navigational flow, Fineract CN and it's > broader applicability enables many different operational workflows to be > supported and will have different flavors of the web UI. > For the brand new Apache Fineract CN architecture, the web UI for the first > use cases has been built out to support a teller-driven credit union > operational methodology. The user interface and navigational flows for such > an operational model is very different from that of a microfinance > institutinon with group and center-based operations whereby the loan officer > travels out to the customers rather than the customer goes to the branch > office. > The UI that will be built out for this project will be very similar to the UI > that was found in the current Gen 2 Mifos X web app as well as the original > Gen 1 web app with support for viewing group and center hierachies, having a > different drilldown navigational flow, etc. > A number of these UI elements will still need the requisite support on the > back-end. > Intern will implement the front-end UI screens for the Fineract CN web UI for > the following functionalities and use case: > * Center & Group Creation > * Center Summary and Details Page > * Group Summary and Details Page > * Group/Center Meeting Page > * Group, Center Listing View > * Drilldown navigation via Groups/Centers > * Collection sheet user interface > * Transferring clients between groups > * Group loan creation UI > * Group loan UI -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINCN-8) Web UI for Microfinance Institutions Practicing Group Lending
[ https://issues.apache.org/jira/browse/FINCN-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391323#comment-16391323 ] Myrle Krantz commented on FINCN-8: -- Are the collection sheets paper, or UI? I'm guessing that since the loan officer is traveling to the customers, connectivity will be a problem. If that's true than an offline first approach is needed. Is this assumption correct? Can you provide (attach) examples of collections sheets currently in use? What does it mean for a client to be transferred between groups. What happens with their debt/savings? Can you detail what differentiates a group loan from a credit union loan? As far as the process goes? As far as the information required goes? > Web UI for Microfinance Institutions Practicing Group Lending > - > > Key: FINCN-8 > URL: https://issues.apache.org/jira/browse/FINCN-8 > Project: Fineract Cloud Native > Issue Type: New Feature >Reporter: Edward Cable >Priority: Major > Labels: gsoc2018 > > While the current Mifos X stack caters to one operational methodology and has > one distinct user interface and navigational flow, Fineract CN and it's > broader applicability enables many different operational workflows to be > supported and will have different flavors of the web UI. > For the brand new Apache Fineract CN architecture, the web UI for the first > use cases has been built out to support a teller-driven credit union > operational methodology. The user interface and navigational flows for such > an operational model is very different from that of a microfinance > institutinon with group and center-based operations whereby the loan officer > travels out to the customers rather than the customer goes to the branch > office. > The UI that will be built out for this project will be very similar to the UI > that was found in the current Gen 2 Mifos X web app as well as the original > Gen 1 web app with support for viewing group and center hierachies, having a > different drilldown navigational flow, etc. > A number of these UI elements will still need the requisite support on the > back-end. > Intern will implement the front-end UI screens for the Fineract CN web UI for > the following functionalities and use case: > * Center & Group Creation > * Center Summary and Details Page > * Group Summary and Details Page > * Group/Center Meeting Page > * Group, Center Listing View > * Drilldown navigation via Groups/Centers > * Collection sheet user interface > * Transferring clients between groups > * Group loan creation UI > * Group loan UI -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-26) Allow a Logo (for Organization) to be set, which will be displayed on the header
[ https://issues.apache.org/jira/browse/FINERACT-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-26: - Labels: gsoc2018 p1 (was: p1) > Allow a Logo (for Organization) to be set, which will be displayed on the > header > > > Key: FINERACT-26 > URL: https://issues.apache.org/jira/browse/FINERACT-26 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc2018, 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-186) optimising the Post Interest For Savings batch job using pagination
[ https://issues.apache.org/jira/browse/FINERACT-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-186: -- Labels: gsoc2018 p1 (was: p1) > optimising the Post Interest For Savings batch job using pagination > --- > > Key: FINERACT-186 > URL: https://issues.apache.org/jira/browse/FINERACT-186 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: venkat Ganesh >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc2018, p1 > Fix For: 1.3.0 > > -- 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: -- Labels: gsoc2018 p1 (was: p1) > 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: gsoc2018, p1 > Fix For: 1.3.0 > > > 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)
