Mailing-List: contact dev-help@fineract.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@fineract.incubator.apache.org
Date: Mon, 12 Dec 2016 04:30:58 +0000 (UTC)
From: "Santosh Math (JIRA)" <jira@apache.org>
To: dev@fineract.incubator.apache.org
Message-ID: <JIRA.13027343.1481517020000.495315.1481517058378@Atlassian.JIRA>
In-Reply-To: <JIRA.13027343.1481517020000@Atlassian.JIRA>
References: <JIRA.13027343.1481517020000@Atlassian.JIRA> <JIRA.13027343.1481517020588@arcas>
Subject: [jira] [Created] (FINERACT-295) Unable to Inactivate Annual (or any
 other recurring fees) fees under certain conditions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 12 Dec 2016 04:31:03 -0000

Santosh Math created FINERACT-295:
-------------------------------------

             Summary: Unable to Inactivate Annual (or any other recurring fees) fees under certain conditions
                 Key: FINERACT-295
                 URL: https://issues.apache.org/jira/browse/FINERACT-295
             Project: Apache Fineract
          Issue Type: Bug
          Components: Savings
            Reporter: Santosh Math
            Assignee: Markus Geiss


Reported by Vishwas Babu at https://mifosforge.jira.com/browse/MIFOSX-1841

Original Description:
The restriction put in for waiving annual fees (or any other recurring fee is that the fee should not already be due before it can be waived)
So, for example, I create an annual fee applicable on 15th January, the following workflow results in an error
1) Create a savings account on 2012
2) Try to waive the fee as of today (todays date is 14th Jan 2015). I should not be able waive the fee since two instances of the fee 15th Jan 2013 and 15th Jan 2014 have already been applied
3) Next pay the fees for 2013 and 2014
4) Now the next due fee is as of tomorrow (Jan 15 2015). So If I inactivate the fee today, i.e on 14th Jan we see an error saying the fee cannot be inactivated as it has already been applied. The error is invalid as the next due date of the fee is tomorrow, so the fee has not yet become due
subramanya Can you please test this out on 1.26 and ensure that you are able to reproduce the same.
Finally before making the issue as fixed, test out this bit of functionality in entirety as there could be regression issues


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)