Bug 386168 - scheduled transactions greyed out in ledger
Summary: scheduled transactions greyed out in ledger
Status: RESOLVED NOT A BUG
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mint (Ubuntu based) Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-25 06:52 UTC by Mike
Modified: 2018-09-21 17:34 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike 2017-10-25 06:52:28 UTC
On occasion, scheduled transactions appear in the ledger greyed out and the only way to edit amounts is to change the base scheduled transaction. This does not happen to all transactions but it does seem to be consistent. For example I create a weekly shopping schedule. I set it to be a variable amount, set the next date and base amount.When it appears in the ledger, I cannot edit the amount or reconcile without opening the scheduled transaction and modify that.  If I then delete and re-create the scheduled transaction, the same thing happens but If I create a schedule for a different payment it will work as expected?

Not sure if this is a bug of some sort or a misunderstanding on my part as to how it should work?

Regards
Mike
Comment 1 Jack 2017-10-25 16:16:46 UTC
I would guess that it is greyed out in the register before the transaction is actually entered.  As you discovered, before you actually enter a transaction it only really exists in the schedule, so that is the only place to edit it.  Once you enter it, it is a real transaction, and you should be able to edit it in the ledger as you wish.  Also, you can edit the details as part of entering the transaction, so you do not need to edit the base schedule.  When you do make a change as part of entering the transaction, it should offer a pop-up asking if you want to make those changes to all future scheduled transactions, or only the one time.
Comment 2 Mike 2017-10-25 17:49:49 UTC
Hi Jerry


Thanks for the prompt reply, I definitely must be doing something wrong 
as the scheduled transaction entry does not look greyed out but is when 
it gets posted in the ledger.

It doesn't happen to every record set up in Schedule Transactions, just 
certain ones. Does it depend on what payment method you choose for each 
transaction?


Mike


On 25/10/17 17:16, Jack wrote:
> https://bugs.kde.org/show_bug.cgi?id=386168
>
> Jack <ostroffjh@users.sourceforge.net> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |ostroffjh@users.sourceforge
>                     |                            |.net
>
> --- Comment #1 from Jack <ostroffjh@users.sourceforge.net> ---
> I would guess that it is greyed out in the register before the transaction is
> actually entered.  As you discovered, before you actually enter a transaction
> it only really exists in the schedule, so that is the only place to edit it.
> Once you enter it, it is a real transaction, and you should be able to edit it
> in the ledger as you wish.  Also, you can edit the details as part of entering
> the transaction, so you do not need to edit the base schedule.  When you do
> make a change as part of entering the transaction, it should offer a pop-up
> asking if you want to make those changes to all future scheduled transactions,
> or only the one time.
>
Comment 3 Thomas Baumgart 2017-10-25 18:44:52 UTC
Which version of KMyMoney are you using? This is indeed a very strange behavior. What happens, if you right click on such a transaction? In case a context menu appears (which is the intended behavior) I am interested in the title line of that context menu.
Comment 4 Jack 2017-10-25 22:52:02 UTC
Also, you haven't clearly specified whether the problem transactions in the ledger are before or after that transaction has actually been entered.  To clarify, when you create a schedule, the next one or two upcoming instances of that schedule are shown in the register, but only as a sort of place-holder.  Since they are only scheduled, you can't do anything to them in the register.  Only when it is "entered" does it become a real transaction you can manipulate.  

Have you read the Chapter 10 in the handbook on this topic?  https://docs.kde.org/stable4/en/extragear-office/kmymoney/details.schedules.html
Comment 5 Mike 2017-10-26 06:26:11 UTC
Jack, Thomas


The problem is resolved, thank you. As I suspected, the error was mine. 
Your instructions have shown me the correct way to deal with the errant 
scheduled transactions, by using the right context menu which, to answer 
Thomas's question is titled Scheduled Transaction Options.

 From there I selected the enter next transaction option as suggested by 
Jack and this then gave me the ability to adjust the fields to reflect 
any changes to the base amount or date, and then to reconcile the record.

Oh,  and I have now read the manual (I have slapped my wrist and stood 
on the naughty step? That's the trouble with being old, you think you 
know everything !!)


Many Thanks again for your prompt and succinct replies


Regards

Mike


On 25/10/17 23:52, Jack wrote:
> https://bugs.kde.org/show_bug.cgi?id=386168
>
> --- Comment #4 from Jack <ostroffjh@users.sourceforge.net> ---
> Also, you haven't clearly specified whether the problem transactions in the
> ledger are before or after that transaction has actually been entered.  To
> clarify, when you create a schedule, the next one or two upcoming instances of
> that schedule are shown in the register, but only as a sort of place-holder.
> Since they are only scheduled, you can't do anything to them in the register.
> Only when it is "entered" does it become a real transaction you can manipulate.
>
> Have you read the Chapter 10 in the handbook on this topic?
> https://docs.kde.org/stable4/en/extragear-office/kmymoney/details.schedules.html
>