[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 ] Edward Cable updated FINERACT-431: -- Fix Version/s: 1.2.0 > 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: Mexina Daniel >Priority: Minor > Labels: gsoc, p2 > Fix For: 1.2.0 > > > 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-652) Deliver status is not getting updated to 'Delivered' (status:300) even message is delivered to the mobile
[ https://issues.apache.org/jira/browse/FINERACT-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-652: -- Issue Type: Bug (was: Improvement) > Deliver status is not getting updated to 'Delivered' (status:300) even > message is delivered to the mobile > -- > > Key: FINERACT-652 > URL: https://issues.apache.org/jira/browse/FINERACT-652 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: p1 > Fix For: 1.2.0 > > > The following are the sms status: > Pending: 100 > Waiting for Delivery Report: 150 > Sent sms: 200 > Delivered sms: 300 > Failed sms: 400 > Even sms is delivered to given mobile number the status in the database is > not getting updating from 150 to 300. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-643) Journal Entries are not filterable by type of entry: system
[ https://issues.apache.org/jira/browse/FINERACT-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-643: -- Fix Version/s: (was: 1.2.0) 1.3.0 > Journal Entries are not filterable by type of entry: system > --- > > Key: FINERACT-643 > URL: https://issues.apache.org/jira/browse/FINERACT-643 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Major > Labels: gsoc, p1 > Fix For: 1.3.0 > > > Related Front -End Issue: > https://github.com/openMF/web-app/issues/236 > As a developer, I am unable to implement the filter for Journal Entries by > type of entry: system, as the only parameter available to filter entries by > type is manualEntriesOnly which filters manual entries (as clear from its > name). There is no way to filter system entries from server-side. > (similar issue in community-app) > Due to a large number of entries in database (over 8), its essential to > implement it from server-side because the default implementation of sending a > HTTP request to get all the entries at once and implementing the logic on > client-side will be too costly for people with slow internet connections. > > Refer: [https://demo.openmf.org/api-docs/apiLive.htm#journalentries_list] > Expected Behaviour: > Journal Entries should be filterable by type of entry: system apart from the > manual as well from the server-side so that it can be implemented on the > client side. > h2. Actual Behaviour > Journal Entries are not filterable by type of entry: system from the > server-side due to which filter by type of entry cannot be implemented > properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-626) MOVING CASH FROM HEAD OFFICE ACCOUNTS TO BRANCHES ACCOUNTS IN MIFOS X 17.07.01
[ https://issues.apache.org/jira/browse/FINERACT-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-626: -- Fix Version/s: (was: 1.2.0) 1.3.0 > MOVING CASH FROM HEAD OFFICE ACCOUNTS TO BRANCHES ACCOUNTS IN MIFOS X 17.07.01 > -- > > Key: FINERACT-626 > URL: https://issues.apache.org/jira/browse/FINERACT-626 > Project: Apache Fineract > Issue Type: New Feature > Components: Organization, System >Affects Versions: 1.1.0 >Reporter: Jimmy Jubha Mayala >Priority: Major > Labels: gsoc, p2 > Fix For: 1.3.0 > > > We need a feature in Fineract to enhance cash distribution from head office > to branches, for examplE, in our office we have taken a loan from bank and we > want it be distributed into our branches, we are able to inject this loan > into Head office accounts, but how is it going to be sent to branches > accounts? this is where we got stuck since mifos x 17.07.01 we are using does > not have this feature. > We do request any developer to pick this task. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-652) Deliver status is not getting updated to 'Delivered' (status:300) even message is delivered to the mobile
[ https://issues.apache.org/jira/browse/FINERACT-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-652: -- Fix Version/s: (was: 1.2.0) 1.3.0 > Deliver status is not getting updated to 'Delivered' (status:300) even > message is delivered to the mobile > -- > > Key: FINERACT-652 > URL: https://issues.apache.org/jira/browse/FINERACT-652 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: p1 > Fix For: 1.3.0 > > > The following are the sms status: > Pending: 100 > Waiting for Delivery Report: 150 > Sent sms: 200 > Delivered sms: 300 > Failed sms: 400 > Even sms is delivered to given mobile number the status in the database is > not getting updating from 150 to 300. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-647) Allow rescheduling of loan with recalculation of interest enabled
[ https://issues.apache.org/jira/browse/FINERACT-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-647: -- Fix Version/s: (was: 1.2.0) 1.3.0 > Allow rescheduling of loan with recalculation of interest enabled > - > > Key: FINERACT-647 > URL: https://issues.apache.org/jira/browse/FINERACT-647 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.1.0 >Reporter: Mexina Daniel >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > > There is a need of allowing the loan which has enabled interest recalculation > to be rescheduled once needed. > for now the system does not allow that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-632) Description in Saving Product should not be mandatory
[ https://issues.apache.org/jira/browse/FINERACT-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-632: -- Labels: Volunteer gci gsoc p2 (was: Volunteer gsoc p2) > Description in Saving Product should not be mandatory > - > > Key: FINERACT-632 > URL: https://issues.apache.org/jira/browse/FINERACT-632 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.1.0 >Reporter: Mexina Daniel >Priority: Minor > Labels: Volunteer, gci, gsoc, p2 > Fix For: 1.3.0 > > Attachments: Screen Shot 2018-11-16 at 2.57.11 PM.png > > > The is no necessarily of making the description filed of saving product to be > mandatory -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-632) Description in Saving Product should not be mandatory
[ https://issues.apache.org/jira/browse/FINERACT-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-632: -- Attachment: Screen Shot 2018-11-16 at 2.57.11 PM.png > Description in Saving Product should not be mandatory > - > > Key: FINERACT-632 > URL: https://issues.apache.org/jira/browse/FINERACT-632 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.1.0 >Reporter: Mexina Daniel >Priority: Minor > Labels: Volunteer, gsoc, p2 > Fix For: 1.3.0 > > Attachments: Screen Shot 2018-11-16 at 2.57.11 PM.png > > > The is no necessarily of making the description filed of saving product to be > mandatory -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-632) Description in Saving Product should not be mandatory
[ https://issues.apache.org/jira/browse/FINERACT-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-632: -- Fix Version/s: (was: 1.2.0) 1.3.0 > Description in Saving Product should not be mandatory > - > > Key: FINERACT-632 > URL: https://issues.apache.org/jira/browse/FINERACT-632 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.1.0 >Reporter: Mexina Daniel >Priority: Minor > Labels: Volunteer, gsoc, p2 > Fix For: 1.3.0 > > > The is no necessarily of making the description filed of saving product to be > mandatory -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-618) Allow for Submitted On Date to be Edited for Groups
[ https://issues.apache.org/jira/browse/FINERACT-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-618: -- Fix Version/s: (was: 1.2.0) 1.3.0 > Allow for Submitted On Date to be Edited for Groups > --- > > Key: FINERACT-618 > URL: https://issues.apache.org/jira/browse/FINERACT-618 > Project: Apache Fineract > Issue Type: Improvement > Components: Groups >Affects Versions: 1.1.0 >Reporter: Edward Cable >Assignee: Shruthi M R >Priority: Minor > Labels: GCI, Newbie, Volunteer, beginner, gsoc, p1 > Fix For: 1.3.0 > > > Just as one can edit the submitted on date for a client after it's been > created, so should a user be able to edit the submitted on date for a group > after it's been created. > Corresponding UI ticket on Github Issues for Mifos X Web App. > As requested by Diane on the mailing list at -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-618) Allow for Submitted On Date to be Edited for Groups
[ https://issues.apache.org/jira/browse/FINERACT-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-618: -- Labels: GCI Newbie Volunteer beginner gsoc p1 (was: Newbie Volunteer beginner gsoc p1) > Allow for Submitted On Date to be Edited for Groups > --- > > Key: FINERACT-618 > URL: https://issues.apache.org/jira/browse/FINERACT-618 > Project: Apache Fineract > Issue Type: Improvement > Components: Groups >Affects Versions: 1.1.0 >Reporter: Edward Cable >Assignee: Shruthi M R >Priority: Minor > Labels: GCI, Newbie, Volunteer, beginner, gsoc, p1 > Fix For: 1.2.0 > > > Just as one can edit the submitted on date for a client after it's been > created, so should a user be able to edit the submitted on date for a group > after it's been created. > Corresponding UI ticket on Github Issues for Mifos X Web App. > As requested by Diane on the mailing list at -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-614) Creation of sub rates
[ https://issues.apache.org/jira/browse/FINERACT-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-614: -- Fix Version/s: (was: 1.2.0) 1.3.0 > Creation of sub rates > - > > Key: FINERACT-614 > URL: https://issues.apache.org/jira/browse/FINERACT-614 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.1.0 >Reporter: Angel Cajas >Priority: Minor > Labels: p2 > Fix For: 1.3.0 > > > Nominal interest rate for loans can be composed of previously defined > interest rates, When a new loan product or loan account is created you can > choose which rates should apply for the loan. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-664) Unable to Approve Share account application which is already submitted
[ https://issues.apache.org/jira/browse/FINERACT-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R reassigned FINERACT-664: - Assignee: Santosh Math (was: Shruthi M R) > Unable to Approve Share account application which is already submitted > -- > > Key: FINERACT-664 > URL: https://issues.apache.org/jira/browse/FINERACT-664 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Santosh Math >Priority: Blocker > Labels: p1 > Fix For: 1.2.0 > > > Try to approve following share accounts: > https://staging.openmf.org/#/viewshareaccount/30 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FINERACT-664) Unable to Approve Share account application which is already submitted
[ https://issues.apache.org/jira/browse/FINERACT-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R resolved FINERACT-664. --- Resolution: Fixed > Unable to Approve Share account application which is already submitted > -- > > Key: FINERACT-664 > URL: https://issues.apache.org/jira/browse/FINERACT-664 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Blocker > Labels: p1 > Fix For: 1.2.0 > > > Try to approve following share accounts: > https://staging.openmf.org/#/viewshareaccount/30 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-664) Unable to Approve Share account application which is already submitted
[ https://issues.apache.org/jira/browse/FINERACT-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689426#comment-16689426 ] Shruthi M R commented on FINERACT-664: --- [~santoshmath] Considering this particular case, account number 25 is issued with 25 shares already, and you are trying to issue 50 more shares. But total shares that can be issued are only 50. So the case you are checking is on wrong data. > Unable to Approve Share account application which is already submitted > -- > > Key: FINERACT-664 > URL: https://issues.apache.org/jira/browse/FINERACT-664 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Blocker > Labels: p1 > Fix For: 1.2.0 > > > Try to approve following share accounts: > https://staging.openmf.org/#/viewshareaccount/30 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-663) In share application clicking on Add button for 'Market Price Period' Moving Wizard to the next step
[ https://issues.apache.org/jira/browse/FINERACT-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689415#comment-16689415 ] Shruthi M R commented on FINERACT-663: --- [~santoshmath] I think you are referring create share product. I am unable to find market price step in create share account. In any case it is a front end issue. kindly close this ticket and raise one in front end. > In share application clicking on Add button for 'Market Price Period' > Moving Wizard to the next step > -- > > Key: FINERACT-663 > URL: https://issues.apache.org/jira/browse/FINERACT-663 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Major > Labels: gci, gsoc, p1 > Fix For: 1.2.0 > > > 1) Take a share application using any share product. > 2) Input all mandatory fields and move until 'Market Price' step . > 3) Click on Add button to add market price > > Control is moving to the next step of the wizard. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-539) Swagger Integration on FINERACT
[ https://issues.apache.org/jira/browse/FINERACT-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R reassigned FINERACT-539: - Assignee: Shruthi M R (was: Shaik Nazeer Hussain) > Swagger Integration on FINERACT > --- > > Key: FINERACT-539 > URL: https://issues.apache.org/jira/browse/FINERACT-539 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Sanyam Goel >Assignee: Shruthi M R >Priority: Major > Labels: GCI, Hacktoberfest > Fix For: 1.2.0 > > > Dynamic Documentation can be done by Annotating Fineract API's and End Points > with some Swagger Annotations > *Google Code In* Tasks are availabe at [https://goo.gl/FWTwc9] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FINERACT-539) Swagger Integration on FINERACT
[ https://issues.apache.org/jira/browse/FINERACT-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R resolved FINERACT-539. --- Resolution: Fixed [~sanyam96] has worked on this feature > Swagger Integration on FINERACT > --- > > Key: FINERACT-539 > URL: https://issues.apache.org/jira/browse/FINERACT-539 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Sanyam Goel >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: GCI, Hacktoberfest > Fix For: 1.2.0 > > > Dynamic Documentation can be done by Annotating Fineract API's and End Points > with some Swagger Annotations > *Google Code In* Tasks are availabe at [https://goo.gl/FWTwc9] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-539) Swagger Integration on FINERACT
[ https://issues.apache.org/jira/browse/FINERACT-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R reassigned FINERACT-539: - Assignee: Shaik Nazeer Hussain (was: Shruthi M R) > Swagger Integration on FINERACT > --- > > Key: FINERACT-539 > URL: https://issues.apache.org/jira/browse/FINERACT-539 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Sanyam Goel >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: GCI, Hacktoberfest > Fix For: 1.2.0 > > > Dynamic Documentation can be done by Annotating Fineract API's and End Points > with some Swagger Annotations > *Google Code In* Tasks are availabe at [https://goo.gl/FWTwc9] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-539) Swagger Integration on FINERACT
[ https://issues.apache.org/jira/browse/FINERACT-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689383#comment-16689383 ] Shruthi M R commented on FINERACT-539: --- [~sanyam96] has worked on this feature. > Swagger Integration on FINERACT > --- > > Key: FINERACT-539 > URL: https://issues.apache.org/jira/browse/FINERACT-539 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Sanyam Goel >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: GCI, Hacktoberfest > Fix For: 1.2.0 > > > Dynamic Documentation can be done by Annotating Fineract API's and End Points > with some Swagger Annotations > *Google Code In* Tasks are availabe at [https://goo.gl/FWTwc9] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (FINERACT-654) Need a new permission for Assign Staff and Unassign Staff for Loans & Savings
[ https://issues.apache.org/jira/browse/FINERACT-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math reopened FINERACT-654: --- > Need a new permission for Assign Staff and Unassign Staff for Loans & Savings > - > > Key: FINERACT-654 > URL: https://issues.apache.org/jira/browse/FINERACT-654 > Project: Apache Fineract > Issue Type: Bug > Components: System >Reporter: Santosh Math >Assignee: Santosh Math >Priority: Major > > If We go to System>Manage Roles and Permissions , There is no choice of > permission for Assign Staff & Unassign Staff under 'Loan Transactions' and > 'Savings Transactions Category'. > Same must be added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-624) Penalties are getting duplicated
[ https://issues.apache.org/jira/browse/FINERACT-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-624. - Resolution: Not A Problem > Penalties are getting duplicated > - > > Key: FINERACT-624 > URL: https://issues.apache.org/jira/browse/FINERACT-624 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Santosh Math >Priority: Critical > Labels: gsoc, p1 > Attachments: penalties duplicated.png > > > For the following loan account the penalties are applied for overdue loans. > After some initial penalties next penalties are getting duplicated (check > 'Charges' tab) > [https://staging.openmf.org/#/viewloanaccount/91] > (mifos/password) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-635) Not able to create new datatable
[ https://issues.apache.org/jira/browse/FINERACT-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-635: -- Fix Version/s: (was: 1.2.0) > Not able to create new datatable > > > Key: FINERACT-635 > URL: https://issues.apache.org/jira/browse/FINERACT-635 > Project: Apache Fineract > Issue Type: Bug > Components: Data Tables >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Blocker > Labels: gsoc, p1 > Attachments: sw.png > > > >Go To Admin>System>Manage Datatables and click on 'Create Datatable. > >Provide any name for data table select application table name as 'Client. > > Provide column name and column type as 'String', and then click on '+' > > button to add. > > Then click on 'Submit' button. > >Throwing validation , 'Required Field' (check screenshot) ..It's always > >expecting one more column to be added > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (FINERACT-635) Not able to create new datatable
[ https://issues.apache.org/jira/browse/FINERACT-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math reopened FINERACT-635: --- > Not able to create new datatable > > > Key: FINERACT-635 > URL: https://issues.apache.org/jira/browse/FINERACT-635 > Project: Apache Fineract > Issue Type: Bug > Components: Data Tables >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Blocker > Labels: gsoc, p1 > Attachments: sw.png > > > >Go To Admin>System>Manage Datatables and click on 'Create Datatable. > >Provide any name for data table select application table name as 'Client. > > Provide column name and column type as 'String', and then click on '+' > > button to add. > > Then click on 'Submit' button. > >Throwing validation , 'Required Field' (check screenshot) ..It's always > >expecting one more column to be added > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-635) Not able to create new datatable
[ https://issues.apache.org/jira/browse/FINERACT-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-635. - Resolution: Invalid > Not able to create new datatable > > > Key: FINERACT-635 > URL: https://issues.apache.org/jira/browse/FINERACT-635 > Project: Apache Fineract > Issue Type: Bug > Components: Data Tables >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Blocker > Labels: gsoc, p1 > Attachments: sw.png > > > >Go To Admin>System>Manage Datatables and click on 'Create Datatable. > >Provide any name for data table select application table name as 'Client. > > Provide column name and column type as 'String', and then click on '+' > > button to add. > > Then click on 'Submit' button. > >Throwing validation , 'Required Field' (check screenshot) ..It's always > >expecting one more column to be added > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-654) Need a new permission for Assign Staff and Unassign Staff for Loans & Savings
[ https://issues.apache.org/jira/browse/FINERACT-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-654: -- Affects Version/s: (was: 1.1.0) > Need a new permission for Assign Staff and Unassign Staff for Loans & Savings > - > > Key: FINERACT-654 > URL: https://issues.apache.org/jira/browse/FINERACT-654 > Project: Apache Fineract > Issue Type: Bug > Components: System >Reporter: Santosh Math >Assignee: Santosh Math >Priority: Major > > If We go to System>Manage Roles and Permissions , There is no choice of > permission for Assign Staff & Unassign Staff under 'Loan Transactions' and > 'Savings Transactions Category'. > Same must be added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-654) Need a new permission for Assign Staff and Unassign Staff for Loans & Savings
[ https://issues.apache.org/jira/browse/FINERACT-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-654. - Resolution: Invalid > Need a new permission for Assign Staff and Unassign Staff for Loans & Savings > - > > Key: FINERACT-654 > URL: https://issues.apache.org/jira/browse/FINERACT-654 > Project: Apache Fineract > Issue Type: Bug > Components: System >Reporter: Santosh Math >Assignee: Santosh Math >Priority: Major > > If We go to System>Manage Roles and Permissions , There is no choice of > permission for Assign Staff & Unassign Staff under 'Loan Transactions' and > 'Savings Transactions Category'. > Same must be added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-654) Need a new permission for Assign Staff and Unassign Staff for Loans & Savings
[ https://issues.apache.org/jira/browse/FINERACT-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-654: -- Fix Version/s: (was: 1.2.0) > Need a new permission for Assign Staff and Unassign Staff for Loans & Savings > - > > Key: FINERACT-654 > URL: https://issues.apache.org/jira/browse/FINERACT-654 > Project: Apache Fineract > Issue Type: Bug > Components: System >Reporter: Santosh Math >Assignee: Santosh Math >Priority: Major > > If We go to System>Manage Roles and Permissions , There is no choice of > permission for Assign Staff & Unassign Staff under 'Loan Transactions' and > 'Savings Transactions Category'. > Same must be added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-635) Not able to create new datatable
[ https://issues.apache.org/jira/browse/FINERACT-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-635: -- Affects Version/s: (was: 1.1.0) > Not able to create new datatable > > > Key: FINERACT-635 > URL: https://issues.apache.org/jira/browse/FINERACT-635 > Project: Apache Fineract > Issue Type: Bug > Components: Data Tables >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Blocker > Labels: gsoc, p1 > Attachments: sw.png > > > >Go To Admin>System>Manage Datatables and click on 'Create Datatable. > >Provide any name for data table select application table name as 'Client. > > Provide column name and column type as 'String', and then click on '+' > > button to add. > > Then click on 'Submit' button. > >Throwing validation , 'Required Field' (check screenshot) ..It's always > >expecting one more column to be added > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-606) Not able to delete groups which are assigned to center
[ https://issues.apache.org/jira/browse/FINERACT-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-606: -- Fix Version/s: (was: 1.2.0) > 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 > Components: Groups >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Major > Labels: p1 > > # 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] [Closed] (FINERACT-606) Not able to delete groups which are assigned to center
[ https://issues.apache.org/jira/browse/FINERACT-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-606. - Resolution: Duplicate > 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 > Components: Groups >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Major > Labels: p1 > > # 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] [Reopened] (FINERACT-606) Not able to delete groups which are assigned to center
[ https://issues.apache.org/jira/browse/FINERACT-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math reopened FINERACT-606: --- > 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 > Components: Groups >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Major > Labels: p1 > > # 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-624) Penalties are getting duplicated
[ https://issues.apache.org/jira/browse/FINERACT-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-624: -- Fix Version/s: (was: 1.2.0) > Penalties are getting duplicated > - > > Key: FINERACT-624 > URL: https://issues.apache.org/jira/browse/FINERACT-624 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Santosh Math >Priority: Critical > Labels: gsoc, p1 > Attachments: penalties duplicated.png > > > For the following loan account the penalties are applied for overdue loans. > After some initial penalties next penalties are getting duplicated (check > 'Charges' tab) > [https://staging.openmf.org/#/viewloanaccount/91] > (mifos/password) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (FINERACT-624) Penalties are getting duplicated
[ https://issues.apache.org/jira/browse/FINERACT-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math reopened FINERACT-624: --- > Penalties are getting duplicated > - > > Key: FINERACT-624 > URL: https://issues.apache.org/jira/browse/FINERACT-624 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Santosh Math >Priority: Critical > Labels: gsoc, p1 > Attachments: penalties duplicated.png > > > For the following loan account the penalties are applied for overdue loans. > After some initial penalties next penalties are getting duplicated (check > 'Charges' tab) > [https://staging.openmf.org/#/viewloanaccount/91] > (mifos/password) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-610) Post Interest As On
[ https://issues.apache.org/jira/browse/FINERACT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-610. - Resolution: Invalid > Post Interest As On > --- > > Key: FINERACT-610 > URL: https://issues.apache.org/jira/browse/FINERACT-610 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: May Myint >Priority: Minor > Labels: saving > > Currently, Post Interest As On is only available when User is given ALL > FUNCTION permission. However, this is needed by many Users who should not be > given the ALL FUNCTION (loan officers etc). This function is used when a > client leaves the MFI and all their Savings are posted up to date and > withdrawn. It would be ideal to have a separate permission setting for this > function. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (FINERACT-610) Post Interest As On
[ https://issues.apache.org/jira/browse/FINERACT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math reopened FINERACT-610: --- > Post Interest As On > --- > > Key: FINERACT-610 > URL: https://issues.apache.org/jira/browse/FINERACT-610 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: May Myint >Priority: Minor > Labels: saving > > Currently, Post Interest As On is only available when User is given ALL > FUNCTION permission. However, this is needed by many Users who should not be > given the ALL FUNCTION (loan officers etc). This function is used when a > client leaves the MFI and all their Savings are posted up to date and > withdrawn. It would be ideal to have a separate permission setting for this > function. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-610) Post Interest As On
[ https://issues.apache.org/jira/browse/FINERACT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-610: -- Fix Version/s: (was: 1.2.0) > Post Interest As On > --- > > Key: FINERACT-610 > URL: https://issues.apache.org/jira/browse/FINERACT-610 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: May Myint >Priority: Minor > Labels: saving > > Currently, Post Interest As On is only available when User is given ALL > FUNCTION permission. However, this is needed by many Users who should not be > given the ALL FUNCTION (loan officers etc). This function is used when a > client leaves the MFI and all their Savings are posted up to date and > withdrawn. It would be ideal to have a separate permission setting for this > function. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (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 reassigned FINERACT-604: - Assignee: Santosh Math (was: Steve Conrad) > 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: Santosh Math >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] [Resolved] (FINERACT-627) ADDING TRANSFER DATE WHEN A CLIENT IS TRANSFERED FROM ONE BRANCH TO ANOTHER
[ https://issues.apache.org/jira/browse/FINERACT-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R resolved FINERACT-627. --- Resolution: Fixed > ADDING TRANSFER DATE WHEN A CLIENT IS TRANSFERED FROM ONE BRANCH TO ANOTHER > --- > > Key: FINERACT-627 > URL: https://issues.apache.org/jira/browse/FINERACT-627 > Project: Apache Fineract > Issue Type: New Feature > Components: Client >Affects Versions: 1.1.0 > Environment: Ubuntu 16 >Reporter: Jimmy Jubha Mayala >Assignee: Shruthi M R >Priority: Major > Labels: easyfix, gsoc, p2 > Fix For: 1.2.0 > > > We need this feature in Mifosx. The current scenario is, when you want to > transfer a client from one branch to another you do not need to choose which > date the transfer was made, Mifos x picks the current date of the transfer. > so for us we find it to be a big need to have a place to select a date when > we are transferring a client from one branch to another. simply because most > of the time our clients transfer are done with back dates. This helps put a > real record concerning a client transfer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-627) ADDING TRANSFER DATE WHEN A CLIENT IS TRANSFERED FROM ONE BRANCH TO ANOTHER
[ https://issues.apache.org/jira/browse/FINERACT-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R reassigned FINERACT-627: - Assignee: Santosh Math (was: Shruthi M R) > ADDING TRANSFER DATE WHEN A CLIENT IS TRANSFERED FROM ONE BRANCH TO ANOTHER > --- > > Key: FINERACT-627 > URL: https://issues.apache.org/jira/browse/FINERACT-627 > Project: Apache Fineract > Issue Type: New Feature > Components: Client >Affects Versions: 1.1.0 > Environment: Ubuntu 16 >Reporter: Jimmy Jubha Mayala >Assignee: Santosh Math >Priority: Major > Labels: easyfix, gsoc, p2 > Fix For: 1.2.0 > > > We need this feature in Mifosx. The current scenario is, when you want to > transfer a client from one branch to another you do not need to choose which > date the transfer was made, Mifos x picks the current date of the transfer. > so for us we find it to be a big need to have a place to select a date when > we are transferring a client from one branch to another. simply because most > of the time our clients transfer are done with back dates. This helps put a > real record concerning a client transfer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-627) ADDING TRANSFER DATE WHEN A CLIENT IS TRANSFERED FROM ONE BRANCH TO ANOTHER
[
https://issues.apache.org/jira/browse/FINERACT-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689219#comment-16689219
]
ASF GitHub Bot commented on FINERACT-627:
-
ShruthiRajaram closed pull request #471: FINERACT-627 back dated client transfer
URL: https://github.com/apache/fineract/pull/471
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/api-docs/apiLive.htm b/api-docs/apiLive.htm
index c182e6588..00751bc2c 100644
--- a/api-docs/apiLive.htm
+++ b/api-docs/apiLive.htm
@@ -5761,7 +5761,7 @@ Update Default Savings Account
Propose a Client Transfer
- Allows you to propose the transfer of a Client to a
different Office.
+ Allows you to propose the transfer of a Client to a
different Office on a specific date, if loan or savings transaction not
present from proposed transfer date to current date.
POST https://Domain
Name/api/v1/clients/{clientId}?command=proposeTransfer
@@ -5769,6 +5769,7 @@ Propose a Client Transfer
Content-Type: application/json
Request Body:
{
+ "transferDate":"28 August 2018",
"destinationOfficeId":"2",
"note":"Client Relocating to Bangalore"
}
diff --git
a/fineract-provider/src/main/java/org/apache/fineract/portfolio/client/api/ClientsApiResource.java
b/fineract-provider/src/main/java/org/apache/fineract/portfolio/client/api/ClientsApiResource.java
index fc8904907..f4f14b206 100644
---
a/fineract-provider/src/main/java/org/apache/fineract/portfolio/client/api/ClientsApiResource.java
+++
b/fineract-provider/src/main/java/org/apache/fineract/portfolio/client/api/ClientsApiResource.java
@@ -21,6 +21,7 @@
import java.io.InputStream;
import java.util.Arrays;
import java.util.Collection;
+import java.util.Date;
import java.util.HashSet;
import java.util.List;
import java.util.Set;
@@ -62,6 +63,7 @@
import
org.apache.fineract.portfolio.loanaccount.guarantor.service.GuarantorReadPlatformService;
import org.apache.fineract.portfolio.savings.data.SavingsAccountData;
import
org.apache.fineract.portfolio.savings.service.SavingsAccountReadPlatformService;
+import org.joda.time.LocalDate;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.context.annotation.Scope;
import org.springframework.stereotype.Component;
@@ -95,10 +97,11 @@ public ClientsApiResource(final PlatformSecurityContext
context, final ClientRea
final AccountDetailsReadPlatformService
accountDetailsReadPlatformService,
final SavingsAccountReadPlatformService
savingsAccountReadPlatformService,
final BulkImportWorkbookPopulatorService
bulkImportWorkbookPopulatorService,
-final BulkImportWorkbookService bulkImportWorkbookService, final
GuarantorReadPlatformService guarantorReadPlatformService) {
-this.context = context;
-this.clientReadPlatformService = readPlatformService;
-this.toApiJsonSerializer = toApiJsonSerializer;
+ final BulkImportWorkbookService
bulkImportWorkbookService,
+ final GuarantorReadPlatformService
guarantorReadPlatformService) {
+ this.context = context;
+ this.clientReadPlatformService = readPlatformService;
+ this.toApiJsonSerializer = toApiJsonSerializer;
this.clientAccountSummaryToApiJsonSerializer =
clientAccountSummaryToApiJsonSerializer;
this.apiRequestParameterHelper = apiRequestParameterHelper;
this.commandsSourceWritePlatformService =
commandsSourceWritePlatformService;
@@ -361,4 +364,16 @@ public String
retrieveObligeeDetails(@PathParam("clientId") final Long clientId,
return this.toApiJsonSerializer.serialize(ObligeeList);
}
+ @Path("{clientId}/transferproposaldate")
+ @Consumes({ MediaType.APPLICATION_JSON })
+ @Produces({ MediaType.APPLICATION_JSON })
+ public String retrieveTransferTemplate(@PathParam("clientId") final
Long clientId, @Context final UriInfo uriInfo) {
+
+
this.context.authenticatedUser().validateHasReadPermission(ClientApiConstants.CLIENT_RESOURCE_NAME);
+ final Date transferDate =
this.clientReadPlatformService.retrieveClientTransferProposalDate(clientId);
+ if (transferDate != null) {
+ return this.toApiJsonSerializer.serialize(new
LocalDate(transferDate));
+ }
+ return this.toApiJsonSerializer.serialize(transferDate);
+ }
}
\ No newline at end of file
diff --git
a/fineract-provider/src/main/java/org/apache/fineract/portfolio
[jira] [Commented] (FINERACT-664) Unable to Approve Share account application which is already submitted
[ https://issues.apache.org/jira/browse/FINERACT-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689174#comment-16689174 ] Santosh Math commented on FINERACT-664: --- [~Shruthi M R], take Share Product Configuration: |*Details*| |Description|fds| |Short name :|sh67| | | |*Items*| |Currency|Indian Rupee| |Decimal Places|2| |Currency in Multiples Of|1| |Total Shares|100| |Total Shares to be Issued|50| |Nominal/Unit Price|15| |Total Shares Capital Value|750| | | |*Settings*| |Shares per Client:|50 ( Min:25 , Max :100 )| |Minimum Active Period|Invalid| |Lock-in Period|Invalid| |Allow dividends for inactive clients|false| | | |*Market Price*| |From Date|Nominal/Unit Price| |01 November 2018|25| In share application, the total shares issued to the client:50 > Unable to Approve Share account application which is already submitted > -- > > Key: FINERACT-664 > URL: https://issues.apache.org/jira/browse/FINERACT-664 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Blocker > Labels: p1 > Fix For: 1.2.0 > > > Try to approve following share accounts: > https://staging.openmf.org/#/viewshareaccount/30 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
