Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 56847200C6C for ; Fri, 5 May 2017 15:07:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 55026160BBE; Fri, 5 May 2017 13:07:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 9ADB3160B97 for ; Fri, 5 May 2017 15:07:09 +0200 (CEST) Received: (qmail 19281 invoked by uid 500); 5 May 2017 13:07:08 -0000 Mailing-List: contact dev-help@fineract.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@fineract.apache.org Delivered-To: mailing list dev@fineract.apache.org Received: (qmail 19176 invoked by uid 99); 5 May 2017 13:07:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 May 2017 13:07:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id A070AC0AB8 for ; Fri, 5 May 2017 13:07:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id lXiR3F4nFA2n for ; Fri, 5 May 2017 13:07:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 296CD5F567 for ; Fri, 5 May 2017 13:07:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6F4CDE06BF for ; Fri, 5 May 2017 13:07:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 310FF21DED for ; Fri, 5 May 2017 13:07:04 +0000 (UTC) Date: Fri, 5 May 2017 13:07:04 +0000 (UTC) From: "Shaik Nazeer Hussain (JIRA)" To: dev@fineract.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (FINERACT-205) If the disbursement date is changed to next meeting date during loan disbursement then first repayment date is falling on disbursement date in repayment schedule MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 05 May 2017 13:07:10 -0000 [ https://issues.apache.org/jira/browse/FINERACT-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaik Nazeer Hussain resolved FINERACT-205. ------------------------------------------- Resolution: Fixed Assignee: Santosh Math (was: Markus Geiss) Fix Version/s: 1.0.0 > If the disbursement date is changed to next meeting date during loan disbursement then first repayment date is falling on disbursement date in repayment schedule > ----------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: FINERACT-205 > URL: https://issues.apache.org/jira/browse/FINERACT-205 > Project: Apache Fineract > Issue Type: Bug > Components: Loan > Reporter: subramanyasn > Assignee: Santosh Math > Labels: p1 > Fix For: 1.0.0 > > Attachments: JLG Loans.png > > > 1. Create simple loan product. > 2. Create a group with meeting attached, weekly every 1 week Friday, from 01 January 2016. > 3. Create a client under that Group and submit new JLG loan with weekly repayment on 01 January 2016, expected disbursement on 01 January 2016. > 4. Approve on 01 January 2016, during disbursement modify date to next meeting date ie on 08 January 2016. > > The repayment schedule should get generated such that the first repayment falls on 15 January 2016. But the first repayment falling on the date of disbursement ie on 08 January 2016. -- This message was sent by Atlassian JIRA (v6.3.15#6346)