[kmymoney] [Bug 473723] Allow to delete multiple Scheduled Transactions at once

[bugzilla_noreply--- via KMyMoney-devel]

https://bugs.kde.org/show_bug.cgi?id=473723

--- Comment #3 from schoenes-...@web.de ---
Jack:

I agree that implicitly the manual is correct in stating that an account can
only be deleted as long as no transactions are associated to it, but as I said
and you agreed - it may not be as obvious.  Having a popup stating the reasons
why account deletion cannot be performed is a good suggestion.

I did not find any special action to request a documentation change or addendum
- that's why I chose to enter it as a "bug".  Changing the ticket status to
WISHLIST is fine with me.  Thanks for picking up on the matter.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmymoney] [Bug 473723] Allow to delete multiple Scheduled Transactions at once

[Jack via KMyMoney-devel]

https://bugs.kde.org/show_bug.cgi?id=473723

Jack  changed:

   What|Removed |Added

Summary|Deleting an account is  |Allow to delete multiple
   |impossible while Scheduled  |Scheduled Transactions at
   |Transactions exist for the  |once
   |respective account  |
  Component|documentation   |general
   Severity|grave   |wishlist

--- Comment #2 from Jack  ---
First, the handbook for 5.1.3 is known to be out of date and incomplete in many
areas.  I am working on a complete review and update of the manual, but it will
not be released until 5.2, which is not yet scheduled.  A bug report is not
necessary for me to complete that work.  Also, there is an existing wishlist
for a popup showing exactly why an account cannot be deleted.
In terms of your report, a Scheduled Transaction can still be though of as a
transaction referring to the account, so the handbook is technically correct,
although I agree it does not provide sufficient detail.
What I propose is to change this report to a wishlist requesting the
possibility to delete multiple scheduled transactions at once.  Currently, any
action on a Scheduled transaction can only be done on one transaction at a
time, so I don't know how difficult this would be to implement.  Having the
wishlist at least ensures it won't be forgotten.

-- 
You are receiving this mail because:
You are the assignee for the bug.