[jira] [Commented] (FINERACT-802) The client can have two or more different usernames to login as self service user
[ https://issues.apache.org/jira/browse/FINERACT-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000855#comment-17000855 ] Santosh Math commented on FINERACT-802: --- [~vorburger] , Sorry I have been off from work because of some personal reason. May I know what's the status of PR #664?. I just checked that It's been closed and reopened again. OR, any new PR is raised which I need to test? > The client can have two or more different usernames to login as self service > user > -- > > Key: FINERACT-802 > URL: https://issues.apache.org/jira/browse/FINERACT-802 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Assignee: Peter Kakoma >Priority: Major > Labels: GCI-2019, p1 > Fix For: 1.4.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide unique > username. > # Provide password and then click on 'Activate Self Service User' button. > # Again in 'More' menu, click on 'Create Self Service user' and follow 3rd > and 4th steps( this time give different username). > h2. Expected Behaviour > Application allows to create two user ids for the same client. > h2. Actual Behaviour > It should throw validation "Self Service User Id is already created. Go to > Admin->Users to edit or delete the self-service user." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FINERACT-753) incorrect savings account balance when charge transaction is reversed during an overdraft recalculate Daily Balances
[
https://issues.apache.org/jira/browse/FINERACT-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santosh Math closed FINERACT-753.
-
> incorrect savings account balance when charge transaction is reversed during
> an overdraft recalculate Daily Balances
>
>
> Key: FINERACT-753
> URL: https://issues.apache.org/jira/browse/FINERACT-753
> Project: Apache Fineract
> Issue Type: Bug
> Components: Savings
>Affects Versions: 1.3.1
>Reporter: andrewDzakpasu
>Assignee: Ed Cable
>Priority: Major
> Labels: p1
> Fix For: 1.4.0
>
> Attachments: current .png, previous issue.png, previous issue.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This bug occurs in specific scenarios where there is an overdraft on account
> code section where the bug offers is below on
> protected void recalculateDailyBalances(final Money openingAccountBalance,
> final LocalDate interestPostingUpToDate)
> {code:java}
> runningBalance = runningBalance.plus(transactionAmount);
> transaction.updateRunningBalance(runningBalance);
> if (overdraftAmount.isZero() && runningBalance.isLessThanZero()) {
> overdraftAmount =
> overdraftAmount.plus(runningBalance.getAmount().negate());
> }
> if (transaction.getId() == null && overdraftAmount.isGreaterThanZero()) {
> transaction.updateOverdraftAmount(overdraftAmount.getAmount());
> } else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> }
> {code}
>
> steps to recreate .
> Set up a savings account with an overdraft say 500.
> # create saying account and add a charge fee of say 300 with opening balance
> of 500 approve and activate.
> # pay charge of 300 balance with now be 200 . charge is paid which creates
> an object in m_savings_account_charge_paid_by
> # now reverse the deposit of 500 .
> # system will recalculateDailyBalances and reverse the charge transaction on
> this section of the code
> {code:java}
> else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> {code}
> # now since the new charge created does not have the charged paid by object
> in the table " m_savings_account_charge_paid_by" recalculating the account
> balance becomes wrong
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (FINERACT-753) incorrect savings account balance when charge transaction is reversed during an overdraft recalculate Daily Balances
[
https://issues.apache.org/jira/browse/FINERACT-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santosh Math resolved FINERACT-753.
---
Resolution: Fixed
> incorrect savings account balance when charge transaction is reversed during
> an overdraft recalculate Daily Balances
>
>
> Key: FINERACT-753
> URL: https://issues.apache.org/jira/browse/FINERACT-753
> Project: Apache Fineract
> Issue Type: Bug
> Components: Savings
>Affects Versions: 1.3.1
>Reporter: andrewDzakpasu
>Assignee: Ed Cable
>Priority: Major
> Labels: p1
> Fix For: 1.4.0
>
> Attachments: current .png, previous issue.png, previous issue.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This bug occurs in specific scenarios where there is an overdraft on account
> code section where the bug offers is below on
> protected void recalculateDailyBalances(final Money openingAccountBalance,
> final LocalDate interestPostingUpToDate)
> {code:java}
> runningBalance = runningBalance.plus(transactionAmount);
> transaction.updateRunningBalance(runningBalance);
> if (overdraftAmount.isZero() && runningBalance.isLessThanZero()) {
> overdraftAmount =
> overdraftAmount.plus(runningBalance.getAmount().negate());
> }
> if (transaction.getId() == null && overdraftAmount.isGreaterThanZero()) {
> transaction.updateOverdraftAmount(overdraftAmount.getAmount());
> } else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> }
> {code}
>
> steps to recreate .
> Set up a savings account with an overdraft say 500.
> # create saying account and add a charge fee of say 300 with opening balance
> of 500 approve and activate.
> # pay charge of 300 balance with now be 200 . charge is paid which creates
> an object in m_savings_account_charge_paid_by
> # now reverse the deposit of 500 .
> # system will recalculateDailyBalances and reverse the charge transaction on
> this section of the code
> {code:java}
> else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> {code}
> # now since the new charge created does not have the charged paid by object
> in the table " m_savings_account_charge_paid_by" recalculating the account
> balance becomes wrong
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-753) incorrect savings account balance when charge transaction is reversed during an overdraft recalculate Daily Balances
[
https://issues.apache.org/jira/browse/FINERACT-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16992408#comment-16992408
]
Santosh Math commented on FINERACT-753:
---
Hi [~andrew.dzak], tested this in my local machine by pulling the PR:
[https://github.com/apache/fineract/pull/659] .
I followed the steps mentioned in the description of this PR. When issue was
there it was showing wrong savings balace(1st screenshot) and after correcting
it it's showing right value(second screeshot with negative balance). Please
confirm.
!previous issue.png!!current .png!
> incorrect savings account balance when charge transaction is reversed during
> an overdraft recalculate Daily Balances
>
>
> Key: FINERACT-753
> URL: https://issues.apache.org/jira/browse/FINERACT-753
> Project: Apache Fineract
> Issue Type: Bug
> Components: Savings
>Affects Versions: 1.3.1
>Reporter: andrewDzakpasu
>Assignee: Ed Cable
>Priority: Major
> Labels: p1
> Fix For: 1.4.0
>
> Attachments: current .png, previous issue.png, previous issue.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This bug occurs in specific scenarios where there is an overdraft on account
> code section where the bug offers is below on
> protected void recalculateDailyBalances(final Money openingAccountBalance,
> final LocalDate interestPostingUpToDate)
> {code:java}
> runningBalance = runningBalance.plus(transactionAmount);
> transaction.updateRunningBalance(runningBalance);
> if (overdraftAmount.isZero() && runningBalance.isLessThanZero()) {
> overdraftAmount =
> overdraftAmount.plus(runningBalance.getAmount().negate());
> }
> if (transaction.getId() == null && overdraftAmount.isGreaterThanZero()) {
> transaction.updateOverdraftAmount(overdraftAmount.getAmount());
> } else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> }
> {code}
>
> steps to recreate .
> Set up a savings account with an overdraft say 500.
> # create saying account and add a charge fee of say 300 with opening balance
> of 500 approve and activate.
> # pay charge of 300 balance with now be 200 . charge is paid which creates
> an object in m_savings_account_charge_paid_by
> # now reverse the deposit of 500 .
> # system will recalculateDailyBalances and reverse the charge transaction on
> this section of the code
> {code:java}
> else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> {code}
> # now since the new charge created does not have the charged paid by object
> in the table " m_savings_account_charge_paid_by" recalculating the account
> balance becomes wrong
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FINERACT-753) incorrect savings account balance when charge transaction is reversed during an overdraft recalculate Daily Balances
[
https://issues.apache.org/jira/browse/FINERACT-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santosh Math updated FINERACT-753:
--
Attachment: current .png
> incorrect savings account balance when charge transaction is reversed during
> an overdraft recalculate Daily Balances
>
>
> Key: FINERACT-753
> URL: https://issues.apache.org/jira/browse/FINERACT-753
> Project: Apache Fineract
> Issue Type: Bug
> Components: Savings
>Affects Versions: 1.3.1
>Reporter: andrewDzakpasu
>Assignee: Ed Cable
>Priority: Major
> Labels: p1
> Fix For: 1.4.0
>
> Attachments: current .png, previous issue.png, previous issue.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This bug occurs in specific scenarios where there is an overdraft on account
> code section where the bug offers is below on
> protected void recalculateDailyBalances(final Money openingAccountBalance,
> final LocalDate interestPostingUpToDate)
> {code:java}
> runningBalance = runningBalance.plus(transactionAmount);
> transaction.updateRunningBalance(runningBalance);
> if (overdraftAmount.isZero() && runningBalance.isLessThanZero()) {
> overdraftAmount =
> overdraftAmount.plus(runningBalance.getAmount().negate());
> }
> if (transaction.getId() == null && overdraftAmount.isGreaterThanZero()) {
> transaction.updateOverdraftAmount(overdraftAmount.getAmount());
> } else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> }
> {code}
>
> steps to recreate .
> Set up a savings account with an overdraft say 500.
> # create saying account and add a charge fee of say 300 with opening balance
> of 500 approve and activate.
> # pay charge of 300 balance with now be 200 . charge is paid which creates
> an object in m_savings_account_charge_paid_by
> # now reverse the deposit of 500 .
> # system will recalculateDailyBalances and reverse the charge transaction on
> this section of the code
> {code:java}
> else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> {code}
> # now since the new charge created does not have the charged paid by object
> in the table " m_savings_account_charge_paid_by" recalculating the account
> balance becomes wrong
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FINERACT-753) incorrect savings account balance when charge transaction is reversed during an overdraft recalculate Daily Balances
[
https://issues.apache.org/jira/browse/FINERACT-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santosh Math updated FINERACT-753:
--
Attachment: previous issue.png
> incorrect savings account balance when charge transaction is reversed during
> an overdraft recalculate Daily Balances
>
>
> Key: FINERACT-753
> URL: https://issues.apache.org/jira/browse/FINERACT-753
> Project: Apache Fineract
> Issue Type: Bug
> Components: Savings
>Affects Versions: 1.3.1
>Reporter: andrewDzakpasu
>Assignee: Ed Cable
>Priority: Major
> Labels: p1
> Fix For: 1.4.0
>
> Attachments: current .png, previous issue.png, previous issue.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This bug occurs in specific scenarios where there is an overdraft on account
> code section where the bug offers is below on
> protected void recalculateDailyBalances(final Money openingAccountBalance,
> final LocalDate interestPostingUpToDate)
> {code:java}
> runningBalance = runningBalance.plus(transactionAmount);
> transaction.updateRunningBalance(runningBalance);
> if (overdraftAmount.isZero() && runningBalance.isLessThanZero()) {
> overdraftAmount =
> overdraftAmount.plus(runningBalance.getAmount().negate());
> }
> if (transaction.getId() == null && overdraftAmount.isGreaterThanZero()) {
> transaction.updateOverdraftAmount(overdraftAmount.getAmount());
> } else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> }
> {code}
>
> steps to recreate .
> Set up a savings account with an overdraft say 500.
> # create saying account and add a charge fee of say 300 with opening balance
> of 500 approve and activate.
> # pay charge of 300 balance with now be 200 . charge is paid which creates
> an object in m_savings_account_charge_paid_by
> # now reverse the deposit of 500 .
> # system will recalculateDailyBalances and reverse the charge transaction on
> this section of the code
> {code:java}
> else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> {code}
> # now since the new charge created does not have the charged paid by object
> in the table " m_savings_account_charge_paid_by" recalculating the account
> balance becomes wrong
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-753) incorrect savings account balance when charge transaction is reversed during an overdraft recalculate Daily Balances
[
https://issues.apache.org/jira/browse/FINERACT-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16992408#comment-16992408
]
Santosh Math edited comment on FINERACT-753 at 12/10/19 10:36 AM:
--
Hi [~andrew.dzak], tested this in my local machine by pulling the PR:
[https://github.com/apache/fineract/pull/659] .
I followed the steps mentioned in the description of this ticket. When issue
was there it was showing wrong savings balace(1st screenshot) and after
correcting it it's showing right value(second screeshot with negative balance).
Please confirm.
!previous issue.png!!current .png!
was (Author: santoshmath):
Hi [~andrew.dzak], tested this in my local machine by pulling the PR:
[https://github.com/apache/fineract/pull/659] .
I followed the steps mentioned in the description of this PR. When issue was
there it was showing wrong savings balace(1st screenshot) and after correcting
it it's showing right value(second screeshot with negative balance). Please
confirm.
!previous issue.png!!current .png!
> incorrect savings account balance when charge transaction is reversed during
> an overdraft recalculate Daily Balances
>
>
> Key: FINERACT-753
> URL: https://issues.apache.org/jira/browse/FINERACT-753
> Project: Apache Fineract
> Issue Type: Bug
> Components: Savings
>Affects Versions: 1.3.1
>Reporter: andrewDzakpasu
>Assignee: Ed Cable
>Priority: Major
> Labels: p1
> Fix For: 1.4.0
>
> Attachments: current .png, previous issue.png, previous issue.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This bug occurs in specific scenarios where there is an overdraft on account
> code section where the bug offers is below on
> protected void recalculateDailyBalances(final Money openingAccountBalance,
> final LocalDate interestPostingUpToDate)
> {code:java}
> runningBalance = runningBalance.plus(transactionAmount);
> transaction.updateRunningBalance(runningBalance);
> if (overdraftAmount.isZero() && runningBalance.isLessThanZero()) {
> overdraftAmount =
> overdraftAmount.plus(runningBalance.getAmount().negate());
> }
> if (transaction.getId() == null && overdraftAmount.isGreaterThanZero()) {
> transaction.updateOverdraftAmount(overdraftAmount.getAmount());
> } else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> }
> {code}
>
> steps to recreate .
> Set up a savings account with an overdraft say 500.
> # create saying account and add a charge fee of say 300 with opening balance
> of 500 approve and activate.
> # pay charge of 300 balance with now be 200 . charge is paid which creates
> an object in m_savings_account_charge_paid_by
> # now reverse the deposit of 500 .
> # system will recalculateDailyBalances and reverse the charge transaction on
> this section of the code
> {code:java}
> else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> {code}
> # now since the new charge created does not have the charged paid by object
> in the table " m_savings_account_charge_paid_by" recalculating the account
> balance becomes wrong
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FINERACT-753) incorrect savings account balance when charge transaction is reversed during an overdraft recalculate Daily Balances
[
https://issues.apache.org/jira/browse/FINERACT-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santosh Math updated FINERACT-753:
--
Attachment: previous issue.png
> incorrect savings account balance when charge transaction is reversed during
> an overdraft recalculate Daily Balances
>
>
> Key: FINERACT-753
> URL: https://issues.apache.org/jira/browse/FINERACT-753
> Project: Apache Fineract
> Issue Type: Bug
> Components: Savings
>Affects Versions: 1.3.1
>Reporter: andrewDzakpasu
>Assignee: Ed Cable
>Priority: Major
> Labels: p1
> Fix For: 1.4.0
>
> Attachments: previous issue.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This bug occurs in specific scenarios where there is an overdraft on account
> code section where the bug offers is below on
> protected void recalculateDailyBalances(final Money openingAccountBalance,
> final LocalDate interestPostingUpToDate)
> {code:java}
> runningBalance = runningBalance.plus(transactionAmount);
> transaction.updateRunningBalance(runningBalance);
> if (overdraftAmount.isZero() && runningBalance.isLessThanZero()) {
> overdraftAmount =
> overdraftAmount.plus(runningBalance.getAmount().negate());
> }
> if (transaction.getId() == null && overdraftAmount.isGreaterThanZero()) {
> transaction.updateOverdraftAmount(overdraftAmount.getAmount());
> } else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> }
> {code}
>
> steps to recreate .
> Set up a savings account with an overdraft say 500.
> # create saying account and add a charge fee of say 300 with opening balance
> of 500 approve and activate.
> # pay charge of 300 balance with now be 200 . charge is paid which creates
> an object in m_savings_account_charge_paid_by
> # now reverse the deposit of 500 .
> # system will recalculateDailyBalances and reverse the charge transaction on
> this section of the code
> {code:java}
> else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> {code}
> # now since the new charge created does not have the charged paid by object
> in the table " m_savings_account_charge_paid_by" recalculating the account
> balance becomes wrong
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-802) The client can have two or more different usernames to login as self service user
[ https://issues.apache.org/jira/browse/FINERACT-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986843#comment-16986843 ] Santosh Math commented on FINERACT-802: --- [~kakoma], Are you able to resolve this? > The client can have two or more different usernames to login as self service > user > -- > > Key: FINERACT-802 > URL: https://issues.apache.org/jira/browse/FINERACT-802 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Assignee: Peter Kakoma >Priority: Major > Labels: GCI-2019, p1 > Fix For: 1.4.0 > > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide unique > username. > # Provide password and then click on 'Activate Self Service User' button. > # Again in 'More' menu, click on 'Create Self Service user' and follow 3rd > and 4th steps( this time give different username). > h2. Expected Behaviour > Application allows to create two user ids for the same client. > h2. Actual Behaviour > It should throw validation "Self Service User Id is already created. Go to > Admin->Users to edit or delete the self-service user." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-802) The client can have two or more different usernames to login as self service user
[ https://issues.apache.org/jira/browse/FINERACT-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986843#comment-16986843 ] Santosh Math edited comment on FINERACT-802 at 12/3/19 12:22 PM: - [~kakoma], Did you get time look into this? was (Author: santoshmath): [~kakoma], Are you able to resolve this? > The client can have two or more different usernames to login as self service > user > -- > > Key: FINERACT-802 > URL: https://issues.apache.org/jira/browse/FINERACT-802 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Assignee: Peter Kakoma >Priority: Major > Labels: GCI-2019, p1 > Fix For: 1.4.0 > > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide unique > username. > # Provide password and then click on 'Activate Self Service User' button. > # Again in 'More' menu, click on 'Create Self Service user' and follow 3rd > and 4th steps( this time give different username). > h2. Expected Behaviour > Application allows to create two user ids for the same client. > h2. Actual Behaviour > It should throw validation "Self Service User Id is already created. Go to > Admin->Users to edit or delete the self-service user." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-803) No validation(500 Internal Server Error) if we use username which is already taken
[ https://issues.apache.org/jira/browse/FINERACT-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-803: -- Labels: p1 volunteers (was: GCI-2019 p1 volunteers) > No validation(500 Internal Server Error) if we use username which is already > taken > -- > > Key: FINERACT-803 > URL: https://issues.apache.org/jira/browse/FINERACT-803 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Assignee: Peter Kakoma >Priority: Major > Labels: p1, volunteers > Fix For: 1.4.0 > > Time Spent: 10m > Remaining Estimate: 0h > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide username > which is already used and uncheck 'Auto Generate password'. > # Provide password and then click on 'Activate Self Service User' button. > h2. Expected Behaviour > Should throw validation, "Username is already taken". > h2. Actual Behaviour > No validation message is displaying and if we check the network, it is > showing 500 internal server error. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-802) The client can have two or more different usernames to login as self service user
[ https://issues.apache.org/jira/browse/FINERACT-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math reassigned FINERACT-802: - Assignee: Peter Kakoma > The client can have two or more different usernames to login as self service > user > -- > > Key: FINERACT-802 > URL: https://issues.apache.org/jira/browse/FINERACT-802 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Assignee: Peter Kakoma >Priority: Major > Labels: GCI-2019, p1 > Fix For: 1.4.0 > > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide unique > username. > # Provide password and then click on 'Activate Self Service User' button. > # Again in 'More' menu, click on 'Create Self Service user' and follow 3rd > and 4th steps( this time give different username). > h2. Expected Behaviour > Application allows to create two user ids for the same client. > h2. Actual Behaviour > It should throw validation "Self Service User Id is already created. Go to > Admin->Users to edit or delete the self-service user." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-803) No validation(500 Internal Server Error) if we use username which is already taken
[ https://issues.apache.org/jira/browse/FINERACT-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math reassigned FINERACT-803: - Assignee: Peter Kakoma > No validation(500 Internal Server Error) if we use username which is already > taken > -- > > Key: FINERACT-803 > URL: https://issues.apache.org/jira/browse/FINERACT-803 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Assignee: Peter Kakoma >Priority: Major > Labels: GCI-2019, p1, volunteers > Fix For: 1.4.0 > > Time Spent: 10m > Remaining Estimate: 0h > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide username > which is already used and uncheck 'Auto Generate password'. > # Provide password and then click on 'Activate Self Service User' button. > h2. Expected Behaviour > Should throw validation, "Username is already taken". > h2. Actual Behaviour > No validation message is displaying and if we check the network, it is > showing 500 internal server error. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-773) Make it possible to customize JDBC URLs in Docker Image at run-time instead of at build
[
https://issues.apache.org/jira/browse/FINERACT-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16983138#comment-16983138
]
Santosh Math commented on FINERACT-773:
---
[~vorburger], [~awasum], PR #648 is merged. Can we change this ticket status
to resolved?
> Make it possible to customize JDBC URLs in Docker Image at run-time instead
> of at build
> ---
>
> Key: FINERACT-773
> URL: https://issues.apache.org/jira/browse/FINERACT-773
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: Michael Vorburger
>Assignee: Michael Vorburger
>Priority: Major
> Fix For: 1.4.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Based on FINERACT-760 discussions in
> [https://github.com/apache/fineract/pull/593] and
> [https://github.com/apache/fineract/pull/595], quote:
> {quote}Will continue to think about a more robust solution. Ideally the db
> seeding scripts will not have a db hostname encoded at all and would pull
> that from an environment variable (defaulting to localhost or some sane
> default).
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-803) No validation(500 Internal Server Error) if we use username which is already taken
[ https://issues.apache.org/jira/browse/FINERACT-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982283#comment-16982283 ] Santosh Math edited comment on FINERACT-803 at 11/26/19 9:28 AM: - Thanks [~kakoma]. You can reproduce this issue here: [https://mobile.openmf.org/#|https://mobile/] username: mifos password: password. was (Author: santoshmath): Thanks [~kakoma]. You can reproduce this issue here: [https://mobile.openmf.org|https://mobile/] username: mifos password: password. > No validation(500 Internal Server Error) if we use username which is already > taken > -- > > Key: FINERACT-803 > URL: https://issues.apache.org/jira/browse/FINERACT-803 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Priority: Major > Labels: GCI-2019, p1, volunteers > Fix For: 1.4.0 > > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide username > which is already used and uncheck 'Auto Generate password'. > # Provide password and then click on 'Activate Self Service User' button. > h2. Expected Behaviour > Should throw validation, "Username is already taken". > h2. Actual Behaviour > No validation message is displaying and if we check the network, it is > showing 500 internal server error. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-803) No validation(500 Internal Server Error) if we use username which is already taken
[ https://issues.apache.org/jira/browse/FINERACT-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982283#comment-16982283 ] Santosh Math commented on FINERACT-803: --- Thanks [~kakoma]. You can reproduce this issue here: [https://mobile.openmf.org.|https://mobile/] username: mifos password: password. > No validation(500 Internal Server Error) if we use username which is already > taken > -- > > Key: FINERACT-803 > URL: https://issues.apache.org/jira/browse/FINERACT-803 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Priority: Major > Labels: GCI-2019, p1, volunteers > Fix For: 1.4.0 > > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide username > which is already used and uncheck 'Auto Generate password'. > # Provide password and then click on 'Activate Self Service User' button. > h2. Expected Behaviour > Should throw validation, "Username is already taken". > h2. Actual Behaviour > No validation message is displaying and if we check the network, it is > showing 500 internal server error. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-803) No validation(500 Internal Server Error) if we use username which is already taken
[ https://issues.apache.org/jira/browse/FINERACT-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982283#comment-16982283 ] Santosh Math edited comment on FINERACT-803 at 11/26/19 9:27 AM: - Thanks [~kakoma]. You can reproduce this issue here: [https://mobile.openmf.org|https://mobile/] username: mifos password: password. was (Author: santoshmath): Thanks [~kakoma]. You can reproduce this issue here: [https://mobile.openmf.org.|https://mobile/] username: mifos password: password. > No validation(500 Internal Server Error) if we use username which is already > taken > -- > > Key: FINERACT-803 > URL: https://issues.apache.org/jira/browse/FINERACT-803 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Priority: Major > Labels: GCI-2019, p1, volunteers > Fix For: 1.4.0 > > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide username > which is already used and uncheck 'Auto Generate password'. > # Provide password and then click on 'Activate Self Service User' button. > h2. Expected Behaviour > Should throw validation, "Username is already taken". > h2. Actual Behaviour > No validation message is displaying and if we check the network, it is > showing 500 internal server error. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-791) Transfer of fund from saving balance to shares
[ https://issues.apache.org/jira/browse/FINERACT-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-791: -- Labels: gsoc p1 (was: p1) > Transfer of fund from saving balance to shares > -- > > Key: FINERACT-791 > URL: https://issues.apache.org/jira/browse/FINERACT-791 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings, Shares >Affects Versions: 1.0.0 >Reporter: Mexina Daniel >Assignee: Mexina Daniel >Priority: Major > Labels: gsoc, p1 > Fix For: 1.5.0 > > > This improvement will enable to use saving balance to purchase a share > through the feature of transfer fund. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-803) No validation(500 Internal Server Error) if we use username which is already taken
[ https://issues.apache.org/jira/browse/FINERACT-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982257#comment-16982257 ] Santosh Math commented on FINERACT-803: --- [~kakoma] , Is it possbile to resolve this ticket at earliest? > No validation(500 Internal Server Error) if we use username which is already > taken > -- > > Key: FINERACT-803 > URL: https://issues.apache.org/jira/browse/FINERACT-803 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Priority: Major > Labels: GCI-2019, p1, volunteers > Fix For: 1.4.0 > > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide username > which is already used and uncheck 'Auto Generate password'. > # Provide password and then click on 'Activate Self Service User' button. > h2. Expected Behaviour > Should throw validation, "Username is already taken". > h2. Actual Behaviour > No validation message is displaying and if we check the network, it is > showing 500 internal server error. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-802) The client can have two or more different usernames to login as self service user
[ https://issues.apache.org/jira/browse/FINERACT-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982256#comment-16982256 ] Santosh Math commented on FINERACT-802: --- [~kakoma], Could you please look into this issue? > The client can have two or more different usernames to login as self service > user > -- > > Key: FINERACT-802 > URL: https://issues.apache.org/jira/browse/FINERACT-802 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Priority: Major > Labels: GCI-2019, p1 > Fix For: 1.4.0 > > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide unique > username. > # Provide password and then click on 'Activate Self Service User' button. > # Again in 'More' menu, click on 'Create Self Service user' and follow 3rd > and 4th steps( this time give different username). > h2. Expected Behaviour > Application allows to create two user ids for the same client. > h2. Actual Behaviour > It should throw validation "Self Service User Id is already created. Go to > Admin->Users to edit or delete the self-service user." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-802) The client can have two or more different usernames to login as self service user
[ https://issues.apache.org/jira/browse/FINERACT-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-802: -- Description: h2. Steps to Reproduce # Go to client page> click on 'More' button. # In 'More' menu, click on 'Create Self Service user' # In next navigation page - create self service user page - provide unique username. # Provide password and then click on 'Activate Self Service User' button. # Again in 'More' menu, click on 'Create Self Service user' and follow 3rd and 4th steps( this time give different username). h2. Expected Behaviour Application allows to create two user ids for the same client. h2. Actual Behaviour It should throw validation "Self Service User Id is already created. Go to Admin->Users to edit or delete the self-service user." was: h2. Steps to Reproduce # Go to client page> click on 'More' button. # In 'More' menu, click on 'Create Self Service user' # In next navigation page - create self service user page - provide unique username. # Provide password and then click on 'Activate Self Service User' button. # Again in 'More' menu, click on 'Create Self Service user' and follow 3rd and 4th steps. h2. Expected Behaviour Application allows to create two user ids for the same client. h2. Actual Behaviour It should throw validation "Self Service User Id is already created. Go to Admin->Users to edit or delete the self-service user." > The client can have two or more different usernames to login as self service > user > -- > > Key: FINERACT-802 > URL: https://issues.apache.org/jira/browse/FINERACT-802 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Priority: Major > Labels: GCI-2019, p1 > Fix For: 1.4.0 > > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide unique > username. > # Provide password and then click on 'Activate Self Service User' button. > # Again in 'More' menu, click on 'Create Self Service user' and follow 3rd > and 4th steps( this time give different username). > h2. Expected Behaviour > Application allows to create two user ids for the same client. > h2. Actual Behaviour > It should throw validation "Self Service User Id is already created. Go to > Admin->Users to edit or delete the self-service user." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-802) The client can have two or more different usernames to login as self service user
[ https://issues.apache.org/jira/browse/FINERACT-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-802: -- Summary: The client can have two or more different usernames to login as self service user (was: The client can have two different usernames to login as self service user) > The client can have two or more different usernames to login as self service > user > -- > > Key: FINERACT-802 > URL: https://issues.apache.org/jira/browse/FINERACT-802 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Priority: Major > Labels: GCI-2019, p1 > Fix For: 1.4.0 > > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide unique > username. > # Provide password and then click on 'Activate Self Service User' button. > # Again in 'More' menu, click on 'Create Self Service user' and follow 3rd > and 4th steps. > h2. Expected Behaviour > Application allows to create two user ids for the same client. > h2. Actual Behaviour > It should throw validation "Self Service User Id is already created. Go to > Admin->Users to edit or delete the self-service user." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-803) No validation(500 Internal Server Error) if we use username which is already taken
[ https://issues.apache.org/jira/browse/FINERACT-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-803: -- Labels: GCI-2019 p1 volunteers (was: GCI-2019 p1) > No validation(500 Internal Server Error) if we use username which is already > taken > -- > > Key: FINERACT-803 > URL: https://issues.apache.org/jira/browse/FINERACT-803 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Priority: Major > Labels: GCI-2019, p1, volunteers > Fix For: 1.4.0 > > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide username > which is already used and uncheck 'Auto Generate password'. > # Provide password and then click on 'Activate Self Service User' button. > h2. Expected Behaviour > Should throw validation, "Username is already taken". > h2. Actual Behaviour > No validation message is displaying and if we check the network, it is > showing 500 internal server error. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-803) No validation(500 Internal Server Error) if we use username which is already taken
[ https://issues.apache.org/jira/browse/FINERACT-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982233#comment-16982233 ] Santosh Math commented on FINERACT-803: --- Related ticket: https://issues.apache.org/jira/browse/FINERACT-787 > No validation(500 Internal Server Error) if we use username which is already > taken > -- > > Key: FINERACT-803 > URL: https://issues.apache.org/jira/browse/FINERACT-803 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Priority: Major > Labels: GCI-2019, p1 > Fix For: 1.4.0 > > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide username > which is already used and uncheck 'Auto Generate password'. > # Provide password and then click on 'Activate Self Service User' button. > h2. Expected Behaviour > Should throw validation, "Username is already taken". > h2. Actual Behaviour > No validation message is displaying and if we check the network, it is > showing 500 internal server error. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-803) No validation(500 Internal Server Error) if we use username which is already taken
Santosh Math created FINERACT-803: - Summary: No validation(500 Internal Server Error) if we use username which is already taken Key: FINERACT-803 URL: https://issues.apache.org/jira/browse/FINERACT-803 Project: Apache Fineract Issue Type: Bug Components: Client Affects Versions: 1.4.0 Reporter: Santosh Math Fix For: 1.4.0 h2. Steps to Reproduce # Go to client page> click on 'More' button. # In 'More' menu, click on 'Create Self Service user' # In next navigation page - create self service user page - provide username which is already used and uncheck 'Auto Generate password'. # Provide password and then click on 'Activate Self Service User' button. h2. Expected Behaviour Should throw validation, "Username is already taken". h2. Actual Behaviour No validation message is displaying and if we check the network, it is showing 500 internal server error. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-802) The client can have two different usernames to login as self service user
[ https://issues.apache.org/jira/browse/FINERACT-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982229#comment-16982229 ] Santosh Math commented on FINERACT-802: --- The related ticket: https://issues.apache.org/jira/browse/FINERACT-787 > The client can have two different usernames to login as self service user > - > > Key: FINERACT-802 > URL: https://issues.apache.org/jira/browse/FINERACT-802 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Priority: Major > Labels: GCI-2019, p1 > Fix For: 1.4.0 > > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide unique > username. > # Provide password and then click on 'Activate Self Service User' button. > # Again in 'More' menu, click on 'Create Self Service user' and follow 3rd > and 4th steps. > h2. Expected Behaviour > Application allows to create two user ids for the same client. > h2. Actual Behaviour > It should throw validation "Self Service User Id is already created. Go to > Admin->Users to edit or delete the self-service user." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-802) The client can have two different usernames to login as self service user
[ https://issues.apache.org/jira/browse/FINERACT-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-802: -- External issue URL: https://issues.apache.org/jira/browse/FINERACT-787 > The client can have two different usernames to login as self service user > - > > Key: FINERACT-802 > URL: https://issues.apache.org/jira/browse/FINERACT-802 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Priority: Major > Labels: GCI-2019, p1 > Fix For: 1.4.0 > > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide unique > username. > # Provide password and then click on 'Activate Self Service User' button. > # Again in 'More' menu, click on 'Create Self Service user' and follow 3rd > and 4th steps. > h2. Expected Behaviour > Application allows to create two user ids for the same client. > h2. Actual Behaviour > It should throw validation "Self Service User Id is already created. Go to > Admin->Users to edit or delete the self-service user." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-802) The client can have two different usernames to login as self service user
Santosh Math created FINERACT-802: - Summary: The client can have two different usernames to login as self service user Key: FINERACT-802 URL: https://issues.apache.org/jira/browse/FINERACT-802 Project: Apache Fineract Issue Type: Bug Components: Client Affects Versions: 1.4.0 Reporter: Santosh Math Fix For: 1.4.0 h2. Steps to Reproduce # Go to client page> click on 'More' button. # In 'More' menu, click on 'Create Self Service user' # In next navigation page - create self service user page - provide unique username. # Provide password and then click on 'Activate Self Service User' button. # Again in 'More' menu, click on 'Create Self Service user' and follow 3rd and 4th steps. h2. Expected Behaviour Application allows to create two user ids for the same client. h2. Actual Behaviour It should throw validation "Self Service User Id is already created. Go to Admin->Users to edit or delete the self-service user." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-802) The client can have two different usernames to login as self service user
[ https://issues.apache.org/jira/browse/FINERACT-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-802: -- External issue URL: (was: https://issues.apache.org/jira/browse/FINERACT-787) > The client can have two different usernames to login as self service user > - > > Key: FINERACT-802 > URL: https://issues.apache.org/jira/browse/FINERACT-802 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.4.0 >Reporter: Santosh Math >Priority: Major > Labels: GCI-2019, p1 > Fix For: 1.4.0 > > > h2. Steps to Reproduce > # Go to client page> click on 'More' button. > # In 'More' menu, click on 'Create Self Service user' > # In next navigation page - create self service user page - provide unique > username. > # Provide password and then click on 'Activate Self Service User' button. > # Again in 'More' menu, click on 'Create Self Service user' and follow 3rd > and 4th steps. > h2. Expected Behaviour > Application allows to create two user ids for the same client. > h2. Actual Behaviour > It should throw validation "Self Service User Id is already created. Go to > Admin->Users to edit or delete the self-service user." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-752) savings interest, posting wrong interest amount when savings-interest-posting-current-period-end is enable
[ https://issues.apache.org/jira/browse/FINERACT-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-752: -- Fix Version/s: (was: 1.4.0) 1.5.0 > savings interest, posting wrong interest amount when > savings-interest-posting-current-period-end is enable > > > Key: FINERACT-752 > URL: https://issues.apache.org/jira/browse/FINERACT-752 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.3.1 >Reporter: andrewDzakpasu >Assignee: Ed Cable >Priority: Critical > Labels: p1 > Fix For: 1.5.0 > > Attachments: fineract79.png, fineract80.png > > Time Spent: 40m > Remaining Estimate: 0h > > When savings-interest-posting-current-period-end is enable the amount of > interest posted is twice the amount when > savings-interest-posting-current-period-end is disabled. > > i was able to replicate this on these two accounts > 1.[https://staging.openmf.org/#/viewsavingaccount/79] when > savings-interest-posting-current-period-end is disable > 2.[https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]80 > savings-interest-posting-current-period-end is enable. > > > To replicate. > # create a savings account with voluntary product with withdrawal fee of 300 > # opening balance 20013 activation date 1-03-2019 > # approve and activate 1-03-2019 > # post interest on 25-03-2019 > # make a withdrawal of 19500 on 26-03-2019 > # you will notice the interest posting total amounts to 296 on > [https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]80 > which is wrong > # whilst on > [https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]79 > the amount is 187 which is correct . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-767) Batch Repayment for Loan
[ https://issues.apache.org/jira/browse/FINERACT-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16976316#comment-16976316 ] Santosh Math edited comment on FINERACT-767 at 11/18/19 6:37 AM: - [~mohitsinha], Could you provide clear description and PR sent for this ticket? was (Author: santoshmath): [~mohitsinha], Could you provide clear description? > Batch Repayment for Loan > > > Key: FINERACT-767 > URL: https://issues.apache.org/jira/browse/FINERACT-767 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan >Affects Versions: 1.4.0 >Reporter: Mohit Sinha >Assignee: Mohit Sinha >Priority: Major > Fix For: 1.4.0 > > > There is already a make Repayment Api on Mifos. > This API should also be available while making batch requests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-767) Batch Repayment for Loan
[ https://issues.apache.org/jira/browse/FINERACT-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16976316#comment-16976316 ] Santosh Math commented on FINERACT-767: --- [~mohitsinha], Could you provide clear description? > Batch Repayment for Loan > > > Key: FINERACT-767 > URL: https://issues.apache.org/jira/browse/FINERACT-767 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan >Affects Versions: 1.4.0 >Reporter: Mohit Sinha >Assignee: Mohit Sinha >Priority: Major > Fix For: 1.4.0 > > > There is already a make Repayment Api on Mifos. > This API should also be available while making batch requests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FINERACT-706) Payments switch integration
[ https://issues.apache.org/jira/browse/FINERACT-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-706. - > Payments switch integration > > > Key: FINERACT-706 > URL: https://issues.apache.org/jira/browse/FINERACT-706 > Project: Apache Fineract > Issue Type: New Feature > Components: Accounting >Affects Versions: 1.3.0 >Reporter: James Dailey >Priority: Major > Labels: features > Fix For: 1.4.0 > > Time Spent: 40m > Remaining Estimate: 0h > > This is a ticket to cover the new requirements from integration with a > payment switching solution, using best practices in a push-payment real-time > environment. > [https://lists.apache.org/thread.html/fa8f745cd7228a8f8418561ddadc715a3388d01656bcbc28680f86f2@%3Cdev.fineract.apache.org%3E] > > Basically, there are a few minor changes are needed to fineract1.x to support > integration with a payments hub. The payments hub will handle most of the > functionality, so the changes to fineract1.x are to be minimal. > A new package will be created with new API endpoints. > The functional requirements will include: > * Get a quote > * Hold funds > * Send funds (confirmed ) > Assuming customers are authenticated and using a front end solution, in the > payments flow, end users (payors) get a "Request for Payment" (RfP) from a > Payee and after getting a quote for the cost of that payment, they do a > Payment Initiation. When they initiate the payment their checking/savings > account shows an entry which is debit-amount-on-hold. > There is a further requirement around lookup values - where a new "secondary > ID" is needed in the account table. That secondary ID is used for the > routing address of the payee. > To further explain the intent, imagine a payments switch between two > instances of fineract, the switch or "interoperable service for transfers" > (IST) talks over APIs to a thin "Payments Hub" on the fineract > infrastructure. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (FINERACT-795) Loan Account is not showing Interest value after some payments
[ https://issues.apache.org/jira/browse/FINERACT-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math reopened FINERACT-795: --- > Loan Account is not showing Interest value after some payments > -- > > Key: FINERACT-795 > URL: https://issues.apache.org/jira/browse/FINERACT-795 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.3.1 >Reporter: Santosh Math >Priority: Critical > Labels: p1 > Fix For: 1.4.0 > > > Create a loan account with following details: > |Repayment Strategy|Penalties, Fees, Interest, Principal order| > |Repayments|30 every 1 Days| > |Amortization|Equal installments| > |Equal Amortization|false| > |Interest|240 per annum (20% Per month) - Flat| > |Interest Calculation Period|Daily/Same As repayment| > |Allow Partial Interest Calculation with same as repayment|false| > |Interest Type|Flat| > |Recalculate Interest|No| > |Days in year|Actual| > |Days in month|Actual| > After 20th instalment, The interest is showing as zero. Please check here: > https://staging.openmf.org/#/viewloanaccount/39 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FINERACT-795) Loan Account is not showing Interest value after some payments
[ https://issues.apache.org/jira/browse/FINERACT-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-795. - Resolution: Not A Problem > Loan Account is not showing Interest value after some payments > -- > > Key: FINERACT-795 > URL: https://issues.apache.org/jira/browse/FINERACT-795 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.3.1 >Reporter: Santosh Math >Priority: Critical > Labels: p1 > > Create a loan account with following details: > |Repayment Strategy|Penalties, Fees, Interest, Principal order| > |Repayments|30 every 1 Days| > |Amortization|Equal installments| > |Equal Amortization|false| > |Interest|240 per annum (20% Per month) - Flat| > |Interest Calculation Period|Daily/Same As repayment| > |Allow Partial Interest Calculation with same as repayment|false| > |Interest Type|Flat| > |Recalculate Interest|No| > |Days in year|Actual| > |Days in month|Actual| > After 20th instalment, The interest is showing as zero. Please check here: > https://staging.openmf.org/#/viewloanaccount/39 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-795) Loan Account is not showing Interest value after some payments
[ https://issues.apache.org/jira/browse/FINERACT-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-795: -- Fix Version/s: (was: 1.4.0) > Loan Account is not showing Interest value after some payments > -- > > Key: FINERACT-795 > URL: https://issues.apache.org/jira/browse/FINERACT-795 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.3.1 >Reporter: Santosh Math >Priority: Critical > Labels: p1 > > Create a loan account with following details: > |Repayment Strategy|Penalties, Fees, Interest, Principal order| > |Repayments|30 every 1 Days| > |Amortization|Equal installments| > |Equal Amortization|false| > |Interest|240 per annum (20% Per month) - Flat| > |Interest Calculation Period|Daily/Same As repayment| > |Allow Partial Interest Calculation with same as repayment|false| > |Interest Type|Flat| > |Recalculate Interest|No| > |Days in year|Actual| > |Days in month|Actual| > After 20th instalment, The interest is showing as zero. Please check here: > https://staging.openmf.org/#/viewloanaccount/39 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FINERACT-615) Throwing 500 internal server error, if we try to upload documents when Amazon S3 is enabled.
[ https://issues.apache.org/jira/browse/FINERACT-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-615. - Resolution: Not A Problem > Throwing 500 internal server error, if we try to upload documents when > Amazon S3 is enabled. > - > > Key: FINERACT-615 > URL: https://issues.apache.org/jira/browse/FINERACT-615 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: gsoc, p1 > > Not able to upload following documents and throwing 500 internal server > error in the following cases: > > # Client Documents( Find tab in any client's page) > # Client picture/photo( On right side of clients page) > # Client's signature(Go to 'More' on Client's page > # Loan Documents (Find the tab on any active loan) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (FINERACT-615) Throwing 500 internal server error, if we try to upload documents when Amazon S3 is enabled.
[ https://issues.apache.org/jira/browse/FINERACT-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math reopened FINERACT-615: --- > Throwing 500 internal server error, if we try to upload documents when > Amazon S3 is enabled. > - > > Key: FINERACT-615 > URL: https://issues.apache.org/jira/browse/FINERACT-615 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: gsoc, p1 > > Not able to upload following documents and throwing 500 internal server > error in the following cases: > > # Client Documents( Find tab in any client's page) > # Client picture/photo( On right side of clients page) > # Client's signature(Go to 'More' on Client's page > # Loan Documents (Find the tab on any active loan) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-615) Throwing 500 internal server error, if we try to upload documents when Amazon S3 is enabled.
[ https://issues.apache.org/jira/browse/FINERACT-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-615: -- Fix Version/s: (was: 1.4.0) > Throwing 500 internal server error, if we try to upload documents when > Amazon S3 is enabled. > - > > Key: FINERACT-615 > URL: https://issues.apache.org/jira/browse/FINERACT-615 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: gsoc, p1 > > Not able to upload following documents and throwing 500 internal server > error in the following cases: > > # Client Documents( Find tab in any client's page) > # Client picture/photo( On right side of clients page) > # Client's signature(Go to 'More' on Client's page > # Loan Documents (Find the tab on any active loan) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (FINERACT-615) Throwing 500 internal server error, if we try to upload documents when Amazon S3 is enabled.
[ https://issues.apache.org/jira/browse/FINERACT-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math reopened FINERACT-615: --- > Throwing 500 internal server error, if we try to upload documents when > Amazon S3 is enabled. > - > > Key: FINERACT-615 > URL: https://issues.apache.org/jira/browse/FINERACT-615 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: gsoc, p1 > Fix For: 1.4.0 > > > Not able to upload following documents and throwing 500 internal server > error in the following cases: > > # Client Documents( Find tab in any client's page) > # Client picture/photo( On right side of clients page) > # Client's signature(Go to 'More' on Client's page > # Loan Documents (Find the tab on any active loan) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FINERACT-615) Throwing 500 internal server error, if we try to upload documents when Amazon S3 is enabled.
[ https://issues.apache.org/jira/browse/FINERACT-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-615. - Resolution: Fixed > Throwing 500 internal server error, if we try to upload documents when > Amazon S3 is enabled. > - > > Key: FINERACT-615 > URL: https://issues.apache.org/jira/browse/FINERACT-615 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: gsoc, p1 > > Not able to upload following documents and throwing 500 internal server > error in the following cases: > > # Client Documents( Find tab in any client's page) > # Client picture/photo( On right side of clients page) > # Client's signature(Go to 'More' on Client's page > # Loan Documents (Find the tab on any active loan) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-594) Recent Transactions Only Displays Charges, It should show savings and loan transitions too
[ https://issues.apache.org/jira/browse/FINERACT-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16976307#comment-16976307 ] Santosh Math edited comment on FINERACT-594 at 11/18/19 6:27 AM: - Recent Transactions is not showing any transactions , even those transactions made on current date. was (Author: santoshmath): Recent Transactions is not showing any transactions , even those transactions made current date. > Recent Transactions Only Displays Charges, It should show savings and loan > transitions too > --- > > Key: FINERACT-594 > URL: https://issues.apache.org/jira/browse/FINERACT-594 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Charges, Loan, Savings >Affects Versions: 1.0.0 >Reporter: Rajan Maurya >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, GSOC, Volunteer, easyfix, enha, patch > Fix For: 1.5.0 > > Original Estimate: 96h > Remaining Estimate: 96h > > Recent Transactions of the self-service user Only Displays Charges but It > should show savings and loan transitions too. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-594) Recent Transactions Only Displays Charges, It should show savings and loan transitions too
[ https://issues.apache.org/jira/browse/FINERACT-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-594: -- Fix Version/s: (was: 1.4.0) 1.5.0 > Recent Transactions Only Displays Charges, It should show savings and loan > transitions too > --- > > Key: FINERACT-594 > URL: https://issues.apache.org/jira/browse/FINERACT-594 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Charges, Loan, Savings >Affects Versions: 1.0.0 >Reporter: Rajan Maurya >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, GSOC, Volunteer, easyfix, enha, patch > Fix For: 1.5.0 > > Original Estimate: 96h > Remaining Estimate: 96h > > Recent Transactions of the self-service user Only Displays Charges but It > should show savings and loan transitions too. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-594) Recent Transactions Only Displays Charges, It should show savings and loan transitions too
[ https://issues.apache.org/jira/browse/FINERACT-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16976307#comment-16976307 ] Santosh Math commented on FINERACT-594: --- Recent Transactions is not showing any transactions , even those transactions made current date. > Recent Transactions Only Displays Charges, It should show savings and loan > transitions too > --- > > Key: FINERACT-594 > URL: https://issues.apache.org/jira/browse/FINERACT-594 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Charges, Loan, Savings >Affects Versions: 1.0.0 >Reporter: Rajan Maurya >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, GSOC, Volunteer, easyfix, enha, patch > Fix For: 1.4.0 > > Original Estimate: 96h > Remaining Estimate: 96h > > Recent Transactions of the self-service user Only Displays Charges but It > should show savings and loan transitions too. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-677) Hide Sensitive contents in xml files and logs
[ https://issues.apache.org/jira/browse/FINERACT-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-677: -- Fix Version/s: (was: 1.4.0) 1.5.0 > Hide Sensitive contents in xml files and logs > - > > Key: FINERACT-677 > URL: https://issues.apache.org/jira/browse/FINERACT-677 > Project: Apache Fineract > Issue Type: Bug > Environment: All environments, Linux/Unix and Windows. >Reporter: ApacheSF User >Priority: Major > Labels: 2019-mifos-gsoc, p1 > Fix For: 1.5.0 > > > This is an issue explaining about hiding sensitive issues in xml files. > These files include. > Usernames & passwords in: > tomcat/conf/server.xml > Mifos system username and password are visible in : > tomcat/logs/localhost_access_log.2018-12-07 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-791) Transfer of fund from saving balance to shares
[ https://issues.apache.org/jira/browse/FINERACT-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-791: -- Fix Version/s: (was: 1.3.1) 1.5.0 > Transfer of fund from saving balance to shares > -- > > Key: FINERACT-791 > URL: https://issues.apache.org/jira/browse/FINERACT-791 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings, Shares >Affects Versions: 1.0.0 >Reporter: Mexina Daniel >Assignee: Mexina Daniel >Priority: Major > Labels: p1 > Fix For: 1.5.0 > > > This improvement will enable to use saving balance to purchase a share > through the feature of transfer fund. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FINERACT-695) Fix bug in generating notification.
[ https://issues.apache.org/jira/browse/FINERACT-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-695. - > Fix bug in generating notification. > --- > > Key: FINERACT-695 > URL: https://issues.apache.org/jira/browse/FINERACT-695 > Project: Apache Fineract > Issue Type: Bug > Components: System >Reporter: Santosh Math >Priority: Major > Labels: p1 > Fix For: 1.4.0 > > > When querying the users required to get a notification, add new topic > subscribers > to the current set of subscribers, instead of replacing the currents set of > subscribers > with the new topic subscribers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-615) Throwing 500 internal server error, if we try to upload documents when Amazon S3 is enabled.
[ https://issues.apache.org/jira/browse/FINERACT-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16971297#comment-16971297 ] Santosh Math commented on FINERACT-615: --- Closed. > Throwing 500 internal server error, if we try to upload documents when > Amazon S3 is enabled. > - > > Key: FINERACT-615 > URL: https://issues.apache.org/jira/browse/FINERACT-615 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: gsoc, p1 > Fix For: 1.4.0 > > > Not able to upload following documents and throwing 500 internal server > error in the following cases: > > # Client Documents( Find tab in any client's page) > # Client picture/photo( On right side of clients page) > # Client's signature(Go to 'More' on Client's page > # Loan Documents (Find the tab on any active loan) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FINERACT-615) Throwing 500 internal server error, if we try to upload documents when Amazon S3 is enabled.
[ https://issues.apache.org/jira/browse/FINERACT-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-615. - Resolution: Not A Problem > Throwing 500 internal server error, if we try to upload documents when > Amazon S3 is enabled. > - > > Key: FINERACT-615 > URL: https://issues.apache.org/jira/browse/FINERACT-615 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: gsoc, p1 > Fix For: 1.4.0 > > > Not able to upload following documents and throwing 500 internal server > error in the following cases: > > # Client Documents( Find tab in any client's page) > # Client picture/photo( On right side of clients page) > # Client's signature(Go to 'More' on Client's page > # Loan Documents (Find the tab on any active loan) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-784) Description Field while creating share product should not be mandatory
[ https://issues.apache.org/jira/browse/FINERACT-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-784: -- Labels: GCI-2019 (was: ) > Description Field while creating share product should not be mandatory > -- > > Key: FINERACT-784 > URL: https://issues.apache.org/jira/browse/FINERACT-784 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Affects Versions: 1.3.1 >Reporter: Santosh Math >Priority: Minor > Labels: GCI-2019 > Fix For: 1.4.0 > > > Go to Admin>Products>Share Products and click on 'Create Share Product'. > In create page, Description field is mandatory. It shouldn't be. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-784) Description Field while creating share product should not be mandatory
[ https://issues.apache.org/jira/browse/FINERACT-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-784: -- Labels: GCI-2019 p1 (was: GCI-2019) > Description Field while creating share product should not be mandatory > -- > > Key: FINERACT-784 > URL: https://issues.apache.org/jira/browse/FINERACT-784 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Affects Versions: 1.3.1 >Reporter: Santosh Math >Priority: Minor > Labels: GCI-2019, p1 > Fix For: 1.4.0 > > > Go to Admin>Products>Share Products and click on 'Create Share Product'. > In create page, Description field is mandatory. It shouldn't be. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FINERACT-795) Loan Account is not showing Interest value after some payments
[ https://issues.apache.org/jira/browse/FINERACT-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-795. - Resolution: Not A Problem > Loan Account is not showing Interest value after some payments > -- > > Key: FINERACT-795 > URL: https://issues.apache.org/jira/browse/FINERACT-795 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.3.1 >Reporter: Santosh Math >Priority: Critical > Labels: p1 > Fix For: 1.4.0 > > > Create a loan account with following details: > |Repayment Strategy|Penalties, Fees, Interest, Principal order| > |Repayments|30 every 1 Days| > |Amortization|Equal installments| > |Equal Amortization|false| > |Interest|240 per annum (20% Per month) - Flat| > |Interest Calculation Period|Daily/Same As repayment| > |Allow Partial Interest Calculation with same as repayment|false| > |Interest Type|Flat| > |Recalculate Interest|No| > |Days in year|Actual| > |Days in month|Actual| > After 20th instalment, The interest is showing as zero. Please check here: > https://staging.openmf.org/#/viewloanaccount/39 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-225) If Loan rescheduling page is submitted with out checking any checkboxes then error message displayed is not proper
[ https://issues.apache.org/jira/browse/FINERACT-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-225: -- Labels: 2019-mifos-gsoc GCI-2019 Volunteer gsoc p2 (was: 2019-mifos-gsoc Volunteer gsoc p2) > If Loan rescheduling page is submitted with out checking any checkboxes then > error message displayed is not proper > -- > > Key: FINERACT-225 > URL: https://issues.apache.org/jira/browse/FINERACT-225 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Markus Geiss >Priority: Minor > Labels: 2019-mifos-gsoc, GCI-2019, Volunteer, gsoc, p2 > Fix For: 1.5.0 > > Attachments: Reschedule loan.png > > > Error message displayed as > "validation.msg.rescheduleloan.graceOnPrincipal.cannot.be.blank" if no check > box is checked. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-274) Not able to create the same datatable which was rejected by the maker checker before
[ https://issues.apache.org/jira/browse/FINERACT-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-274: -- Labels: 2019-mifos-gsoc GCI-2019 gsoc p2 verify (was: 2019-mifos-gsoc Volunteer gci gsoc p2 verify) > Not able to create the same datatable which was rejected by the maker checker > before > > > Key: FINERACT-274 > URL: https://issues.apache.org/jira/browse/FINERACT-274 > Project: Apache Fineract > Issue Type: Bug > Components: Data Tables >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: 2019-mifos-gsoc, GCI-2019, gsoc, p2, verify > Fix For: 1.4.0 > > Attachments: JIRA-274.JPG > > > Posted by Subramanya at [https://mifosforge.jira.com/browse/MIFOSX-1246] > Original Description: > 1. Click on Admin ->System - enable maker-checker. > 2. Click on Admin ->System - Configure maker-checker tasks -> Select > Configurations ->select check box for create, update and delete data tables. > 3. Click on the Admin -> System -> Manage data tables -> Create data table - > and create data table for client. > 4. The navigated page displays "Waiting For Checker Approval" -> Click on > details -> Click on reject button in "View Checker Inbox" -> click on confirm > in confirmation page. > With the above action in UI the data table will not appear, but in the > database the table is still exist. > > Again try to create datable with the same name as above, which displays > error message as the data table already exists, -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (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:all-tabpanel ] Santosh Math updated FINERACT-520: -- Labels: 2019-mifos-gsoc Volunteer client gsoc p2 (was: 2019-mifos-gsoc Volunteer client gci gsoc p2) > 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: 2019-mifos-gsoc, Volunteer, client, gsoc, p2 > Fix For: 1.5.0 > > > 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 (v8.3.4#803005)
[jira] [Updated] (FINERACT-580) Dashboard summary
[ https://issues.apache.org/jira/browse/FINERACT-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-580: -- Labels: GSOC p1 (was: GSOC gci p1) > Dashboard summary > - > > Key: FINERACT-580 > URL: https://issues.apache.org/jira/browse/FINERACT-580 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.2.0 >Reporter: sangamesh >Assignee: Markus Geiss >Priority: Major > Labels: GSOC, p1 > Fix For: 1.5.0 > > > Dashboard summary- Dashboard is not working as expected it doesn't show's up > the values. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-463) Dashboard showing no data for 'Amount Collected for Today' even though there are transactions today
[ https://issues.apache.org/jira/browse/FINERACT-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-463: -- Labels: 2019-mifos-gsoc GSOC Volunteer community-app p1 verify (was: 2019-mifos-gsoc GSOC Volunteer community-app gci p1 verify) > Dashboard showing no data for 'Amount Collected for Today' even though there > are transactions today > - > > Key: FINERACT-463 > URL: https://issues.apache.org/jira/browse/FINERACT-463 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, GSOC, Volunteer, community-app, p1, > verify > Fix For: 1.4.0 > > Attachments: dashboard.png > > > Reported by Onyedikachi Nwosu > 1. Create a new office and create a client under the new office. > 2. perform a deposit of 10,000 to a savings account and issued a loan to the > value of 10,000 for the same client. > As can be seen from the attached screenshot, On the dashboard, Amount > Disbursed for Today reflects the 10,000 loan, but the Amount Collected for > Today does not reflect 10,000 savings made. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-661) Not able to import Savings, FD and RD transactions
[ https://issues.apache.org/jira/browse/FINERACT-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-661: -- Labels: (was: GCI-2019) > Not able to import Savings, FD and RD transactions > -- > > Key: FINERACT-661 > URL: https://issues.apache.org/jira/browse/FINERACT-661 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.1.0 >Reporter: Mexina Daniel >Priority: Major > > When account number preference is enable for a saving account, during > download of Saving/Fixed deposit/Recurring deposit transactions, the system > bring an error > *Whitelabel Error Page > This application has no explicit mapping for /error, so you are seeing this > as a fallback. > Tue Nov 06 12:11:50 EAT 2018 > There was an unexpected error (type=Internal Server Error, status=500). > For input string: "CS00094" > * -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-661) Not able to import Savings, FD and RD transactions
[ https://issues.apache.org/jira/browse/FINERACT-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-661: -- Labels: GCI-2019 (was: ) > Not able to import Savings, FD and RD transactions > -- > > Key: FINERACT-661 > URL: https://issues.apache.org/jira/browse/FINERACT-661 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.1.0 >Reporter: Mexina Daniel >Priority: Major > Labels: GCI-2019 > > When account number preference is enable for a saving account, during > download of Saving/Fixed deposit/Recurring deposit transactions, the system > bring an error > *Whitelabel Error Page > This application has no explicit mapping for /error, so you are seeing this > as a fallback. > Tue Nov 06 12:11:50 EAT 2018 > There was an unexpected error (type=Internal Server Error, status=500). > For input string: "CS00094" > * -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-689) Able to Create Fixed Deposit/Recurring Deposit product without adding Interest Rate Chart
[ https://issues.apache.org/jira/browse/FINERACT-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-689: -- Labels: GCI-2019 (was: 2019-mifos-gsoc GSOC Volunteer p1) > Able to Create Fixed Deposit/Recurring Deposit product without adding > Interest Rate Chart > -- > > Key: FINERACT-689 > URL: https://issues.apache.org/jira/browse/FINERACT-689 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.2.0 >Reporter: Santosh Math >Priority: Critical > Labels: GCI-2019 > Fix For: 1.4.0 > > Time Spent: 50m > Remaining Estimate: 0h > > 1) Go to Admin>Products and select either Fixed Deposit Products or Recurring > Deposit Products and then click on Create Fixed Deposit Product/Recurring > Deposit Product. > 2) Give all mandatory inputs and under 'Interest Rate Chart' provide 'Valid > From Date' and then just submit it without adding interest rate. > > Able to Submit and create FD/RD product without interest rate chart. > Expected: Validation should be thrown 'Interest Rate is not added' , once > submit button is hit. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-701) In Individual Collection sheet and Collection Sheet, Not able to select previous year dates(2018) through date picker.
[ https://issues.apache.org/jira/browse/FINERACT-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-701: -- Labels: GCI-2019 gsoc (was: GSOC Volunteer review) > In Individual Collection sheet and Collection Sheet, Not able to select > previous year dates(2018) through date picker. > -- > > Key: FINERACT-701 > URL: https://issues.apache.org/jira/browse/FINERACT-701 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Critical > Labels: GCI-2019, gsoc > Fix For: 1.4.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-749) Client family member date of birth min value set to current year
[ https://issues.apache.org/jira/browse/FINERACT-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-749: -- Labels: GCI-2019 (was: ) > Client family member date of birth min value set to current year > > > Key: FINERACT-749 > URL: https://issues.apache.org/jira/browse/FINERACT-749 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.3.1 >Reporter: Sidhant Gupta >Priority: Major > Labels: GCI-2019 > Fix For: 1.5.0 > > > The date of birth value for client family member cannot be set to less than > the first date of the current year. It can be fixed by modifying the input > tag's `min` attribute. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-794) Integrate open banking APIs into interoperability layer
[ https://issues.apache.org/jira/browse/FINERACT-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-794: -- Labels: (was: GCI-2019) > Integrate open banking APIs into interoperability layer > --- > > Key: FINERACT-794 > URL: https://issues.apache.org/jira/browse/FINERACT-794 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Steve Conrad >Assignee: Steve Conrad >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Integrate open banking API functionality into interoperability layer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-794) Integrate open banking APIs into interoperability layer
[ https://issues.apache.org/jira/browse/FINERACT-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-794: -- Labels: GCI-2019 (was: ) > Integrate open banking APIs into interoperability layer > --- > > Key: FINERACT-794 > URL: https://issues.apache.org/jira/browse/FINERACT-794 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Steve Conrad >Assignee: Steve Conrad >Priority: Major > Labels: GCI-2019 > Time Spent: 20m > Remaining Estimate: 0h > > Integrate open banking API functionality into interoperability layer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-631) Allow to specify transfer date when transferring client from one branch to another
[ https://issues.apache.org/jira/browse/FINERACT-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-631: -- Component/s: Client > Allow to specify transfer date when transferring client from one branch to > another > -- > > Key: FINERACT-631 > URL: https://issues.apache.org/jira/browse/FINERACT-631 > Project: Apache Fineract > Issue Type: Improvement > Components: Client >Reporter: Mexina Daniel >Priority: Major > Labels: 2019-mifos-gsoc, gsoc, p2 > Fix For: 1.5.0 > > > Then transferring the client from one branch to another, the system take the > current data and assume its a transfer date, the system should allow a user > to specify, sometimes it might be a back date. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-631) Allow to specify transfer date when transferring client from one branch to another
[ https://issues.apache.org/jira/browse/FINERACT-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-631: -- Fix Version/s: 1.5.0 > Allow to specify transfer date when transferring client from one branch to > another > -- > > Key: FINERACT-631 > URL: https://issues.apache.org/jira/browse/FINERACT-631 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Mexina Daniel >Priority: Major > Labels: 2019-mifos-gsoc, gsoc, p2 > Fix For: 1.5.0 > > > Then transferring the client from one branch to another, the system take the > current data and assume its a transfer date, the system should allow a user > to specify, sometimes it might be a back date. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-795) Loan Account is not showing Interest value after some payments
[ https://issues.apache.org/jira/browse/FINERACT-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-795: -- Summary: Loan Account is not showing Interest value after some payments (was: Loan Account is not showing Interest value after cer) > Loan Account is not showing Interest value after some payments > -- > > Key: FINERACT-795 > URL: https://issues.apache.org/jira/browse/FINERACT-795 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.3.1 >Reporter: Santosh Math >Priority: Critical > Labels: p1 > Fix For: 1.4.0 > > > Create a loan account with following details: > |Repayment Strategy|Penalties, Fees, Interest, Principal order| > |Repayments|30 every 1 Days| > |Amortization|Equal installments| > |Equal Amortization|false| > |Interest|240 per annum (20% Per month) - Flat| > |Interest Calculation Period|Daily/Same As repayment| > |Allow Partial Interest Calculation with same as repayment|false| > |Interest Type|Flat| > |Recalculate Interest|No| > |Days in year|Actual| > |Days in month|Actual| > After 20th instalment, The interest is showing as zero. Please check here: > https://staging.openmf.org/#/viewloanaccount/39 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel=16953673#comment-16953673 ] Santosh Math commented on FINERACT-652: --- [~edcable], This ticket needs to be assigned to someone. > 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: 2019-mifos-gsoc, GSOC, Volunteer, p1 > Fix For: 1.4.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 (v8.3.4#803005)
[jira] [Updated] (FINERACT-657) Enhancement of Standing Instruction dealing with insufficient fund in Savings Account
[ https://issues.apache.org/jira/browse/FINERACT-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-657: -- Labels: p2 (was: ) > Enhancement of Standing Instruction dealing with insufficient fund in > Savings Account > -- > > Key: FINERACT-657 > URL: https://issues.apache.org/jira/browse/FINERACT-657 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan, Savings >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Major > Labels: p2 > Fix For: 1.5.0 > > > (Original Description By Zayyad in mailing list) > Current Behaviour: > If there isn't sufficient funds in the linked savings account, Scheduler jobs > for "Execute Standing Instruction" gets failed. And the repayment doesn't > happen. > Expected Behaviour: > We have had an enquiry before that if the linked savings doesn’t have enough, > then the system should recover the whole amount available in the account and > once the account is credited with any other amount the same is deducted until > the amount due is fully collected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-657) Enhancement of Standing Instruction dealing with insufficient fund in Savings Account
[ https://issues.apache.org/jira/browse/FINERACT-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-657: -- Fix Version/s: 1.5.0 > Enhancement of Standing Instruction dealing with insufficient fund in > Savings Account > -- > > Key: FINERACT-657 > URL: https://issues.apache.org/jira/browse/FINERACT-657 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan, Savings >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Major > Fix For: 1.5.0 > > > (Original Description By Zayyad in mailing list) > Current Behaviour: > If there isn't sufficient funds in the linked savings account, Scheduler jobs > for "Execute Standing Instruction" gets failed. And the repayment doesn't > happen. > Expected Behaviour: > We have had an enquiry before that if the linked savings doesn’t have enough, > then the system should recover the whole amount available in the account and > once the account is credited with any other amount the same is deducted until > the amount due is fully collected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-661) Not able to import Savings, FD and RD transactions
[ https://issues.apache.org/jira/browse/FINERACT-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953628#comment-16953628 ] Santosh Math commented on FINERACT-661: --- [~mexina], Isn't this resolved in latest code base deployed on staging? > Not able to import Savings, FD and RD transactions > -- > > Key: FINERACT-661 > URL: https://issues.apache.org/jira/browse/FINERACT-661 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.1.0 >Reporter: Mexina Daniel >Priority: Major > > When account number preference is enable for a saving account, during > download of Saving/Fixed deposit/Recurring deposit transactions, the system > bring an error > *Whitelabel Error Page > This application has no explicit mapping for /error, so you are seeing this > as a fallback. > Tue Nov 06 12:11:50 EAT 2018 > There was an unexpected error (type=Internal Server Error, status=500). > For input string: "CS00094" > * -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-666) Uploading image ends in errror whereas other files are working just fine
[ https://issues.apache.org/jira/browse/FINERACT-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-666: -- Labels: p2 (was: ) > Uploading image ends in errror whereas other files are working just fine > > > Key: FINERACT-666 > URL: https://issues.apache.org/jira/browse/FINERACT-666 > Project: Apache Fineract > Issue Type: Bug > Components: System >Reporter: Vadi >Priority: Major > Labels: p2 > Fix For: 1.3.0 > > Attachments: image-2018-11-19-20-47-41-475.png > > > Uploading images resulting error `fields is required` not sure what this > means, tried uploading .txt file or .xml file it works fine. Same case with > PDF file as well. > Version: 2304bb49 > !image-2018-11-19-20-47-41-475.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-666) Uploading image ends in errror whereas other files are working just fine
[ https://issues.apache.org/jira/browse/FINERACT-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-666: -- Component/s: System > Uploading image ends in errror whereas other files are working just fine > > > Key: FINERACT-666 > URL: https://issues.apache.org/jira/browse/FINERACT-666 > Project: Apache Fineract > Issue Type: Bug > Components: System >Reporter: Vadi >Priority: Major > Fix For: 1.3.0 > > Attachments: image-2018-11-19-20-47-41-475.png > > > Uploading images resulting error `fields is required` not sure what this > means, tried uploading .txt file or .xml file it works fine. Same case with > PDF file as well. > Version: 2304bb49 > !image-2018-11-19-20-47-41-475.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-666) Uploading image ends in errror whereas other files are working just fine
[ https://issues.apache.org/jira/browse/FINERACT-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-666: -- Fix Version/s: 1.3.0 > Uploading image ends in errror whereas other files are working just fine > > > Key: FINERACT-666 > URL: https://issues.apache.org/jira/browse/FINERACT-666 > Project: Apache Fineract > Issue Type: Bug >Reporter: Vadi >Priority: Major > Fix For: 1.3.0 > > Attachments: image-2018-11-19-20-47-41-475.png > > > Uploading images resulting error `fields is required` not sure what this > means, tried uploading .txt file or .xml file it works fine. Same case with > PDF file as well. > Version: 2304bb49 > !image-2018-11-19-20-47-41-475.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-690) Global configuration to disallow the change of overdue charges on a loan product to affect the already created loans.
[ https://issues.apache.org/jira/browse/FINERACT-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-690: -- Labels: GSoC p1 (was: 2019-mifos-gsoc GSoC) > Global configuration to disallow the change of overdue charges on a loan > product to affect the already created loans. > - > > Key: FINERACT-690 > URL: https://issues.apache.org/jira/browse/FINERACT-690 > Project: Apache Fineract > Issue Type: New Feature > Components: Charges, Loan >Reporter: Mexina Daniel >Priority: Major > Labels: GSoC, p1 > Fix For: 1.5.0 > > > For now when you attach an overdue charge to a loan product which did not > have previously, it affect the active loans that were created without a > penalty. > Am suggesting for the system to have a configuration to allow are disallow > this feature. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-787) Support creation of self-service users
[ https://issues.apache.org/jira/browse/FINERACT-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953605#comment-16953605 ] Santosh Math commented on FINERACT-787: --- [~kakoma], thanks for the PR: https://github.com/apache/fineract/pull/649 > Support creation of self-service users > -- > > Key: FINERACT-787 > URL: https://issues.apache.org/jira/browse/FINERACT-787 > Project: Apache Fineract > Issue Type: New Feature > Components: User Management >Affects Versions: 1.3.0 >Reporter: Peter Kakoma >Assignee: Peter Kakoma >Priority: Minor > Labels: p1 > Time Spent: 10m > Remaining Estimate: 0h > > *Background* > A self-service user is a staff user assigned to a specific role which can > perform certain actions. These users are used to login to the self-service > web and mobile applications. The challenge is that there's no user-friendly > way of creating a self-service user. > > *Where we are now* > There's currently [an open PR > |https://github.com/openMF/community-app/pull/2139]to the community app that > allows the creation of a self-service user. In it, self-service user creation > is done using the same API used to create a back-office user but while > specifying a _self-service role_ in the API call. > First, an API call is made to retrieve all available roles. These roles are > presented to the admin who then selects which one is the self service role. > With the role selected, an API call is made to create the self service user. > > *The problem* > Since the admin is presented with all roles, if they select a wrong role [a > non self-service role], the user will have more/less rights than they ought > to. > > *The proposed solution* > The solution is three-fold > > 1. Create a different template resource in the API which returns only the > self-service related roles. Ref [ > #[https://demo.openmf.org/api-docs/apiLive.htm#users_template]] i.e. Besides > 'availableRoles', add a 'selfServiceRoles' in the returned data > 2. With that done, update the open PR to use `selfServiceRoles` > 3. The API call to create the self-service user is made to a custom > endpoint, POST > [https://DomainName/api/v1/users/self|https://domainname/api/v1/users/self], > that evaluates that the role specified is a self-service role and then > proceeds to create the user. > > This card is to propose that items 1 and 3 are added to the fineract. I'm on > hand to explore implementing the card if this is accepted. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-694) API for Withdrawing Savings Account not available
[ https://issues.apache.org/jira/browse/FINERACT-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953457#comment-16953457 ] Santosh Math commented on FINERACT-694: --- It requires for the support of self-service app. > API for Withdrawing Savings Account not available > - > > Key: FINERACT-694 > URL: https://issues.apache.org/jira/browse/FINERACT-694 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Saksham Handu >Priority: Major > Fix For: 1.4.0 > > > Currently, there is no API for withdrawing Saving Account -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-694) API for Withdrawing Savings Account not available
[ https://issues.apache.org/jira/browse/FINERACT-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-694: -- Component/s: Savings > API for Withdrawing Savings Account not available > - > > Key: FINERACT-694 > URL: https://issues.apache.org/jira/browse/FINERACT-694 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Saksham Handu >Priority: Major > Fix For: 1.4.0 > > > Currently, there is no API for withdrawing Saving Account -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-694) API for Withdrawing Savings Account not available
[ https://issues.apache.org/jira/browse/FINERACT-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-694: -- Fix Version/s: 1.4.0 > API for Withdrawing Savings Account not available > - > > Key: FINERACT-694 > URL: https://issues.apache.org/jira/browse/FINERACT-694 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Saksham Handu >Priority: Major > Fix For: 1.4.0 > > > Currently, there is no API for withdrawing Saving Account -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-701) In Individual Collection sheet and Collection Sheet, Not able to select previous year dates(2018) through date picker.
[ https://issues.apache.org/jira/browse/FINERACT-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953451#comment-16953451 ] Santosh Math commented on FINERACT-701: --- [~sg004] , This is Fineract issue. Please send th PR to https://github.com/apache/fineract/pulls > In Individual Collection sheet and Collection Sheet, Not able to select > previous year dates(2018) through date picker. > -- > > Key: FINERACT-701 > URL: https://issues.apache.org/jira/browse/FINERACT-701 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Critical > Labels: GSOC, Volunteer, review > Fix For: 1.4.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FINERACT-704) Unable to login
[ https://issues.apache.org/jira/browse/FINERACT-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-704. - Resolution: Invalid [~asimpatnaik] ,such concerns should be raised here first : [http://mifos.cloud.answerhub.com/index.html] [https://gitter.im/openMF/mifos] Please subscribe to following channels. > Unable to login > --- > > Key: FINERACT-704 > URL: https://issues.apache.org/jira/browse/FINERACT-704 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Reporter: asim >Priority: Major > > Hi, > We tried installing Mifos X on Ubuntu Server 18.04.2 LTS, the only difference > being that the mysql version was 5.7. We are able to run the tomcat but there > are errors in the log due to mysql version mismatch. We are unable to find > mysql version 5.5 or 5.6. > We referred this url - > https://mifosforge.jira.com/wiki/spaces/docs/pages/74711072/Mifos+X+Installation+on+Linux+-+Ubuntu+Server > Please suggest what can be done. > Regards, > Asim. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-727) Improving the Home Page by adding some Content to it also making navigation drawer look good
[ https://issues.apache.org/jira/browse/FINERACT-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953437#comment-16953437 ] Santosh Math commented on FINERACT-727: --- [~vipinsoni38], Isn't this ticket related to front end? > Improving the Home Page by adding some Content to it also making navigation > drawer look good > > > Key: FINERACT-727 > URL: https://issues.apache.org/jira/browse/FINERACT-727 > Project: Apache Fineract > Issue Type: New Feature > Environment: android studio >Reporter: vipin soni >Priority: Major > Fix For: 1.5.0 > > > As the user logs in the App, there flashes the empty screen with just a card > to create a new user which can be changed to a screen with adding Most used > content in it for better user experience > also the navigation drawer (Hamburger menu) have some same drawable files > changing them to some relatable files -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-727) Improving the Home Page by adding some Content to it also making navigation drawer look good
[ https://issues.apache.org/jira/browse/FINERACT-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-727: -- Fix Version/s: 1.5.0 > Improving the Home Page by adding some Content to it also making navigation > drawer look good > > > Key: FINERACT-727 > URL: https://issues.apache.org/jira/browse/FINERACT-727 > Project: Apache Fineract > Issue Type: New Feature > Environment: android studio >Reporter: vipin soni >Priority: Major > Fix For: 1.5.0 > > > As the user logs in the App, there flashes the empty screen with just a card > to create a new user which can be changed to a screen with adding Most used > content in it for better user experience > also the navigation drawer (Hamburger menu) have some same drawable files > changing them to some relatable files -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-737) Ability to fetch details of charges paid by a loan transaction
[ https://issues.apache.org/jira/browse/FINERACT-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-737: -- Fix Version/s: (was: 1.4.0) 1.5.0 > Ability to fetch details of charges paid by a loan transaction > -- > > Key: FINERACT-737 > URL: https://issues.apache.org/jira/browse/FINERACT-737 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Vishwas Babu A J >Assignee: Angel Cajas >Priority: Major > Labels: gsoc2019 > Fix For: 1.5.0 > > > As a side effect of > [https://github.com/apache/fineract/commit/aaa61695cf27419a2bc9e018fc6e2715512a1094] > , along with the functionality for "Predefined nominal interest rates" > associated with loan products, the ability to fetch the details of charges > paid by a loan transaction have also been added in > [https://github.com/apache/fineract/tree/Fineract-614.] > Details of the relevant code changes and the functionality are present in > comments on github at > [https://github.com/apache/fineract/pull/465#pullrequestreview-212401382.] > To merge the same into our develop branch, the API docs and Integration tests > needs to updated to reflect these changes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-737) Ability to fetch details of charges paid by a loan transaction
[ https://issues.apache.org/jira/browse/FINERACT-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-737: -- Component/s: Loan Charges > Ability to fetch details of charges paid by a loan transaction > -- > > Key: FINERACT-737 > URL: https://issues.apache.org/jira/browse/FINERACT-737 > Project: Apache Fineract > Issue Type: New Feature > Components: Charges, Loan >Reporter: Vishwas Babu A J >Assignee: Angel Cajas >Priority: Major > Labels: gsoc2019 > Fix For: 1.5.0 > > > As a side effect of > [https://github.com/apache/fineract/commit/aaa61695cf27419a2bc9e018fc6e2715512a1094] > , along with the functionality for "Predefined nominal interest rates" > associated with loan products, the ability to fetch the details of charges > paid by a loan transaction have also been added in > [https://github.com/apache/fineract/tree/Fineract-614.] > Details of the relevant code changes and the functionality are present in > comments on github at > [https://github.com/apache/fineract/pull/465#pullrequestreview-212401382.] > To merge the same into our develop branch, the API docs and Integration tests > needs to updated to reflect these changes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-739) Loan (Installment in multiples of) Rounding not working
[ https://issues.apache.org/jira/browse/FINERACT-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-739: -- Fix Version/s: 1.5.0 > Loan (Installment in multiples of) Rounding not working > --- > > Key: FINERACT-739 > URL: https://issues.apache.org/jira/browse/FINERACT-739 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.3.0 >Reporter: Okeleke Mike >Priority: Major > Fix For: 1.5.0 > > Attachments: SS1.png, SS2.png, SS3.png > > > Loan repay schedule is not affected by *Installment in multiples of (IIM)* > setting in Loan Product screen > when you set the IIM to say: 1000, you are expected to have your total > repayments calculated to the nearest 1000 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-739) Loan (Installment in multiples of) Rounding not working
[ https://issues.apache.org/jira/browse/FINERACT-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952551#comment-16952551 ] Santosh Math commented on FINERACT-739: --- [~sg004], Did you work on this? > Loan (Installment in multiples of) Rounding not working > --- > > Key: FINERACT-739 > URL: https://issues.apache.org/jira/browse/FINERACT-739 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.3.0 >Reporter: Okeleke Mike >Priority: Major > Fix For: 1.5.0 > > Attachments: SS1.png, SS2.png, SS3.png > > > Loan repay schedule is not affected by *Installment in multiples of (IIM)* > setting in Loan Product screen > when you set the IIM to say: 1000, you are expected to have your total > repayments calculated to the nearest 1000 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-739) Loan (Installment in multiples of) Rounding not working
[ https://issues.apache.org/jira/browse/FINERACT-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-739: -- Affects Version/s: 1.3.0 > Loan (Installment in multiples of) Rounding not working > --- > > Key: FINERACT-739 > URL: https://issues.apache.org/jira/browse/FINERACT-739 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.3.0 >Reporter: Okeleke Mike >Priority: Major > Attachments: SS1.png, SS2.png, SS3.png > > > Loan repay schedule is not affected by *Installment in multiples of (IIM)* > setting in Loan Product screen > when you set the IIM to say: 1000, you are expected to have your total > repayments calculated to the nearest 1000 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-749) Client family member date of birth min value set to current year
[ https://issues.apache.org/jira/browse/FINERACT-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-749: -- Affects Version/s: 1.3.1 > Client family member date of birth min value set to current year > > > Key: FINERACT-749 > URL: https://issues.apache.org/jira/browse/FINERACT-749 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.3.1 >Reporter: Sidhant Gupta >Priority: Major > > The date of birth value for client family member cannot be set to less than > the first date of the current year. It can be fixed by modifying the input > tag's `min` attribute. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-749) Client family member date of birth min value set to current year
[ https://issues.apache.org/jira/browse/FINERACT-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-749: -- Fix Version/s: 1.5.0 > Client family member date of birth min value set to current year > > > Key: FINERACT-749 > URL: https://issues.apache.org/jira/browse/FINERACT-749 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.3.1 >Reporter: Sidhant Gupta >Priority: Major > Fix For: 1.5.0 > > > The date of birth value for client family member cannot be set to less than > the first date of the current year. It can be fixed by modifying the input > tag's `min` attribute. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-752) savings interest, posting wrong interest amount when savings-interest-posting-current-period-end is enable
[ https://issues.apache.org/jira/browse/FINERACT-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-752: -- Fix Version/s: 1.4.0 > savings interest, posting wrong interest amount when > savings-interest-posting-current-period-end is enable > > > Key: FINERACT-752 > URL: https://issues.apache.org/jira/browse/FINERACT-752 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.3.1 >Reporter: andrewDzakpasu >Priority: Critical > Fix For: 1.4.0 > > Attachments: fineract79.png, fineract80.png > > Time Spent: 40m > Remaining Estimate: 0h > > When savings-interest-posting-current-period-end is enable the amount of > interest posted is twice the amount when > savings-interest-posting-current-period-end is disabled. > > i was able to replicate this on these two accounts > 1.[https://staging.openmf.org/#/viewsavingaccount/79] when > savings-interest-posting-current-period-end is disable > 2.[https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]80 > savings-interest-posting-current-period-end is enable. > > > To replicate. > # create a savings account with voluntary product with withdrawal fee of 300 > # opening balance 20013 activation date 1-03-2019 > # approve and activate 1-03-2019 > # post interest on 25-03-2019 > # make a withdrawal of 19500 on 26-03-2019 > # you will notice the interest posting total amounts to 296 on > [https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]80 > which is wrong > # whilst on > [https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]79 > the amount is 187 which is correct . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-752) savings interest, posting wrong interest amount when savings-interest-posting-current-period-end is enable
[ https://issues.apache.org/jira/browse/FINERACT-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-752: -- Labels: p1 (was: ) > savings interest, posting wrong interest amount when > savings-interest-posting-current-period-end is enable > > > Key: FINERACT-752 > URL: https://issues.apache.org/jira/browse/FINERACT-752 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.3.1 >Reporter: andrewDzakpasu >Priority: Critical > Labels: p1 > Fix For: 1.4.0 > > Attachments: fineract79.png, fineract80.png > > Time Spent: 40m > Remaining Estimate: 0h > > When savings-interest-posting-current-period-end is enable the amount of > interest posted is twice the amount when > savings-interest-posting-current-period-end is disabled. > > i was able to replicate this on these two accounts > 1.[https://staging.openmf.org/#/viewsavingaccount/79] when > savings-interest-posting-current-period-end is disable > 2.[https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]80 > savings-interest-posting-current-period-end is enable. > > > To replicate. > # create a savings account with voluntary product with withdrawal fee of 300 > # opening balance 20013 activation date 1-03-2019 > # approve and activate 1-03-2019 > # post interest on 25-03-2019 > # make a withdrawal of 19500 on 26-03-2019 > # you will notice the interest posting total amounts to 296 on > [https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]80 > which is wrong > # whilst on > [https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]79 > the amount is 187 which is correct . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-752) savings interest, posting wrong interest amount when savings-interest-posting-current-period-end is enable
[ https://issues.apache.org/jira/browse/FINERACT-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-752: -- Component/s: Savings > savings interest, posting wrong interest amount when > savings-interest-posting-current-period-end is enable > > > Key: FINERACT-752 > URL: https://issues.apache.org/jira/browse/FINERACT-752 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.3.1 >Reporter: andrewDzakpasu >Priority: Critical > Fix For: 1.4.0 > > Attachments: fineract79.png, fineract80.png > > Time Spent: 40m > Remaining Estimate: 0h > > When savings-interest-posting-current-period-end is enable the amount of > interest posted is twice the amount when > savings-interest-posting-current-period-end is disabled. > > i was able to replicate this on these two accounts > 1.[https://staging.openmf.org/#/viewsavingaccount/79] when > savings-interest-posting-current-period-end is disable > 2.[https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]80 > savings-interest-posting-current-period-end is enable. > > > To replicate. > # create a savings account with voluntary product with withdrawal fee of 300 > # opening balance 20013 activation date 1-03-2019 > # approve and activate 1-03-2019 > # post interest on 25-03-2019 > # make a withdrawal of 19500 on 26-03-2019 > # you will notice the interest posting total amounts to 296 on > [https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]80 > which is wrong > # whilst on > [https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]79 > the amount is 187 which is correct . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-752) savings interest, posting wrong interest amount when savings-interest-posting-current-period-end is enable
[ https://issues.apache.org/jira/browse/FINERACT-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-752: -- Affects Version/s: (was: 1.4.0) 1.3.1 > savings interest, posting wrong interest amount when > savings-interest-posting-current-period-end is enable > > > Key: FINERACT-752 > URL: https://issues.apache.org/jira/browse/FINERACT-752 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.3.1 >Reporter: andrewDzakpasu >Priority: Critical > Attachments: fineract79.png, fineract80.png > > Time Spent: 40m > Remaining Estimate: 0h > > When savings-interest-posting-current-period-end is enable the amount of > interest posted is twice the amount when > savings-interest-posting-current-period-end is disabled. > > i was able to replicate this on these two accounts > 1.[https://staging.openmf.org/#/viewsavingaccount/79] when > savings-interest-posting-current-period-end is disable > 2.[https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]80 > savings-interest-posting-current-period-end is enable. > > > To replicate. > # create a savings account with voluntary product with withdrawal fee of 300 > # opening balance 20013 activation date 1-03-2019 > # approve and activate 1-03-2019 > # post interest on 25-03-2019 > # make a withdrawal of 19500 on 26-03-2019 > # you will notice the interest posting total amounts to 296 on > [https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]80 > which is wrong > # whilst on > [https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]79 > the amount is 187 which is correct . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-754) Linked between savings transfer transaction broken when account goes into overdraft
[
https://issues.apache.org/jira/browse/FINERACT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santosh Math updated FINERACT-754:
--
Component/s: Savings
> Linked between savings transfer transaction broken when account goes into
> overdraft
> ---
>
> Key: FINERACT-754
> URL: https://issues.apache.org/jira/browse/FINERACT-754
> Project: Apache Fineract
> Issue Type: Bug
> Components: Savings
>Affects Versions: 1.3.0
>Reporter: andrewDzakpasu
>Priority: Major
> Fix For: 1.4.0
>
>
> {code:java}
> // code code where bug is found
> else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse(); /// why reverse the transaction here if you could just
> update the details
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> }
> {code}
> I have replicated it on https://demo.openmf.org/#/viewsavingaccount/2589
> steps to replicate
> 1.create a savings account using the same product with opening balance as
> 45,754 , activation date 31-01-2019
> 2.manually posted interest on savings with transaction date as 31-01-2019
> 3. make an account transfer to another client with amount 45,854 transaction
> date 28-02-2019.
> 5. if you view the details you will see the transfer was made to another
> person will all details
> 6. now make a deposit of 5 on 27-02-2018
> 5. you will see the code above reverses the initial transfers and books it
> again (just a withdrawal )there by breaking the link of the transfer to
> another client.
> you can also view this from the journals
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FINERACT-754) Linked between savings transfer transaction broken when account goes into overdraft
[
https://issues.apache.org/jira/browse/FINERACT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santosh Math updated FINERACT-754:
--
Labels: p2 (was: )
> Linked between savings transfer transaction broken when account goes into
> overdraft
> ---
>
> Key: FINERACT-754
> URL: https://issues.apache.org/jira/browse/FINERACT-754
> Project: Apache Fineract
> Issue Type: Bug
> Components: Savings
>Affects Versions: 1.3.0
>Reporter: andrewDzakpasu
>Priority: Major
> Labels: p2
> Fix For: 1.4.0
>
>
> {code:java}
> // code code where bug is found
> else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse(); /// why reverse the transaction here if you could just
> update the details
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> }
> {code}
> I have replicated it on https://demo.openmf.org/#/viewsavingaccount/2589
> steps to replicate
> 1.create a savings account using the same product with opening balance as
> 45,754 , activation date 31-01-2019
> 2.manually posted interest on savings with transaction date as 31-01-2019
> 3. make an account transfer to another client with amount 45,854 transaction
> date 28-02-2019.
> 5. if you view the details you will see the transfer was made to another
> person will all details
> 6. now make a deposit of 5 on 27-02-2018
> 5. you will see the code above reverses the initial transfers and books it
> again (just a withdrawal )there by breaking the link of the transfer to
> another client.
> you can also view this from the journals
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FINERACT-753) incorrect savings account balance when charge transaction is reversed during an overdraft recalculate Daily Balances
[
https://issues.apache.org/jira/browse/FINERACT-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santosh Math updated FINERACT-753:
--
Component/s: Savings
> incorrect savings account balance when charge transaction is reversed during
> an overdraft recalculate Daily Balances
>
>
> Key: FINERACT-753
> URL: https://issues.apache.org/jira/browse/FINERACT-753
> Project: Apache Fineract
> Issue Type: Bug
> Components: Savings
>Affects Versions: 1.3.1
>Reporter: andrewDzakpasu
>Priority: Major
> Fix For: 1.4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This bug occurs in specific scenarios where there is an overdraft on account
> code section where the bug offers is below on
> protected void recalculateDailyBalances(final Money openingAccountBalance,
> final LocalDate interestPostingUpToDate)
> {code:java}
> runningBalance = runningBalance.plus(transactionAmount);
> transaction.updateRunningBalance(runningBalance);
> if (overdraftAmount.isZero() && runningBalance.isLessThanZero()) {
> overdraftAmount =
> overdraftAmount.plus(runningBalance.getAmount().negate());
> }
> if (transaction.getId() == null && overdraftAmount.isGreaterThanZero()) {
> transaction.updateOverdraftAmount(overdraftAmount.getAmount());
> } else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> }
> {code}
>
> steps to recreate .
> Set up a savings account with an overdraft say 500.
> # create saying account and add a charge fee of say 300 with opening balance
> of 500 approve and activate.
> # pay charge of 300 balance with now be 200 . charge is paid which creates
> an object in m_savings_account_charge_paid_by
> # now reverse the deposit of 500 .
> # system will recalculateDailyBalances and reverse the charge transaction on
> this section of the code
> {code:java}
> else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> {code}
> # now since the new charge created does not have the charged paid by object
> in the table " m_savings_account_charge_paid_by" recalculating the account
> balance becomes wrong
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FINERACT-753) incorrect savings account balance when charge transaction is reversed during an overdraft recalculate Daily Balances
[
https://issues.apache.org/jira/browse/FINERACT-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santosh Math updated FINERACT-753:
--
Labels: p1 (was: )
> incorrect savings account balance when charge transaction is reversed during
> an overdraft recalculate Daily Balances
>
>
> Key: FINERACT-753
> URL: https://issues.apache.org/jira/browse/FINERACT-753
> Project: Apache Fineract
> Issue Type: Bug
> Components: Savings
>Affects Versions: 1.3.1
>Reporter: andrewDzakpasu
>Priority: Major
> Labels: p1
> Fix For: 1.4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This bug occurs in specific scenarios where there is an overdraft on account
> code section where the bug offers is below on
> protected void recalculateDailyBalances(final Money openingAccountBalance,
> final LocalDate interestPostingUpToDate)
> {code:java}
> runningBalance = runningBalance.plus(transactionAmount);
> transaction.updateRunningBalance(runningBalance);
> if (overdraftAmount.isZero() && runningBalance.isLessThanZero()) {
> overdraftAmount =
> overdraftAmount.plus(runningBalance.getAmount().negate());
> }
> if (transaction.getId() == null && overdraftAmount.isGreaterThanZero()) {
> transaction.updateOverdraftAmount(overdraftAmount.getAmount());
> } else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> }
> {code}
>
> steps to recreate .
> Set up a savings account with an overdraft say 500.
> # create saying account and add a charge fee of say 300 with opening balance
> of 500 approve and activate.
> # pay charge of 300 balance with now be 200 . charge is paid which creates
> an object in m_savings_account_charge_paid_by
> # now reverse the deposit of 500 .
> # system will recalculateDailyBalances and reverse the charge transaction on
> this section of the code
> {code:java}
> else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> {code}
> # now since the new charge created does not have the charged paid by object
> in the table " m_savings_account_charge_paid_by" recalculating the account
> balance becomes wrong
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (FINERACT-795) Loan Account is not showing Interest value after cer
Santosh Math created FINERACT-795: - Summary: Loan Account is not showing Interest value after cer Key: FINERACT-795 URL: https://issues.apache.org/jira/browse/FINERACT-795 Project: Apache Fineract Issue Type: Bug Components: Loan Affects Versions: 1.3.1 Reporter: Santosh Math Fix For: 1.4.0 Create a loan account with following details: |Repayment Strategy|Penalties, Fees, Interest, Principal order| |Repayments|30 every 1 Days| |Amortization|Equal installments| |Equal Amortization|false| |Interest|240 per annum (20% Per month) - Flat| |Interest Calculation Period|Daily/Same As repayment| |Allow Partial Interest Calculation with same as repayment|false| |Interest Type|Flat| |Recalculate Interest|No| |Days in year|Actual| |Days in month|Actual| After 20th instalment, The interest is showing as zero. Please check here: https://staging.openmf.org/#/viewloanaccount/39 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-753) incorrect savings account balance when charge transaction is reversed during an overdraft recalculate Daily Balances
[
https://issues.apache.org/jira/browse/FINERACT-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santosh Math updated FINERACT-753:
--
Affects Version/s: (was: 1.4.0)
1.3.1
> incorrect savings account balance when charge transaction is reversed during
> an overdraft recalculate Daily Balances
>
>
> Key: FINERACT-753
> URL: https://issues.apache.org/jira/browse/FINERACT-753
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.3.1
>Reporter: andrewDzakpasu
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This bug occurs in specific scenarios where there is an overdraft on account
> code section where the bug offers is below on
> protected void recalculateDailyBalances(final Money openingAccountBalance,
> final LocalDate interestPostingUpToDate)
> {code:java}
> runningBalance = runningBalance.plus(transactionAmount);
> transaction.updateRunningBalance(runningBalance);
> if (overdraftAmount.isZero() && runningBalance.isLessThanZero()) {
> overdraftAmount =
> overdraftAmount.plus(runningBalance.getAmount().negate());
> }
> if (transaction.getId() == null && overdraftAmount.isGreaterThanZero()) {
> transaction.updateOverdraftAmount(overdraftAmount.getAmount());
> } else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> }
> {code}
>
> steps to recreate .
> Set up a savings account with an overdraft say 500.
> # create saying account and add a charge fee of say 300 with opening balance
> of 500 approve and activate.
> # pay charge of 300 balance with now be 200 . charge is paid which creates
> an object in m_savings_account_charge_paid_by
> # now reverse the deposit of 500 .
> # system will recalculateDailyBalances and reverse the charge transaction on
> this section of the code
> {code:java}
> else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse();
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> {code}
> # now since the new charge created does not have the charged paid by object
> in the table " m_savings_account_charge_paid_by" recalculating the account
> balance becomes wrong
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
