If you were performing an action on the app from the webadmin or the CLI (install, update, backup, restore, change_url...), you are on the right place!
Otherwise, the issue may be due to Firefly III itself. Refer to its documentation or repository for help.
If you have a doubt, post here, we will figure it out together.
Delete the italic comments as you write over them below, and remove this guide.
Describe the bug
I used the public CSV importer to import expenses. Everything worked but the mapping. I never tried mapping before, so I can't tell what could resulted the bug. The only error the importer gave me was for one line which can not be a problem for that - I guess: Error(s)
Line #32: transactions.0.amount: transactions.0.amount muss größer als 0 sein. (original value: "0")
=must be larger than 0.
Versions
Hardware: Old laptop or computer
YunoHost 4.0.8.3 (stable).
I have access to my server: Through everything
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ?: no
If yes, please explain:
Using, or trying to install package version/branch: master
To ReproduceSteps to reproduce the behavior.
Install Firefly III current version on current Yunohost
Setup Firefly (accounts, budgets, categories, rules) (No rule changes the account of an expense)
Create OAuth2 access for the public importer
Import expense data in the CSV importer
Let the opposing account data be mapped with a click on the checkbox
In the next screen map accordingly
Start import
Everything should look just fine in the importer
Check Firefly III accounts
Find a lot of wrong entries due to ignored mapping
Expected behavior
only 3 extra accounts should be created by the importer because I forgot 3 accounts while I was creating the expense accounts and the transactions should be mapped to the existing ones + those 3.
How to post a meaningful bug report
Describe the bug I used the public CSV importer to import expenses. Everything worked but the mapping. I never tried mapping before, so I can't tell what could resulted the bug. The only error the importer gave me was for one line which can not be a problem for that - I guess: Error(s)
Versions
To Reproduce Steps to reproduce the behavior.
Expected behavior
Logs no logs