Bug 323146

Summary:	Schedule erroneously listed as finished
Product:	[Applications] kmymoney	Reporter:	Marko Käning <mk-lists>
Component:	general	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	onet.cristian
Priority:	NOR	Keywords:	triaged
Version:	git (master)
Target Milestone:	---
Platform:	MacPorts
OS:	macOS
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Marko Käning 2013-08-03 17:26:20 UTC

I have a schedule which is set to frequency "once" and has to be executed in the future.

Although all is seemingly okay the "Scheduled transactions" view lists it as "Finished".

Reproducible: Always

Steps to Reproduce:
1. "Go to Scheduled transactions" view
2. Look at "Next Due Date" column
Actual Results:  
Observe in "Next Due Date" column the state "Finished"

Expected Results:  
"Next Due Date" column should contain the next and ONLY execution date

I think this is due to the fact that I originally copied this schedule from an existing one which had a monthly frequency. Then I only changed the copy's frequency and suddenly the problems appeared.

SOME SPECULATION:
I believe that for some reason this schedule uses the "Date of final transaction" which is by default the current day, although it shouldn't do so, since "This schedule will end at some time" is not selected (it is even not selectable due to the fact that this schedule is executed only ONCE).

Comment 1 Cristian Oneț 2014-07-31 08:24:46 UTC

I can't reproduce this, are you sure you haven't already entered the transaction? I that case it will, correctly, be displayed as finished.

Comment 2 Andrew Crouthamel 2018-09-25 03:50:19 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Andrew Crouthamel 2018-10-27 02:43:46 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!