Bug 377869 - when adding a second entry w\o payer/receiver it substitute from previous entry
Summary: when adding a second entry w\o payer/receiver it substitute from previous entry
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.6.6
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-21 07:53 UTC by Octopuss
Modified: 2022-12-19 22:52 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 Octopuss 2017-03-21 07:53:31 UTC
hi,

when adding a second entity in ledger, after entity with payer/receiver, kMyMoney automatically fill payer/receiver field from previous entity.
More over, it is imposible to enter a second entity WITHOUT something in payer/receiver (after entering entity with payer/receiver).

How to reproduce:
1. open Ledger
2. enter trasaction to payer/receiver which is already in the program
3. enter next transaction without any payer/receiver
4. check that the last transaction also got a payer/receiver as in the first one

OS: Opensuse 13.2
source: opensuse-13.2-oss repo
version: 4.6.6-2.1.8-x86_64
Comment 1 Justin Zobel 2022-11-30 05:28:15 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-12-15 05:13:20 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
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!
Comment 3 Jack 2022-12-19 21:11:49 UTC
Given this does not occur with 5.x or current master, and was reported with 4.6, I'm closing at UNMAINTAINED.