Bug 371177

Summary: Request for additional date format - no year!
Product: [Applications] kmymoney Reporter: allan <agander93>
Component: importerAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: REPORTED ---    
Severity: wishlist    
Priority: NOR    
Version: 4.8.0   
Target Milestone: ---   
Platform: Mint (Ubuntu based)   
OS: Linux   
Latest Commit: Version Fixed In:

Description allan 2016-10-18 18:36:03 UTC 
My new format credit card statement causes further problems.
It produces a date with no year, like "15 Aug".

To avoid an on-going need to edit every entry, it would be good if the CSV importer could cope with this format, please.

Thanks

Allan

Reproducible: Always
Comment 1 Jack 2018-08-30 21:43:17 UTC 
Is this really something we want KMM to handle, or should this be handled by one of the KDE Frameworks we rely on, in which case this bug could be UPSTREAM?
Comment 2 Thomas Baumgart 2018-09-02 07:04:03 UTC 
AFAICT there is no KDE framework involved here. It is the CSV importer which provides a QDate object in the end and that *must* contain a year. So it is the task of the CSV importer to provide it.

In a similar scenario I used the following logic in case the year information was missing:
- Use currentYear as the value for statementDate
- If currentMonth < statementMonth decrement year

Anything else must be handled externally before the import.