Bug 277041 - "Pay to" text box unexpectedly changes when changing field from OFX import
Summary: "Pay to" text box unexpectedly changes when changing field from OFX import
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: SVN
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2011-07-04 02:35 UTC by Mike Wolfe
Modified: 2018-10-27 02:22 UTC (History)
1 user (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 Wolfe 2011-07-04 02:35:34 UTC
Version:           SVN trunk (using KDE 4.4.5) 
OS:                Linux

When I update my accounts with OFX Direct Connect, transactions are imported with yellow highlighting, often with names that are taken from OFX fields.  When I try to change the "Pay to" field then move to another field, the changes are reverted to the original (imported from OFX) payee names.

Note: This behavior has been around for at least the past year or two, I'm only reporting it now because I have the time and motivation :).  This bug does NOT happen when selecting new fields with a mouse, only with the keyboard.

Reproducible: Always

Steps to Reproduce:
1) Perform an OFX direct connect download with unmatched transactions.
2) Edit an unmatched transaction and select the "pay to" field
3) Type the name you wish to change to in the "pay to" field, hit enter to select it from the list.
4) Press the TAB key to move to the next field

Actual Results:  
The cursor moves to the next field, but the "Pay to" field has the original, uncorrected name.

Expected Results:  
The corrected name stays in the field, and the Category is autofilled based on the most frequent transaction for that payee.

I would be happy to answer any questions in emails to wolfemi1 at gmail.
Comment 1 Cristian Oneț 2014-07-28 14:30:23 UTC
Could you try is this still happens with the latest stable version? If you can compile from sources testing git master would be even greater.
Comment 2 Jack 2016-09-27 17:11:29 UTC
With no feedback or evidence it still happens, should this be closed?
Comment 3 Thomas Baumgart 2016-09-27 18:42:27 UTC
Maybe Mike (the OP) can drop a note about the current state.
Comment 4 Andrew Crouthamel 2018-09-26 22:14:52 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 set the bug status 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 5 Andrew Crouthamel 2018-10-27 02:22:22 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!