Bug 368106

Summary:	can not enter $0 in future scheduled payments. It requires a value other then 0
Product:	[Applications] kmymoney	Reporter:	Chuck <m116chucklesf>
Component:	general	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED FIXED
Severity:	normal	CC:	jakykong
Priority:	NOR
Version:	4.8.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Chuck 2016-09-01 14:02:48 UTC

After I enter a  recurring scheduled transaction as paid I change the value to 0 until I get the next bill. I was able to do that on version 4.6.8. Version 4.8 requires me to put in an amount other then 0 before it will accept the amount.

Reproducible: Always

Steps to Reproduce:
1.enter a scheduled transaction.
2.Modify the amount for the next months scheduled transaction
3.

Actual Results:  
If I put in o for the amount, it will not let me accept that amount. I have to put in any valu above 0 for the program to accept the change

Expected Results:  
It should have accepted 0 for a value

Comment 1 Thomas Baumgart 2016-09-01 16:13:09 UTC

Bug 311481 is the reason for that. The last commit in comment 15 causes this behavior. This was changed more than 3 years ago.

Comment 2 Jack Mudge 2017-05-07 16:47:37 UTC

Before opening a bug, I searched and found this one. I wanted to add a comment here in the hope that it brings some attention to this issue.

I use $0 scheduled transactions to track due dates on credit cards with respect to projected balances on the ledger. It's one of the (if not the) single most useful feature that sets kMyMoney apart from other options I've tried. Sadly, I cannot enter that now, and have resorted to using $0.01 transactions instead, which doesn't stand out visually as well as the $0 ones did, since those ended up in the payments column. 

I sincerely hope this issue can be resolved. Thank you for all of your hard work!

Comment 3 Justin Zobel 2022-11-06 09:24:46 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 4 Chuck 2022-11-06 14:55:02 UTC

Status = solved