Bug 504371 - Entering split scheduled
Summary: Entering split scheduled
Status: RESOLVED FIXED
Alias: None
Product: kmymoney
Classification: Applications
Component: file (other bugs)
Version First Reported In: 5.1.92
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-17 00:51 UTC by bnbunch
Modified: 2025-05-22 09:11 UTC (History)
0 users

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


Attachments
attachment-1767014-0.html (1.48 KB, text/html)
2025-05-21 04:34 UTC, bnbunch
Details
USD.png (42.73 KB, image/png)
2025-05-21 23:50 UTC, bnbunch
Details

Note You need to log in before you can comment on or make changes to this bug.
Description bnbunch 2025-05-17 00:51:00 UTC
When entering scheduled transaction from either scheduled transactions OR from ledger,changes made will not record in ledger, Have tried multiple times. Only way is to record scheduled transactions as is. Then go to ledger and make proper changes. Scheduled transactions seem to work as long as splits are not changed or contain no splits.
Comment 1 Thomas Baumgart 2025-05-20 07:45:45 UTC
I tried to duplicate this with  version 5.1.95-fbe0d43 on Linux and Windows but was not able to do so. It works for me just fine. Can you please update and see if the problem persists and if so, please explain exactly each step you do? Thank you in advance.
Comment 2 bnbunch 2025-05-21 04:34:07 UTC
Created attachment 181593 [details]
attachment-1767014-0.html

Yes, I will check.

On Tue, May 20, 2025, 2:45 AM Thomas Baumgart <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=504371
>
> Thomas Baumgart <tbaumgart@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |WAITINGFORINFO
>              Status|REPORTED                    |NEEDSINFO
>
> --- Comment #1 from Thomas Baumgart <tbaumgart@kde.org> ---
> I tried to duplicate this with  version 5.1.95-fbe0d43 on Linux and
> Windows but
> was not able to do so. It works for me just fine. Can you please update
> and see
> if the problem persists and if so, please explain exactly each step you do?
> Thank you in advance.
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 bnbunch 2025-05-21 23:50:11 UTC
Created attachment 181632 [details]
USD.png

That seemed to have worked for now. But all reports now show price column
all the way down with whole column of 1.0. If convert Values to currency is
checked then price is greyed out.
If Convert values is unchecked, you can uncheck price but amounts all show
(+-) USD in front of dollar amount.
The USD portion is out of aligned to left . I understand the amount itself
is right justified

Any way to remove USD and Price.

See attachment


On Tue, May 20, 2025 at 11:33 PM Brady Mattison <bnbunch@gmail.com> wrote:

> Yes, I will check.
>
> On Tue, May 20, 2025, 2:45 AM Thomas Baumgart <bugzilla_noreply@kde.org>
> wrote:
>
>> https://bugs.kde.org/show_bug.cgi?id=504371
>>
>> Thomas Baumgart <tbaumgart@kde.org> changed:
>>
>>            What    |Removed                     |Added
>>
>> ----------------------------------------------------------------------------
>>          Resolution|---                         |WAITINGFORINFO
>>              Status|REPORTED                    |NEEDSINFO
>>
>> --- Comment #1 from Thomas Baumgart <tbaumgart@kde.org> ---
>> I tried to duplicate this with  version 5.1.95-fbe0d43 on Linux and
>> Windows but
>> was not able to do so. It works for me just fine. Can you please update
>> and see
>> if the problem persists and if so, please explain exactly each step you
>> do?
>> Thank you in advance.
>>
>> --
>> You are receiving this mail because:
>> You reported the bug.
>
>
Comment 4 Thomas Baumgart 2025-05-22 09:11:54 UTC
The price column and currency display is a different topic and already mentioned in another ticket. Since you confirmed that the original problem entering split transactions in schedules is solved, I close this one as fixed.