[jira] [Commented] (FINERACT-384) Product Mix - for Saving Accounts
[ https://issues.apache.org/jira/browse/FINERACT-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516722#comment-16516722 ] Sendoro Juma commented on FINERACT-384: --- Hello [~Ippez] Any comments on this issue? > 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] [Commented] (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:comment-tabpanel&focusedCommentId=16516730#comment-16516730 ] Sendoro Juma commented on FINERACT-227: --- Hello [~venkata ganesh] Was this merged? > 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] [Commented] (FINERACT-429) Node aware Scheduler
[
https://issues.apache.org/jira/browse/FINERACT-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516733#comment-16516733
]
Sendoro Juma commented on FINERACT-429:
---
Hello [~kumaranath_fernando]
How far have you gone?
> 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] [Commented] (FINERACT-471) Preview feature for uploaded document
[ https://issues.apache.org/jira/browse/FINERACT-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516737#comment-16516737 ] Sendoro Juma commented on FINERACT-471: --- Dear [~fboniphace] Are you still following this up? > 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] [Commented] (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:comment-tabpanel&focusedCommentId=16516743#comment-16516743 ] Sendoro Juma commented on FINERACT-516: --- Dear [~nikhilpa...@yahoo.in] Any comments on this... > 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] [Commented] (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:comment-tabpanel&focusedCommentId=16516748#comment-16516748 ] Sendoro Juma commented on FINERACT-551: --- Hello [~santoshmath] Can this be closed according to [~mexina] comments? > 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] [Commented] (FINERACT-422) REST API "live" documentation (Using OpenAPI/Swagger)
[ https://issues.apache.org/jira/browse/FINERACT-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516818#comment-16516818 ] Sendoro Juma commented on FINERACT-422: --- Hello [~santoshmath] When issue is duplicate... doesn't need one of to be closed? > REST API "live" documentation (Using OpenAPI/Swagger) > - > > Key: FINERACT-422 > URL: https://issues.apache.org/jira/browse/FINERACT-422 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Edward Cable >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: gsoc2017 > Fix For: 1.2.0 > > > Mifos (Fineract) of course has a documented REST API already. It currently > has two limitations: > It's source is simply a HTML file that is maintained manually in parallel to > the source code which actually defines the REST API, and therefore can be out > of sync > It's not "live", that is one currently has set up a REST tool such as e.g. > Postman & Co. to "explore" it; contrary to the approach you can see e.g. on > the Swagger Petstore example and (increasingly) other sites offering REST > APIs. > The goal of this project is address this by using Swagger (now Open API > Initiative OAI), most probably combined with SpringFox in for Mifos > (Fineract), and replace the current apiLive.htm. > Phase II: once the Swagger live documentation is working it would be > interesting to use the Swagger descriptor to generate client libraries (e. g. > Java, Angular2). Nice to have optional add-on ideas for the end of the > project: Add a paragraph to this new REST API Doc explaining how to easily > import the (latest) Mifos Swagger into Postman, and perhaps add a Run in > Postman button? > Someone suggested a potential alternative to using Swagger & SpringFox may be > to instead use Spring REST Docs; if you feel that is better suite to fulfill > the requirements above, please do feel free to explain this to your mentor > and pursue in that direction. > UPDATE: this idea might be swapped to focus on doing the same task but for > the new forthcoming generation 3 architecture (Apache Fineract 2.0 at > https://github.com/mifosio) > Tasks: > * familiarize yourself with Swagger + SpringFox > * create working v1 code demonstrating feasibility of approach > * propose it to the community (mailing list), and react to feedback > * don't lose any documentation that's already on the current (manual) REST > API doc, maintain it's human readable comments (by moving that into > JavaDoc/annotations in code which SpringFox/Swagger exploit), the "sections", > etc. > See also https://mifosforge.jira.com/browse/MIFOSX-2699 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-531) Issue in Recalculate Interest For Loans JOB
[
https://issues.apache.org/jira/browse/FINERACT-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516819#comment-16516819
]
Sendoro Juma commented on FINERACT-531:
---
Hello [~santoshmath]
As per [~thynn] comment, does it mean we can close this issue?
> Issue in Recalculate Interest For Loans JOB
>
>
> Key: FINERACT-531
> URL: https://issues.apache.org/jira/browse/FINERACT-531
> Project: Apache Fineract
> Issue Type: Bug
> Components: System
>Reporter: Chanda Aparna
>Assignee: Markus Geiss
>Priority: Major
> Attachments: Recalculate Interest For Loans Error Log.png,
> Recalculate Interest For Loans-Job issue.png
>
>
> There is an error In Demo site (https://demo.openmf.org/#/) for "Recalculate
> Interest For Loans" Job. Could you please check it. {color:red}This is
> critical issue and need to be resolved ASAP.{color}
> If we manually run the job in our local system, there is memory leaking and
> CPU is highly consumed because of the issue in"Recalculate Interest For
> Loans" JOB. Not even creating any failure logs to check.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (FINERACT-567) BulkJLG - Allows amount modification, but upon submission it does not take in the changed amount
[ https://issues.apache.org/jira/browse/FINERACT-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516820#comment-16516820 ] Sendoro Juma commented on FINERACT-567: --- Dear [~jpvel] Dear [~mexina] Can this therefore be closed [~santoshmath] > BulkJLG - Allows amount modification, but upon submission it does not take in > the changed amount > > > Key: FINERACT-567 > URL: https://issues.apache.org/jira/browse/FINERACT-567 > Project: Apache Fineract > Issue Type: Bug > Components: Client, Loan >Affects Versions: 1.1.0 >Reporter: Janarthanan Poornavel >Assignee: Markus Geiss >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-560) (Self-service) - Apply for Savings Accounts
[ https://issues.apache.org/jira/browse/FINERACT-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516823#comment-16516823 ] Sendoro Juma commented on FINERACT-560: --- Hello [~fboniphace] What is your comment on this? > (Self-service) - Apply for Savings Accounts > > > Key: FINERACT-560 > URL: https://issues.apache.org/jira/browse/FINERACT-560 > Project: Apache Fineract > Issue Type: Bug > Components: Client, Savings >Affects Versions: 1.0.0 >Reporter: Rajan Maurya >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: api-change, features > Fix For: 1.0.0 > > > As any self-service user can apply for loan and field officer will review the > application and respond accordingly. We were discussing in our mentor meeting > it would be good if the user can apply for a savings account and field > officer will review and rest of things will be same as of loan application. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-38) Period Close feature where inc & exp booked to retained earnings account
[ https://issues.apache.org/jira/browse/FINERACT-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516826#comment-16516826 ] Sendoro Juma commented on FINERACT-38: -- Dear [~avikganguly010] How is it? has it been merged? cc [~santoshmath] > Period Close feature where inc & exp booked to retained earnings account > > > Key: FINERACT-38 > URL: https://issues.apache.org/jira/browse/FINERACT-38 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > > https://mifosforge.jira.com/browse/MIFOSX-2337 > Relates to: https://mifosforge.jira.com/browse/MIFOSX-2288 (see attachments > and narrative) > financial year end to be user definable and to have the full effect of > closing off the year with initialization of the profit and loss account. Year > end process should be run as/when the institution is ready to close their > books and may not necessarily happen exactly > Musoni is implementing and sharing the following: > Ability to close a financial year from an accounting perspective (booking off > income and expense accounts against your retained earnings equity account). > The high-level spec of this feature is: > * When a user performs a financial close period (existing feature) we have > added various parameters to the call that allow you to also book off the > income and expenses generated in that period. > * Once you submit this request the various balances will be pulled out and > the difference between all expenses and income accounts will be booked off > against a (specified) equity account. > * The journal entry that is generated to perform this booking will be stored > with the close period so that it can be reversed again if a close period is > reopened. > * There is a preview/template API endpoint that allows you to preview the > booking that is going to be performed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-567) BulkJLG - Allows amount modification, but upon submission it does not take in the changed amount
[ https://issues.apache.org/jira/browse/FINERACT-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516827#comment-16516827 ] Santosh Math commented on FINERACT-567: --- [~edcable], please close this issue. > BulkJLG - Allows amount modification, but upon submission it does not take in > the changed amount > > > Key: FINERACT-567 > URL: https://issues.apache.org/jira/browse/FINERACT-567 > Project: Apache Fineract > Issue Type: Bug > Components: Client, Loan >Affects Versions: 1.1.0 >Reporter: Janarthanan Poornavel >Assignee: Markus Geiss >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-72) Speed up the retrieval of journal entries when "transactionDetails" is set to true
[ https://issues.apache.org/jira/browse/FINERACT-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516831#comment-16516831 ] Sendoro Juma commented on FINERACT-72: -- Hello Colleagues, How far has this great work done gone? cc [~santoshmath] > Speed up the retrieval of journal entries when "transactionDetails" is set to > true > -- > > Key: FINERACT-72 > URL: https://issues.apache.org/jira/browse/FINERACT-72 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Emmanuel Nnaa >Assignee: Markus Geiss >Priority: Major > > It takes a little over 3 minutes to retrieve about 360 journal entries if the > "transactionDetails" parameter is set to true. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-531) Issue in Recalculate Interest For Loans JOB
[
https://issues.apache.org/jira/browse/FINERACT-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516830#comment-16516830
]
Santosh Math commented on FINERACT-531:
---
[~edcable] , please close this issue.
> Issue in Recalculate Interest For Loans JOB
>
>
> Key: FINERACT-531
> URL: https://issues.apache.org/jira/browse/FINERACT-531
> Project: Apache Fineract
> Issue Type: Bug
> Components: System
>Reporter: Chanda Aparna
>Assignee: Markus Geiss
>Priority: Major
> Attachments: Recalculate Interest For Loans Error Log.png,
> Recalculate Interest For Loans-Job issue.png
>
>
> There is an error In Demo site (https://demo.openmf.org/#/) for "Recalculate
> Interest For Loans" Job. Could you please check it. {color:red}This is
> critical issue and need to be resolved ASAP.{color}
> If we manually run the job in our local system, there is memory leaking and
> CPU is highly consumed because of the issue in"Recalculate Interest For
> Loans" JOB. Not even creating any failure logs to check.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (FINERACT-46) Throw an exception if staff to be deactivated is attached to an entity with status enum id not equal to 600
[ https://issues.apache.org/jira/browse/FINERACT-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516833#comment-16516833 ] Sendoro Juma commented on FINERACT-46: -- Hello [~santoshmath] Is this still pending or deserve closure? > Throw an exception if staff to be deactivated is attached to an entity with > status enum id not equal to 600 > --- > > Key: FINERACT-46 > URL: https://issues.apache.org/jira/browse/FINERACT-46 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Emmanuel Nnaa >Assignee: Markus Geiss >Priority: Major > > Throw an exception if staff to be deactivated is attached to an entity with > status enum id not equal to 600. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-422) REST API "live" documentation (Using OpenAPI/Swagger)
[ https://issues.apache.org/jira/browse/FINERACT-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516832#comment-16516832 ] Santosh Math commented on FINERACT-422: --- Yes [~sendoro] > REST API "live" documentation (Using OpenAPI/Swagger) > - > > Key: FINERACT-422 > URL: https://issues.apache.org/jira/browse/FINERACT-422 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Edward Cable >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: gsoc2017 > Fix For: 1.2.0 > > > Mifos (Fineract) of course has a documented REST API already. It currently > has two limitations: > It's source is simply a HTML file that is maintained manually in parallel to > the source code which actually defines the REST API, and therefore can be out > of sync > It's not "live", that is one currently has set up a REST tool such as e.g. > Postman & Co. to "explore" it; contrary to the approach you can see e.g. on > the Swagger Petstore example and (increasingly) other sites offering REST > APIs. > The goal of this project is address this by using Swagger (now Open API > Initiative OAI), most probably combined with SpringFox in for Mifos > (Fineract), and replace the current apiLive.htm. > Phase II: once the Swagger live documentation is working it would be > interesting to use the Swagger descriptor to generate client libraries (e. g. > Java, Angular2). Nice to have optional add-on ideas for the end of the > project: Add a paragraph to this new REST API Doc explaining how to easily > import the (latest) Mifos Swagger into Postman, and perhaps add a Run in > Postman button? > Someone suggested a potential alternative to using Swagger & SpringFox may be > to instead use Spring REST Docs; if you feel that is better suite to fulfill > the requirements above, please do feel free to explain this to your mentor > and pursue in that direction. > UPDATE: this idea might be swapped to focus on doing the same task but for > the new forthcoming generation 3 architecture (Apache Fineract 2.0 at > https://github.com/mifosio) > Tasks: > * familiarize yourself with Swagger + SpringFox > * create working v1 code demonstrating feasibility of approach > * propose it to the community (mailing list), and react to feedback > * don't lose any documentation that's already on the current (manual) REST > API doc, maintain it's human readable comments (by moving that into > JavaDoc/annotations in code which SpringFox/Swagger exploit), the "sections", > etc. > See also https://mifosforge.jira.com/browse/MIFOSX-2699 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16516836#comment-16516836 ] Santosh Math commented on FINERACT-551: --- [~edcable] , please close this issue. > 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] [Issue Comment Deleted] (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: -- Comment: was deleted (was: [~edcable] , please close this issue. ) > 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] [Closed] (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 closed FINERACT-551. - Resolution: Fixed > 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] [Commented] (FINERACT-520) The field for "is staff" in the client creation does not store data
[ https://issues.apache.org/jira/browse/FINERACT-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516837#comment-16516837 ] Sendoro Juma commented on FINERACT-520: --- Hello [~mexina] [~Ippez] Is there a chance that [~santoshmath] comment was taken care? > The field for "is staff" in the client creation does not store data > > > Key: FINERACT-520 > URL: https://issues.apache.org/jira/browse/FINERACT-520 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Mexina Daniel >Assignee: Markus Geiss >Priority: Major > Labels: client, p2 > > When you create a client and select the field "is staff", it is selected but > after submission and come again to edit, you find the field not selected, > which shows the value was not stored. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-46) Throw an exception if staff to be deactivated is attached to an entity with status enum id not equal to 600
[ https://issues.apache.org/jira/browse/FINERACT-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516838#comment-16516838 ] Santosh Math commented on FINERACT-46: -- [~edcable] ,please close this issue. > Throw an exception if staff to be deactivated is attached to an entity with > status enum id not equal to 600 > --- > > Key: FINERACT-46 > URL: https://issues.apache.org/jira/browse/FINERACT-46 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Emmanuel Nnaa >Assignee: Markus Geiss >Priority: Major > > Throw an exception if staff to be deactivated is attached to an entity with > status enum id not equal to 600. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-510) report access for self service user
[ https://issues.apache.org/jira/browse/FINERACT-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516841#comment-16516841 ] Sendoro Juma commented on FINERACT-510: --- Dear [~fboniphace] Is it still the case? > report access for self service user > --- > > Key: FINERACT-510 > URL: https://issues.apache.org/jira/browse/FINERACT-510 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Shaik Nazeer Hussain >Assignee: Markus Geiss >Priority: Major > > Self service user should be able to access reports for which they have > permission . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-506) Note at the deposit side
[ https://issues.apache.org/jira/browse/FINERACT-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516842#comment-16516842 ] Sendoro Juma commented on FINERACT-506: --- Dear [~santoshmath] [~Ippez] How far has we gone? > Note at the deposit side > > > Key: FINERACT-506 > URL: https://issues.apache.org/jira/browse/FINERACT-506 > Project: Apache Fineract > Issue Type: New Feature > Components: Savings >Affects Versions: 1.0.0, 1.1.0 > Environment: Windows, software platform >Reporter: Kingsley Adjei Baah >Assignee: Markus Geiss >Priority: Major > Fix For: 1.1.0 > > Original Estimate: 4m > Remaining Estimate: 4m > > I want note to be added to deposit side as in loan repayment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-458) Unable to Modify JLG loan application
[ https://issues.apache.org/jira/browse/FINERACT-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516843#comment-16516843 ] Sendoro Juma commented on FINERACT-458: --- Hello [~santoshmath] Shouldn't we close the issue then? > Unable to Modify JLG loan application > - > > Key: FINERACT-458 > URL: https://issues.apache.org/jira/browse/FINERACT-458 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: p1 > Fix For: 1.0.0 > > > Submit JLG loan for a client. Before approval , click on Modify Application > and then resubmit the loan. Unable to Resubmit, showing the error , "Field is > required". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-484) In Mifos report 'Client Loan Schedule', it does not indicate the amounts paid by the client, only shows the loan balance. Ideally the client would be interested to se
[ https://issues.apache.org/jira/browse/FINERACT-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516844#comment-16516844 ] Sendoro Juma commented on FINERACT-484: --- Dear [~santoshmath] Do we still need to keep this open? Hello [~Alex Mbatha] Is it already resolved on your side? > In Mifos report 'Client Loan Schedule', it does not indicate the amounts paid > by the client, only shows the loan balance. Ideally the client would be > interested to see how much interest and principal has been paid > - > > Key: FINERACT-484 > URL: https://issues.apache.org/jira/browse/FINERACT-484 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Alex Mbatha >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer > Attachments: screenshot-1.png, screenshot-2.png > > > In Mifos report 'Client Loan Schedule', it does not indicate the amounts paid > by the client, only shows the loan balance. Ideally the client would be > interested to see how much interest and principal has been paid. Kindly > include this. > Regards, > Alex -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-257) Scorecards never get returned
[ https://issues.apache.org/jira/browse/FINERACT-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516845#comment-16516845 ] Sendoro Juma commented on FINERACT-257: --- Hello [~edcable] Is this issue still valid or gone with time :) > Scorecards never get returned > - > > Key: FINERACT-257 > URL: https://issues.apache.org/jira/browse/FINERACT-257 > Project: Apache Fineract > Issue Type: Bug > Components: Surveys >Reporter: Markus Geiss >Assignee: Markus Geiss >Priority: Major > Labels: confirm, p2 > > This issue (or a related one) has been a showstopper for Mentor's > International and it's been blocking the work of 4 GSOC interns. The full > background of the issue can be found at this thread: > https://goo.gl/iutqc7 > The gist of it is that responses to the PPI survey can't be retrieved after a > PPI survey has been submitted. This could or could not relate to the > resources being changed from mifos x to apache fineract. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-177) Individual client share in group loan
[ https://issues.apache.org/jira/browse/FINERACT-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516846#comment-16516846 ] Sendoro Juma commented on FINERACT-177: --- Dear [~santoshmath] Is this issue still not merged? > Individual client share in group loan > - > > Key: FINERACT-177 > URL: https://issues.apache.org/jira/browse/FINERACT-177 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Pramod kumar sharma >Assignee: Markus Geiss >Priority: Major > Labels: p2 > > In group loan , track the amount disbursed for individual clients of that > group. > In group of 3 member A, B and C, have taken loan of amount 10$ > If the details is present then track what is the share of A, B and C like. > share of A is 2$, share of B is 3$ and share of C is 5$, B. > Otherwise it will take default null for each client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-130) Abillity to place a client's savings balance on hold
[ https://issues.apache.org/jira/browse/FINERACT-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516847#comment-16516847 ] Sendoro Juma commented on FINERACT-130: --- Hello [~Ippez] How is it now? > Abillity to place a client's savings balance on hold > > > Key: FINERACT-130 > URL: https://issues.apache.org/jira/browse/FINERACT-130 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Edward Cable >Assignee: Markus Geiss >Priority: Major > > As reported by Robert Ippez at https://mifosforge.jira.com/browse/MIFOSX-2509 > This fits into the more broader support of flagging/holding/freezing accounts > for whatever configurable purpose described at: https://goo.gl/AJfSGL > In case a client has died and there are no proper documents to support > transfer of ownership, such accounts should be placed on Hold - no > transactions especially withdrawals should be permitted. > *Hold Reason - (Code & Code values maybe):-* > * Passbook loss > * Illegal entries (Fraud) > * Guarantying a loan > * Compulsory Savings (e.g 20% of Loan Amount) > * Hold for Fixed Deposit etc > *Assumptions* > When Account is on hold, closing of the account should not be permitted. > Available Balance i.e withdraw-able amount should be less than the (Hold > Amount + Min Balance required) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-458) Unable to Modify JLG loan application
[ https://issues.apache.org/jira/browse/FINERACT-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516851#comment-16516851 ] Santosh Math commented on FINERACT-458: --- [~sendoro] , this is reopened. Try to modify loan application here https://staging.openmf.org/#/editloanaccount/93 > Unable to Modify JLG loan application > - > > Key: FINERACT-458 > URL: https://issues.apache.org/jira/browse/FINERACT-458 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: p1 > Fix For: 1.0.0 > > > Submit JLG loan for a client. Before approval , click on Modify Application > and then resubmit the loan. Unable to Resubmit, showing the error , "Field is > required". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-433) Transactions done by cashier for one teller is replicating in other teller with same cashier but different time duration.
[ https://issues.apache.org/jira/browse/FINERACT-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516852#comment-16516852 ] Sendoro Juma commented on FINERACT-433: --- Hello [~santoshmath] Isn't not wise to close the section which is complete and open for only side which is not doesn't making the issue simple may attract volunteer to fix it > Transactions done by cashier for one teller is replicating in other teller > with same cashier but different time duration. > - > > Key: FINERACT-433 > URL: https://issues.apache.org/jira/browse/FINERACT-433 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: gsoc2017, p2 > Fix For: 1.1.0 > > > 1. Create a 'Teller 1' with 'cashier A' with time duration 9am to 1pm. > 2. Create another 'Teller 2', with same 'cashier A' and time duration 2pm to > 5pm > 3. Create an user with employee as 'cashier A' with valid credentials and > permissions. > 4. Login with the credentials of the user for cashier A and do all > disbursements and repayments,etc. for the time duration between 9am to 1pm > >If you check the transactions for Teller 1 and Teller 2, both have same > >transactions though same cashier is assigned with different time duration. > > The transactions done by cashier for specific teller(say Teller 1) at > > specific time duration must be highlighted only to that teller , not in > > other teller . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-167) Implementation of loan foreclosure functionality
[ https://issues.apache.org/jira/browse/FINERACT-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516854#comment-16516854 ] Sendoro Juma commented on FINERACT-167: --- Dear @Vishwa1311 cc [~santoshmath] How far... > Implementation of loan foreclosure functionality > > > Key: FINERACT-167 > URL: https://issues.apache.org/jira/browse/FINERACT-167 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan >Reporter: Vishwanath R >Assignee: Markus Geiss >Priority: Major > Labels: confirm > > On foreclosure of the active loan application, the following things should > happen, > 1) Repay total loan outstanding principal amount. > 2) Repay total Interest amount (accrued and due) till Foreclosure date. > 3) Repay total Fee, Charges or Penalties due, if any till Foreclosure date. > 4) Accounting entries will be made as per product configuration for interest > and loan portfolio payments. > 5) Future installment Interest, Fee, Charge, or Penalty, if any, is waived > off (there won’t be any accounting entries for these transactions). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-415) Loan product should not allow to be created and should throw proper error when mandatory guarantee is not equal to any one of the guarantee(own or guarantor) or sum o
[ https://issues.apache.org/jira/browse/FINERACT-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516865#comment-16516865 ] Sendoro Juma commented on FINERACT-415: --- Hello [~charu12] How far have you gone? > Loan product should not allow to be created and should throw proper error > when mandatory guarantee is not equal to any one of the guarantee(own or > guarantor) or sum of both > > > Key: FINERACT-415 > URL: https://issues.apache.org/jira/browse/FINERACT-415 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc2017, p2 > > While creating loan product, Enable 'Place guarantee funds on Hold'. > There you will see three fileds: > a) Mandatory Guarantee > b) Minimum Guarantee from Own Funds > c) Minimum Guarantee from Guarantor funds. > a should be equal to b+c. > If a=b then 'c' can be blank. > If a=c then 'b' can be blank. > If not, the loan product should not allow to be created and should throw > proper error: "Mandatory Guarantee should be equal to sum of own fund and > guarantor fund OR any one of them". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-419) Non-Person Client codes can not be updated to blank
[ https://issues.apache.org/jira/browse/FINERACT-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516875#comment-16516875 ] Sendoro Juma commented on FINERACT-419: --- Dear [~thisura] and [~tonic...@gmail.com] can you re-test this issue... in case not re-reproduce-able Can we close? cc [~santoshmath] > Non-Person Client codes can not be updated to blank > --- > > Key: FINERACT-419 > URL: https://issues.apache.org/jira/browse/FINERACT-419 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Reporter: Brian C Cooke >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p2 > > Steps to reproduce: > 1. Create a client with Legal Form=Entity and assign this client a value from > the Main Business Line. Save. > 2. Edit this client and try to remove Main Business Line (assign back to > --Select Main Business Line). Save. > 3. Edit again and observe Main Business Line is still assigned. > Seems to be an issue for Client Nonperson domain object, as other drop downs > related to Client domain object are working as expected. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-321) Manual Journal entries should not allowed to reverse after accounting closure is done for that branch
[ https://issues.apache.org/jira/browse/FINERACT-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516879#comment-16516879 ] Sendoro Juma commented on FINERACT-321: --- Hello [~santoshmath] What next with this issue? > Manual Journal entries should not allowed to reverse after accounting closure > is done for that branch > - > > Key: FINERACT-321 > URL: https://issues.apache.org/jira/browse/FINERACT-321 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: p2 > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2519 > Original Description: > 1. Create 2 Chart of accounts with Asset1 and Asset 2. > 2. Click on accounting -> Add Journal entries -> Add one debit and Credit > entries with above entities on 31 January 2016. > 3. Click on Accounting and Click on Closing entries and close the accounting > entries for the organization on 01 February 2016. > 4. Navigate back to the journal entries created and click on reverse entries. > It is allowing to reverse. > > It should not allowed to reverse the entries once Accounting entry is > > closed for the branch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-304) Issue with Maximum allowed outstanding balance in loans
[ https://issues.apache.org/jira/browse/FINERACT-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516880#comment-16516880 ] Sendoro Juma commented on FINERACT-304: --- Dear [~fboniphace] Can you offer to test with latest release and revert back? > Issue with Maximum allowed outstanding balance in loans > --- > > Key: FINERACT-304 > URL: https://issues.apache.org/jira/browse/FINERACT-304 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: beginner, p2 > > Reported by Chandrika at https://mifosforge.jira.com/browse/MIFOSX-2077 > Original Description: > Create a new tranche loan application. > With Principal as 10,000 and maximum allowed outstanding balance as 9,000. > Enter the first tranche with tranche amount as 10,000.Still able to submit. > Tranche amount should not exceed maximum allowed outstanding balance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-298) If more charge is paid in Individual collection sheet is getting collected as advance for the next repayments
[ https://issues.apache.org/jira/browse/FINERACT-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516882#comment-16516882 ] Sendoro Juma commented on FINERACT-298: --- Hello [~fboniphace] Can you test on latest version and revert back/ > If more charge is paid in Individual collection sheet is getting collected as > advance for the next repayments > - > > Key: FINERACT-298 > URL: https://issues.apache.org/jira/browse/FINERACT-298 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: p3 > Attachments: Scr-557.png, Scr-558.png, Scr-559.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1867 > Original Description: > 1. Submit new loan application for a client on 01 November 2014 -> Approve > and Disburse on same date, attache a specified due date charge on 05 November > 2014 and amount as 100. > 2. Run Individual collection sheet in which enter meeting calendar date as 01 > December 2014 -> Click on collection sheet. > 3. In same page total due and charges displayed for 01 December 2014. > 4. In charges field enter amount as 200 (edit 100) and click on submit button. > 5. Navigate back to repayment schedule page of that particular client loan. > In Loan repayment page the amount get repaid on 01 December 2014, but the > charges paid excess (100 more than defined) is getting collected as advance > for the next repayment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-105) Issue related to Change future meeting functionality
[ https://issues.apache.org/jira/browse/FINERACT-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516884#comment-16516884 ] Sendoro Juma commented on FINERACT-105: --- Hello [~fboniphace] Can you re-test and revert back? > Issue related to Change future meeting functionality > > > Key: FINERACT-105 > URL: https://issues.apache.org/jira/browse/FINERACT-105 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Markus Geiss >Priority: Major > Labels: p2 > > 1. If the loan is disbursed on 01 March 2016 and first repayment date is on > 01 April 2016, then it should allow to change future meeting date with in > current system date to 30 April 2016. > > If the future meeting date is set to current system date then first > > repayment should fall on today's date only. > 2. It should not allow to change future meeting date from 01 April 2016 to 01 > May 2016 or beyond that,(beyond immediate next meeting date) and proper error > message should get displayed. > 3. If the future meeting date is changed from 01 April 2016 to today's system > date and again changed to 05 April 2016, then first repayment date should > fall on 05 April 2016. > 4. After change in future meeting date from 01 April 2016 to today's system > date and new loan is disbursed on 01 March 2016 then first repayment date > should fall on today's (current system) date. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FINERACT-321) Manual Journal entries should not allowed to reverse after accounting closure is done for that branch
[ https://issues.apache.org/jira/browse/FINERACT-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math resolved FINERACT-321. --- Resolution: Fixed > Manual Journal entries should not allowed to reverse after accounting closure > is done for that branch > - > > Key: FINERACT-321 > URL: https://issues.apache.org/jira/browse/FINERACT-321 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: p2 > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2519 > Original Description: > 1. Create 2 Chart of accounts with Asset1 and Asset 2. > 2. Click on accounting -> Add Journal entries -> Add one debit and Credit > entries with above entities on 31 January 2016. > 3. Click on Accounting and Click on Closing entries and close the accounting > entries for the organization on 01 February 2016. > 4. Navigate back to the journal entries created and click on reverse entries. > It is allowing to reverse. > > It should not allowed to reverse the entries once Accounting entry is > > closed for the branch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-321) Manual Journal entries should not allowed to reverse after accounting closure is done for that branch
[ https://issues.apache.org/jira/browse/FINERACT-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516891#comment-16516891 ] Santosh Math commented on FINERACT-321: --- [~sendoro], it's yet to be tested. > Manual Journal entries should not allowed to reverse after accounting closure > is done for that branch > - > > Key: FINERACT-321 > URL: https://issues.apache.org/jira/browse/FINERACT-321 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting >Reporter: Santosh Math >Assignee: Santosh Math >Priority: Major > Labels: p2 > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2519 > Original Description: > 1. Create 2 Chart of accounts with Asset1 and Asset 2. > 2. Click on accounting -> Add Journal entries -> Add one debit and Credit > entries with above entities on 31 January 2016. > 3. Click on Accounting and Click on Closing entries and close the accounting > entries for the organization on 01 February 2016. > 4. Navigate back to the journal entries created and click on reverse entries. > It is allowing to reverse. > > It should not allowed to reverse the entries once Accounting entry is > > closed for the branch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-321) Manual Journal entries should not allowed to reverse after accounting closure is done for that branch
[ https://issues.apache.org/jira/browse/FINERACT-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math reassigned FINERACT-321: - Assignee: Santosh Math (was: Markus Geiss) > Manual Journal entries should not allowed to reverse after accounting closure > is done for that branch > - > > Key: FINERACT-321 > URL: https://issues.apache.org/jira/browse/FINERACT-321 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting >Reporter: Santosh Math >Assignee: Santosh Math >Priority: Major > Labels: p2 > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2519 > Original Description: > 1. Create 2 Chart of accounts with Asset1 and Asset 2. > 2. Click on accounting -> Add Journal entries -> Add one debit and Credit > entries with above entities on 31 January 2016. > 3. Click on Accounting and Click on Closing entries and close the accounting > entries for the organization on 01 February 2016. > 4. Navigate back to the journal entries created and click on reverse entries. > It is allowing to reverse. > > It should not allowed to reverse the entries once Accounting entry is > > closed for the branch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-484) In Mifos report 'Client Loan Schedule', it does not indicate the amounts paid by the client, only shows the loan balance. Ideally the client would be interested to se
[ https://issues.apache.org/jira/browse/FINERACT-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516901#comment-16516901 ] Alex Mbatha commented on FINERACT-484: -- Hi Sendoro Juma The issue is resolved on my side. If you can help me with the link for the updated Mifos, I will be quite grateful. Have been asking around with no much help. Regards, Alex > In Mifos report 'Client Loan Schedule', it does not indicate the amounts paid > by the client, only shows the loan balance. Ideally the client would be > interested to see how much interest and principal has been paid > - > > Key: FINERACT-484 > URL: https://issues.apache.org/jira/browse/FINERACT-484 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Alex Mbatha >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer > Attachments: screenshot-1.png, screenshot-2.png > > > In Mifos report 'Client Loan Schedule', it does not indicate the amounts paid > by the client, only shows the loan balance. Ideally the client would be > interested to see how much interest and principal has been paid. Kindly > include this. > Regards, > Alex -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-624) Penalties are getting duplicated
[ https://issues.apache.org/jira/browse/FINERACT-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516954#comment-16516954 ] Sifiso Mtetwa commented on FINERACT-624: I agree with Mexina and Santosh. The penalties are performing normally.This is not a bug. > 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 > Fix For: 1.2.0 > > 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] [Created] (FINERACT-633) New Penalty Charge not appearing in Product dropdown list
Sifiso Mtetwa created FINERACT-633: -- Summary: New Penalty Charge not appearing in Product dropdown list Key: FINERACT-633 URL: https://issues.apache.org/jira/browse/FINERACT-633 Project: Apache Fineract Issue Type: Bug Components: Charges, Loan Affects Versions: 1.2.0 Environment: v18.03.01 Reporter: Sifiso Mtetwa Fix For: 1.3.0 We have been developing a new feature for penalties overdue on maturity [https://mifosforge.jira.com/browse/MIFOSX-2848?filter=-2] We have an issue where after you create the penalty in the charges area with a new charge time type of overdue on maturity and submit it, it does not appear in loan products penalties dropdown box for selection. Wanted to find out which class fetches the penalties that are fetched to appear in this list yet in table m_charges it appears fine. We have added some code in the UI to fetch the required variables but it still does not appear. We can’t proceed beyond this point. Please advise -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-624) Penalties are getting duplicated
[ https://issues.apache.org/jira/browse/FINERACT-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517055#comment-16517055 ] Jimmy Jubha Mayala commented on FINERACT-624: -- Hi Santosh! I think i didn't understand how the penalties were supposed to work, i understand now! You can close the ticket! Thanks all for caring:) > 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 > Fix For: 1.2.0 > > 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] [Commented] (FINERACT-13) Multi-tranche Loan repayment on 2nd tranche incorrect
[ https://issues.apache.org/jira/browse/FINERACT-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517167#comment-16517167 ] Sendoro Juma commented on FINERACT-13: -- Hello [~santoshmath] Agness informs me that she tested in 18.03.01 and she doesn't see a problem can you re-check? > Multi-tranche Loan repayment on 2nd tranche incorrect > - > > Key: FINERACT-13 > URL: https://issues.apache.org/jira/browse/FINERACT-13 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2398 - See for attachments > 1. Create a loan product with following data sets, > Principal:10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max) > Repay Every: 1 Months > Nominal Interest Rate:1 ( Min: , Max) Per month > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Repayment StrategyPenalties, Fees, Interest, Principal order > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Recalculate Interest Yes > Advance payments adjustment type Reduce number of installments > Pre-closure interest calculation rule Calculate till pre closure date > Interest recalculation compounding on None > Frequency for recalculate Outstanding Principal Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01-Sep-15 > Enable Multiple DisbursalsTRUE > Maximum Tranche count 2 > Maximum allowed outstanding balance 1 > 2. Create specified due date charge 1% of amount and attache to the above > loan product, > 3. Submit new loan application for a client on 01 September 2015 with first > tranche of 5000 on same date and second tranche on 01 November 2015 and > amount 5000. Add specified due date charge date as 15 September 2015. > 4. Make repayment on 01 October 2015 in which charge applied on 15 September > 2015 got collected and amount as 50 (1% of disbursed amount). > 5. Disburse 2nd tranche as 5000 on 01 November 2015. > > In the repayment schedule 50 is displaying as balance in 01 October 2015 > > repayment. > > Application Should not allowed to modify or apply charge for the repayment > > which is already paid -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-613) 500 Internal Server Errors on Data Tables
[ https://issues.apache.org/jira/browse/FINERACT-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Conrad reassigned FINERACT-613: - Assignee: Santosh Math (was: Steve Conrad) > 500 Internal Server Errors on Data Tables > - > > Key: FINERACT-613 > URL: https://issues.apache.org/jira/browse/FINERACT-613 > Project: Apache Fineract > Issue Type: Bug > Components: Data Tables >Affects Versions: 1.1.0 >Reporter: Edward Cable >Assignee: Santosh Math >Priority: Blocker > Attachments: Screen Shot 2018-04-08 at 19.35.16.png > > > After the release of Apache Fineract 1.1, users have reported the following > errors related to data tables: > * A logged in user will receive an empty ‘error’ alert when they click on > any data tables that were previously set. > * On close inspection with Firefox debugger, the GET request to retrieve > datatables data is returning with an internal server error (500) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FINERACT-613) 500 Internal Server Errors on Data Tables
[ https://issues.apache.org/jira/browse/FINERACT-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Conrad resolved FINERACT-613. --- Resolution: Fixed Assignee: Steve Conrad > 500 Internal Server Errors on Data Tables > - > > Key: FINERACT-613 > URL: https://issues.apache.org/jira/browse/FINERACT-613 > Project: Apache Fineract > Issue Type: Bug > Components: Data Tables >Affects Versions: 1.1.0 >Reporter: Edward Cable >Assignee: Steve Conrad >Priority: Blocker > Attachments: Screen Shot 2018-04-08 at 19.35.16.png > > > After the release of Apache Fineract 1.1, users have reported the following > errors related to data tables: > * A logged in user will receive an empty ‘error’ alert when they click on > any data tables that were previously set. > * On close inspection with Firefox debugger, the GET request to retrieve > datatables data is returning with an internal server error (500) -- 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. - > 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 > Fix For: 1.2.0 > > 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] [Commented] (FINERACT-13) Multi-tranche Loan repayment on 2nd tranche incorrect
[ https://issues.apache.org/jira/browse/FINERACT-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517842#comment-16517842 ] Santosh Math commented on FINERACT-13: -- [~sendoro], Checked, this issue is not yet resolved. > Multi-tranche Loan repayment on 2nd tranche incorrect > - > > Key: FINERACT-13 > URL: https://issues.apache.org/jira/browse/FINERACT-13 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2398 - See for attachments > 1. Create a loan product with following data sets, > Principal:10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max) > Repay Every: 1 Months > Nominal Interest Rate:1 ( Min: , Max) Per month > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Repayment StrategyPenalties, Fees, Interest, Principal order > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Recalculate Interest Yes > Advance payments adjustment type Reduce number of installments > Pre-closure interest calculation rule Calculate till pre closure date > Interest recalculation compounding on None > Frequency for recalculate Outstanding Principal Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01-Sep-15 > Enable Multiple DisbursalsTRUE > Maximum Tranche count 2 > Maximum allowed outstanding balance 1 > 2. Create specified due date charge 1% of amount and attache to the above > loan product, > 3. Submit new loan application for a client on 01 September 2015 with first > tranche of 5000 on same date and second tranche on 01 November 2015 and > amount 5000. Add specified due date charge date as 15 September 2015. > 4. Make repayment on 01 October 2015 in which charge applied on 15 September > 2015 got collected and amount as 50 (1% of disbursed amount). > 5. Disburse 2nd tranche as 5000 on 01 November 2015. > > In the repayment schedule 50 is displaying as balance in 01 October 2015 > > repayment. > > Application Should not allowed to modify or apply charge for the repayment > > which is already paid -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-613) 500 Internal Server Errors on Data Tables
[ https://issues.apache.org/jira/browse/FINERACT-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517845#comment-16517845 ] Santosh Math commented on FINERACT-613: --- Thank you [~conradsp] for assigning this issue to me and changing the status to 'Resolved'. As a QA , it will be very helpful for me to track which are ready for QA. :) > 500 Internal Server Errors on Data Tables > - > > Key: FINERACT-613 > URL: https://issues.apache.org/jira/browse/FINERACT-613 > Project: Apache Fineract > Issue Type: Bug > Components: Data Tables >Affects Versions: 1.1.0 >Reporter: Edward Cable >Assignee: Santosh Math >Priority: Blocker > Attachments: Screen Shot 2018-04-08 at 19.35.16.png > > > After the release of Apache Fineract 1.1, users have reported the following > errors related to data tables: > * A logged in user will receive an empty ‘error’ alert when they click on > any data tables that were previously set. > * On close inspection with Firefox debugger, the GET request to retrieve > datatables data is returning with an internal server error (500) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
