Bug 361318

Summary:	Setting reconciliation status fails if multi-selection includes scheduled transactions
Product:	[Applications] kmymoney	Reporter:	Christian David <christian-david>
Component:	general	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED FIXED
Severity:	minor	CC:	k, ralf.habacker
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:	5.0.1
Sentry Crash Report:

Description Christian David 2016-04-02 13:15:33 UTC

A useless error message is shown if "Mark transaction as…" was used on a selection of multiple transactions in the ledger if the selection includes scheduled transactions which were not entered, yet (“the grey ones”).

Reproducible: Always

Steps to Reproduce:
1. Mark multiple transactions in ledger, including a scheduled transaction
2. Context menu -> Mark transaction as… -> Select something

Actual Results:  
Warning dialog with useless error message "Error" and empty details

Expected Results:  
Hard to say how KMyMoney should react in this case. Minimum resolution should be a better error message.

Using KMyMoney from branch frameworks 04/02/2016. I do not think we changed anything here, so the issue is probably the same in the 4.x branch.

Comment 1 Thomas Baumgart 2016-04-02 13:33:06 UTC

I was unable to select a regular transaction together with a scheduled transaction in the ledger view. This is on 4.x master branch. How did you manage to get there?

Comment 2 Christian David 2016-04-02 14:40:55 UTC

Maybe you have to be tricky: Create a normal transaction with a date which is after the one of the scheduled transaction. Select the normal transaction and click on an transaction which is above the scheduled one using a shift click.

Comment 3 Christian 2018-04-17 14:25:55 UTC

I installed KMyMoney version 5.0.1 amd tried to confirm. Here, I can select multiple transactions including some with future date, and then right-click and Mark as reconciled or mark as cleared, and everything works as expected. Cannot confirm bug. Maybe it's been fixed?

Comment 4 Ralf Habacker 2018-09-20 21:34:10 UTC

If the error persists, you are welcome to reopen this ticket with additional tracking information.