Cache information needed for auto-fill and transfers between accounts

[mtotschnig]

Currently, the auto-fill feature and transfers between accounts retrieve information from past transactions. This information gets lost, if user deletes transactions (e.g. after export). We should make the information needed for these features persistent, so that they continue to work as expected even if transactions are deleted.

[Zykino]

I may add to a couple of points:

• Use the last transaction to auto-fill instead of the fist one
  • Sometimes my first buy is a "try" so it's not the money I'll spend the consecutive times
• Let the user manually manage this cached info? (bonus)
  • I'm buying at "My local store"
  • I defaulted the app to prefill $20
  • So now I just have to enter the cents

[mtotschnig]

Many thanks for your comments. I am not sure if I understand your points correctly, but I think what you describe is the current behavior of the app:

• The last transaction is used for auto-fill
• After auto-fill is done based on the payer, you can modify the transaction freely.

This ticket is not about auto-fill as such, which is already implemented, but describes the problem, that auto-fill only takes into account transactions that are still stored in the database, whereas it should work on the last information you entered, independent from it being deleted in the mean time.

[Zykino]

What I saw is that the autofill feature use the FIRST transaction of the tier instead of the last. (I never deleted any transaction)
What I wanted is to use the last transaction.

And maybe having an option to set the infos for a specific Tier.
For example in my public transport transaction I want to have a Comment "Subscription {Month}". I don't ask you to replace {Month} but I'd rather have already written "Subscription" so I write the month (and I don't have to first delete the last one)

[mtotschnig]

This is very surprising that you see the first transaction instead of the last, since it is designed to use the last, and I cannot reproduce this buggy behavior. Could you maybe send me more details of the device where you observe this to support@myexpenses.mobi?

[mtotschnig]

As for your second paragraph, wouldn't the existing template functionality allow you to achieve this as efficiently?

[Zykino]

It was on a OnePlus 2 (Oxygen OS 2.1.X == Android 5 AND CyanogenMod 13 == Android 6)
Now I don't have this phone anymore so I'll tell you what I see on the next one :)

Yes I think the templates are enough for this :)