Created attachment 132040 [details] Test kmymoney file showing the issue SUMMARY When trying to cancelled a repeating scheduled entry, clicking on the second or third item in the schedule, results of the first time being reported as the object to be cancelled. STEPS TO REPRODUCE 1. Create a test kmymoney file 2. Set up a repeating payment schedule for every two weeks 3. Click on the second or third entry and kmymoney will prompt to cancel the first OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
The design of KMyMoney at this point is to always operate on the next occurrence of a schedule. In some instances, the preview shows more than one occurrence of a schedule and I agree, that it is confusing that trying to skip the third occurrence suddenly skips the first. On the other hand, what you try to achieve is more of an exception to a schedule but the current implementation does not support exceptions to schedules. Technically, KMyMoney keeps the date of the next transaction and the recurring period. So the second and further occurrences do not exist on file but are generated for display purposes only. So skipping an occurrence simply forwards the date of the next transaction to the one following. What we could do is to make sure that we always present 'Operation on *next* occurrence of schedule' in the tooltips and descriptions. This seems to be a more or less easy task. The second best would be to disable the operations on any but the next occurrence of a schedule, which is more of a larger change. Any other ideas?
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 mark the bug 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!
Changing into a wish list item as proposed by original poster and changing state to reported.