[jira] [Assigned] (FINERACT-671) Adding 'Specific Due Date' charge to the loan account when date is not given, is not throwing any validation
[ https://issues.apache.org/jira/browse/FINERACT-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R reassigned FINERACT-671: - Assignee: Santosh Math (was: Shruthi M R) > Adding 'Specific Due Date' charge to the loan account when date is not given, > is not throwing any validation > > > Key: FINERACT-671 > URL: https://issues.apache.org/jira/browse/FINERACT-671 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Santosh Math >Priority: Major > Fix For: 1.3.0 > > Attachments: sde.png > > Time Spent: 20m > Remaining Estimate: 0h > > # Create a loan Account for a client. > # Create a specific due date charge. > # In Loan account, click on 'Add charge' and select specific due date > charge, but don't give date and try to submit it. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FINERACT-671) Adding 'Specific Due Date' charge to the loan account when date is not given, is not throwing any validation
[ https://issues.apache.org/jira/browse/FINERACT-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R resolved FINERACT-671. --- Resolution: Fixed > Adding 'Specific Due Date' charge to the loan account when date is not given, > is not throwing any validation > > > Key: FINERACT-671 > URL: https://issues.apache.org/jira/browse/FINERACT-671 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Major > Fix For: 1.3.0 > > Attachments: sde.png > > Time Spent: 20m > Remaining Estimate: 0h > > # Create a loan Account for a client. > # Create a specific due date charge. > # In Loan account, click on 'Add charge' and select specific due date > charge, but don't give date and try to submit it. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-518) Share Transaction doesn't capture user ID
[ https://issues.apache.org/jira/browse/FINERACT-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-518: -- Fix Version/s: (was: 1.3.0) > Share Transaction doesn't capture user ID > - > > Key: FINERACT-518 > URL: https://issues.apache.org/jira/browse/FINERACT-518 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Critical > Labels: Volunteer, gci, gsoc, p1 > > In m_share_account_transactions table there is no column for appuser_id for > capturing the user id of whose so ever has done a transaction, be it Share > purchase, Share Redeem hence auditing share transactions is hard -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (FINERACT-518) Share Transaction doesn't capture user ID
[ https://issues.apache.org/jira/browse/FINERACT-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math reopened FINERACT-518: --- > Share Transaction doesn't capture user ID > - > > Key: FINERACT-518 > URL: https://issues.apache.org/jira/browse/FINERACT-518 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Critical > Labels: Volunteer, gci, gsoc, p1 > > In m_share_account_transactions table there is no column for appuser_id for > capturing the user id of whose so ever has done a transaction, be it Share > purchase, Share Redeem hence auditing share transactions is hard -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-518) Share Transaction doesn't capture user ID
[ https://issues.apache.org/jira/browse/FINERACT-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-518. - Resolution: Workaround > Share Transaction doesn't capture user ID > - > > Key: FINERACT-518 > URL: https://issues.apache.org/jira/browse/FINERACT-518 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Critical > Labels: Volunteer, gci, gsoc, p1 > > In m_share_account_transactions table there is no column for appuser_id for > capturing the user id of whose so ever has done a transaction, be it Share > purchase, Share Redeem hence auditing share transactions is hard -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-518) Share Transaction doesn't capture user ID
[ https://issues.apache.org/jira/browse/FINERACT-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-518. - Resolution: Workaround While implementing https://issues.apache.org/jira/browse/FINERACT-440, this can be added. > Share Transaction doesn't capture user ID > - > > Key: FINERACT-518 > URL: https://issues.apache.org/jira/browse/FINERACT-518 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Critical > Labels: Volunteer, gci, gsoc, p1 > Fix For: 1.3.0 > > > In m_share_account_transactions table there is no column for appuser_id for > capturing the user id of whose so ever has done a transaction, be it Share > purchase, Share Redeem hence auditing share transactions is hard -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-107) Unable to create deposit product instance
Ashutosh Jadhav created FINCN-107: - Summary: Unable to create deposit product instance Key: FINCN-107 URL: https://issues.apache.org/jira/browse/FINCN-107 Project: Fineract Cloud Native Issue Type: Bug Components: fineract-cn-command, fineract-cn-demo-server, fineract-cn-deposit-account-management Reporter: Ashutosh Jadhav Hi While creating a new deposit product instance for a customer/member via "Manage member deposit accounts" screen in fineract-cn-fims-web-app using fineract-cn-demo-server. I just get a message on frontend screen that "Deposit account is going to be saved". But new account is not available. While checking the deposit.log at backend following is my observation - Async command to create new deposit product instance is not working. Logs of first called to First call before cache or cache entry for CreateProductInstanceCommand is created - {quote} 18:38:05.188 [async-processor-1] DEBUG command-logger - CommandBus::dispatch-async called. 18:38:05.188 [async-processor-1] DEBUG command-logger - CommandBus::storeCommand called. 18:38:05.204 [async-processor-1] INFO cassandra-logger - Create new mapping mapper for tenant [playground] and type [CommandSource]. 18:38:05.223 [async-processor-1] DEBUG command-logger - CommandBus::findCommandHandler called for CreateProductInstanceCommand. 18:38:05.232 [async-processor-1] DEBUG command-logger - CommandBus::findCommandHandler added method for CreateProductInstanceCommand. 18:38:05.267 [async-processor-1] INFO o.s.c.a.AnnotationConfigApplicationContext - Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@23952a7a: startup date [Tue Dec 25 18:38:05 IST 2018]; parent: org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@5bfbf16f 18:38:05.304 [async-processor-1] INFO o.s.b.f.a.AutowiredAnnotationBeanPostProcessor - JSR-330 'javax.inject.Inject' annotation found and supported for autowiring 18:38:05.525 [qtp1681303515-21] INFO anubis-logger - Tenant token for user depositmanager1, with key timestamp 2018-12-16T12_41_11 authenticated successfully. 18:38:05.526 [qtp1681303515-21] DEBUG anubis-logger - Authorizing access to /instances based on permission: ApplicationPermission {servletPathSegmentMatchers='/instances', allowedOperation=READ} 18:38:05.528 [async-processor-1] INFO c.n.config.ChainedDynamicProperty - Flipping property: accounting-v1.ribbon.ActiveConnectionsLimit to use NEXT property: niws.loadbalancer.availabilityFilteringRule.activeConnectionsLimit = 2147483647 18:38:05.619 [async-processor-1] INFO c.n.u.c.ShutdownEnabledTimer - Shutdown hook installed for: NFLoadBalancer-PingTimer-accounting-v1 18:38:05.629 [async-processor-1] INFO c.n.loadbalancer.BaseLoadBalancer - Client:accounting-v1 instantiated a LoadBalancer:DynamicServerListLoadBalancer:\{NFLoadBalancer:name=accounting-v1,current list of Servers=[],Load balancer stats=Zone stats: {},Server stats: []}ServerList:null 18:38:05.638 [async-processor-1] INFO c.n.l.DynamicServerListLoadBalancer - Using serverListUpdater PollingServerListUpdater 18:38:05.680 [async-processor-1] INFO c.n.config.ChainedDynamicProperty - Flipping property: accounting-v1.ribbon.ActiveConnectionsLimit to use NEXT property: niws.loadbalancer.availabilityFilteringRule.activeConnectionsLimit = 2147483647 18:38:05.683 [async-processor-1] INFO c.n.l.DynamicServerListLoadBalancer - DynamicServerListLoadBalancer for client accounting-v1 initialized: DynamicServerListLoadBalancer:{NFLoadBalancer:name=accounting-v1,current list of Servers=[localhost:2025],Load balancer stats=Zone stats: {defaultzone=[Zone:defaultzone; Instance count:1; Active connections count: 0; Circuit breaker tripped count: 0; Active connections per server: 0.0;] },Server stats: [[Server:localhost:2025; Zone:defaultZone; Total Requests:0; Successive connection failure:0; Total blackout seconds:0; Last connection made:Thu Jan 01 05:30:00 IST 1970; First connection made: Thu Jan 01 05:30:00 IST 1970; Active Connections:0; total failure count in last (1000) msecs:0; average resp time:0.0; 90 percentile resp time:0.0; 95 percentile resp time:0.0; min resp time:0.0; max resp time:0.0; stddev resp time:0.0] ]} ServerList:org.springframework.cloud.netflix.ribbon.eureka.DomainExtractingServerList@7d6cf5ab 18:38:06.039 [async-processor-1] WARN command-logger - Error while processing command. NotFoundException: no details available 18:38:06.039 [async-processor-1] DEBUG command-logger - CommandBus::updateCommandSource called. ``` {quote} After the entry for CreateProductInstanceCommand is available in cachec and no call to add CreateProductInstanceCommand. {quote}```java 18:46:24.637 [async-processor-2] DEBUG command-logger - CommandBus::dispatch-async called. 18:46:24.638 [async-processor-
[jira] [Commented] (FINERACT-186) optimising the Post Interest For Savings batch job using pagination
[ https://issues.apache.org/jira/browse/FINERACT-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728706#comment-16728706 ] Shruthi M R commented on FINERACT-186: --- [~venkata ganesh] worked on this improvement. > optimising the Post Interest For Savings batch job using pagination > --- > > Key: FINERACT-186 > URL: https://issues.apache.org/jira/browse/FINERACT-186 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: venkat Ganesh >Assignee: Shruthi M R >Priority: Minor > Labels: gsoc, p1 > Fix For: 1.3.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FINERACT-186) optimising the Post Interest For Savings batch job using pagination
[ https://issues.apache.org/jira/browse/FINERACT-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R resolved FINERACT-186. --- Resolution: Fixed > optimising the Post Interest For Savings batch job using pagination > --- > > Key: FINERACT-186 > URL: https://issues.apache.org/jira/browse/FINERACT-186 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: venkat Ganesh >Assignee: Shruthi M R >Priority: Minor > Labels: gsoc, p1 > Fix For: 1.3.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-186) optimising the Post Interest For Savings batch job using pagination
[ https://issues.apache.org/jira/browse/FINERACT-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R reassigned FINERACT-186: - Assignee: (was: Markus Geiss) > optimising the Post Interest For Savings batch job using pagination > --- > > Key: FINERACT-186 > URL: https://issues.apache.org/jira/browse/FINERACT-186 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: venkat Ganesh >Priority: Minor > Labels: gsoc, p1 > Fix For: 1.3.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-186) optimising the Post Interest For Savings batch job using pagination
[ https://issues.apache.org/jira/browse/FINERACT-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R reassigned FINERACT-186: - Assignee: Shruthi M R > optimising the Post Interest For Savings batch job using pagination > --- > > Key: FINERACT-186 > URL: https://issues.apache.org/jira/browse/FINERACT-186 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: venkat Ganesh >Assignee: Shruthi M R >Priority: Minor > Labels: gsoc, p1 > Fix For: 1.3.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-518) Share Transaction doesn't capture user ID
[ https://issues.apache.org/jira/browse/FINERACT-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728683#comment-16728683 ] Shruthi M R commented on FINERACT-518: --- [~santoshmath] as suggested by [~Ippez] can we close this issue and merge with https://issues.apache.org/jira/browse/FINERACT-440 .? > Share Transaction doesn't capture user ID > - > > Key: FINERACT-518 > URL: https://issues.apache.org/jira/browse/FINERACT-518 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Critical > Labels: Volunteer, gci, gsoc, p1 > Fix For: 1.3.0 > > > In m_share_account_transactions table there is no column for appuser_id for > capturing the user id of whose so ever has done a transaction, be it Share > purchase, Share Redeem hence auditing share transactions is hard -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-518) Share Transaction doesn't capture user ID
[ https://issues.apache.org/jira/browse/FINERACT-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R updated FINERACT-518: -- Issue Type: Improvement (was: Bug) > Share Transaction doesn't capture user ID > - > > Key: FINERACT-518 > URL: https://issues.apache.org/jira/browse/FINERACT-518 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Critical > Labels: Volunteer, gci, gsoc, p1 > Fix For: 1.3.0 > > > In m_share_account_transactions table there is no column for appuser_id for > capturing the user id of whose so ever has done a transaction, be it Share > purchase, Share Redeem hence auditing share transactions is hard -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-336) Fund Mapping page Points to Advanced Search page
[ https://issues.apache.org/jira/browse/FINERACT-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728679#comment-16728679 ] Shruthi M R commented on FINERACT-336: --- Temporarily hide the fund mapping icon. Done this in,https://github.com/openMF/community-app/pull/3075 > Fund Mapping page Points to Advanced Search page > > > Key: FINERACT-336 > URL: https://issues.apache.org/jira/browse/FINERACT-336 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: gsoc, p1 > Fix For: 1.4.0 > > Attachments: fundmapping.png > > > Reported by Ed Cable at https://mifosforge.jira.com/browse/MIFOSX-2795 > Original Description: > Hi all, > I think this bug has been existent for several months now as we actually > documented it as intended functionality at > https://mifosforge.jira.com/wiki/display/docs/Fund+Mapping > If you got to Admin >> Organization >> Fund Mapping, clicking the link takes > you to > https://demo4.openmf.org/#/advsearch > rather than the intended page on fund mapping (i'm not sure which it is). > On a similar note, I don't think this advance search link is accessible from > the search menu although it should be there or in the quick links. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-336) Fund Mapping page Points to Advanced Search page
[ https://issues.apache.org/jira/browse/FINERACT-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shruthi M R updated FINERACT-336: -- Fix Version/s: (was: 1.3.0) 1.4.0 > Fund Mapping page Points to Advanced Search page > > > Key: FINERACT-336 > URL: https://issues.apache.org/jira/browse/FINERACT-336 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: gsoc, p1 > Fix For: 1.4.0 > > Attachments: fundmapping.png > > > Reported by Ed Cable at https://mifosforge.jira.com/browse/MIFOSX-2795 > Original Description: > Hi all, > I think this bug has been existent for several months now as we actually > documented it as intended functionality at > https://mifosforge.jira.com/wiki/display/docs/Fund+Mapping > If you got to Admin >> Organization >> Fund Mapping, clicking the link takes > you to > https://demo4.openmf.org/#/advsearch > rather than the intended page on fund mapping (i'm not sure which it is). > On a similar note, I don't think this advance search link is accessible from > the search menu although it should be there or in the quick links. -- This message was sent by Atlassian JIRA (v7.6.3#76005)