[kmymoney] [Bug 351535] Lost payee information when matched

2023-09-17 Thread Antoine T
https://bugs.kde.org/show_bug.cgi?id=351535

--- Comment #16 from Antoine T  ---
(In reply to Jack from comment #15)
> I'm sorry if it wasn't clear enough, but this patch is not yet available in
> the 5.1 branch, so you will continue to see the problem in 5.1.3 and even
> the nightly build from the 5.1 branch.  It is only available in master
> branch, which will eventually be released as 5.2, but there is not yet a
> specific timeline for this.

Hmm if I am looking at the build related to my test:
https://binary-factory.kde.org/view/AppImage/job/KMyMoney_Release_appimage-centos7/607/
, it looks to me like the build is done against master branch, not 5.1 branch.
The version showed in KMyMoney help might not be updated to reflect the master
branch (it should have been 5.2-SNAPSHOT or something similar).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 351535] Lost payee information when matched

2023-09-17 Thread Antoine T
https://bugs.kde.org/show_bug.cgi?id=351535

--- Comment #14 from Antoine T  ---
Ok, I tested with
https://binary-factory.kde.org/view/AppImage/job/KMyMoney_Release_appimage-centos7/lastSuccessfulBuild/artifact/kmymoney-5.1-607-linux-gcc-x86_64.AppImage
. Version info shows: 5.1.3-2fecc3fb5

The issue is reproducible. Test scenario:
1. create a new account file
2. create a QIF file
D12/12/2022
T-12.10
PCARTE 09/12/22 AGRCSTCB*4563
^
3. import the qif file

As a result, the payee is unchanged and the memo field is empty.
Another test: if I add a Payee that matches the pattern (here AGRCST), and
delete and reimport it, then the Payee is recognized but the MEMO field is
still empty.
So the KMyMoney 5.1.3 give the same symptoms as 5.1.2.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 351535] Lost payee information when matched

2023-09-10 Thread Antoine T
https://bugs.kde.org/show_bug.cgi?id=351535

--- Comment #12 from Antoine T  ---
(In reply to Jack from comment #10)
> Antoine, I'm a bit confused.  Is the bug currently that when doing a QIF
> import with 5.1.2, if the Payee is changed based on matching rules, you lose
> the information in the original field? 

Hi, yes indeed.

I know for sure this was fixed in
> master branch (which now shows the "Original payee" in the memo.  I'll have
> to check whether that fix was backported to 5.1.3, so if you can test that
> version, it would help.  Also, as far as I know, the changes should apply
> equally to QIF and OFX, so it's important to know exactly what results you
> get now.  I have not actually tested any qif import in a long time, so I'll
> have to see if I have any sample data to use.

Currently, I am using Ubuntu latest LTS (so 22.04 jammy), which officially
released kmymoney 5.1.2 (https://launchpad.net/ubuntu/+source/kmymoney) for
this distribution version. I could try 5.1.3 but that would require me to test
in another VM with Ubuntu 23.10 to setup. Let me a few days for that, when I
have freetime :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 463854] When transaction is imported and match a configured Payee, the date info from Payee is lost

2023-09-07 Thread Antoine T
https://bugs.kde.org/show_bug.cgi?id=463854

--- Comment #5 from Antoine T  ---
Please note that there is an error in the test scenario I have written in
description. I said it is an OFX file while describing a QIF file. The test
scenario of the issue is actually with a QIF file, because there is no issue
with an OFX file.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 463854] When transaction is imported and match a configured Payee, the date info from Payee is lost

2023-09-07 Thread Antoine T
https://bugs.kde.org/show_bug.cgi?id=463854

Antoine T  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #4 from Antoine T  ---


*** This bug has been marked as a duplicate of bug 351535 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 351535] Lost payee information when matched

2023-09-07 Thread Antoine T
https://bugs.kde.org/show_bug.cgi?id=351535

--- Comment #9 from Antoine T  ---
*** Bug 463854 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 463854] When transaction is imported and match a configured Payee, the date info from Payee is lost

2023-09-07 Thread Antoine T
https://bugs.kde.org/show_bug.cgi?id=463854

--- Comment #3 from Antoine T  ---
I am closing this ticket as I didn't see I have opened a duplicate ticket
#351535 in 2015 (!).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 351535] Lost payee information when matched

2023-09-07 Thread Antoine T
https://bugs.kde.org/show_bug.cgi?id=351535

Antoine T  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---
 Ever confirmed|0   |1

--- Comment #8 from Antoine T  ---
Hi @Jack,

I am sorry to have to reopen this ticket. When I tested to reproduce this bug,
I tested on OFX import and yes, from a long time ago, the import of OFX file
does a copy of Payee field to MEMO field, even if the MEMO tag is not set in
OFX file.

However this is not the case for QIF import, which is the original test
scenario in description. The QIF import in KMyMoney 5.1.2 does not copy Payee
to MEMO field.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 351535] Lost payee information when matched

2023-08-09 Thread Antoine T
https://bugs.kde.org/show_bug.cgi?id=351535

--- Comment #6 from Antoine T  ---
Oups cannot set the status as FIXED. I closed it anyway.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 351535] Lost payee information when matched

2023-08-09 Thread Antoine T
https://bugs.kde.org/show_bug.cgi?id=351535

Antoine T  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

--- Comment #5 from Antoine T  ---
Hi, sorry for the delay.

I can confirm the issue is fixed. Tested in KMyMoney 5.1.2. Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 463854] When transaction is imported and match a configured Payee, the date info from Payee is lost

2023-01-04 Thread Antoine T
https://bugs.kde.org/show_bug.cgi?id=463854

--- Comment #2 from Antoine T  ---
(In reply to Jack from comment #1)
> I believe in master branch, the original field from which Payee was detected
> is included in it's entirety in the memo.  I don't know if there is any
> chance that this will be back-ported to 5.1 or not.  What date does the
> transaction end up having?  Also - saying the date is lost implies that
> there is a date field in the import which is lost.  What is actually lost is
> the full original content of the Payee field,  Have I understood correctly?

Exactly, the date lost is not the transaction date field, but the time of
operation date, that is in the content of Payee field. You understood
correctly.
Also, the mechanism should be an option in case there is already information in
MEMO field provided by the bank.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 463854] New: When transaction is imported and match a configured Payee, the date info from Payee is lost

2023-01-04 Thread Antoine T
https://bugs.kde.org/show_bug.cgi?id=463854

Bug ID: 463854
   Summary: When transaction is imported and match a configured
Payee, the date info from Payee is lost
Classification: Applications
   Product: kmymoney
   Version: 5.1.2
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: importer
  Assignee: kmymoney-de...@kde.org
  Reporter: antoine.tran.31+...@gmail.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
The Pay to field contains data info and when importing the OFX file, the Payee
is replaced by the configured Payee, then the date info is lost.

STEPS TO REPRODUCE
1. Creates a OFX file containing
---
D12/12/2022
T-12.10
PCARTE 09/12/22 AGRCSTCB*4563
---
2. Creates a Payee that matches partially on "AGRCST".
3. Import the transaction


OBSERVED RESULT

Then the import of such event will create a transaction with "Pay to" field of
"AGRCST". The date info "09/12/22" is then lost! Which is a critical info. MEMO
field provided by bank is empty so it does not contain the date info too.

EXPECTED RESULT

An option when importing OFX to copy "Pay to" field to MEMO.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 349938] hang freeze during QIF import

2016-12-10 Thread Antoine T
https://bugs.kde.org/show_bug.cgi?id=349938

--- Comment #23 from Antoine T <antoine.tran.31+...@gmail.com> ---
I am quite confident because:
* it has always worked since month except this month
* the only noticeable changement is that I have put the QIF in one level down
with a "," inside, instead of parent
* I tried multiple times with and without ",", with small and long filename,
and this is the conclusion.
* the issue is very reproductible, but with 2 kind of symptoms. In my usual
(3year-old) account file, it either freezes or shows a window to choose which
date format I want to use (although it already is set in QIF profile). For the
latter, the app shows that it has imported successfully no element. As if it
can see nothing inside the file. I have tried today to create a new account,
and it never freezes, but always ask me the date format, and import nothing.
When removing the ",", it works.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 349938] hang freeze during QIF import

2016-12-10 Thread Antoine T
https://bugs.kde.org/show_bug.cgi?id=349938

--- Comment #21 from Antoine T <antoine.tran.31+...@gmail.com> ---
(In reply to allan from comment #20)
> Just saw your commment about the ',', and I have tried that, both in a file
> name and in a directory, again without problem, I'm afraid.
> 
> Allan

Have you tried in Windows or Linux?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 349938] hang freeze during QIF import

2016-12-08 Thread Antoine T
https://bugs.kde.org/show_bug.cgi?id=349938

Antoine T <antoine.tran.31+...@gmail.com> changed:

   What|Removed |Added

Version|4.7.2   |4.8.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 349938] hang freeze during QIF import

2016-12-08 Thread Antoine T
https://bugs.kde.org/show_bug.cgi?id=349938

--- Comment #16 from Antoine T <antoine.tran.31+...@gmail.com> ---
Hi, any news on this? I can confirm this bug is still here in a completely
fresh install Windows 10 and fresh Kmymoney 4.8.0. This bug is random, sometime
I can have a windows asking me the date format, sometime it freezes, sometime
it works. I use this app each month, and this month particularly, it never
works, strange...

-- 
You are receiving this mail because:
You are watching all bug changes.