scottohara / loot

An implementation of some of the core MS Money features in Ruby on Rails
MIT License
4 stars 3 forks source link

Further refine population of last transaction details #84

Open scottohara opened 9 years ago

scottohara commented 9 years ago

For a new transaction, on payee select we lookup the details of the previous transaction for that payee (in any account, for any category); and copy those details into the new transaction.

Should we repeat this as the transaction details are further refined?

For example, a payee that is commonly used for two different categories of transactions; eg. a transaction for "TPG" is typically either a "Telephone: Home" or "Work Expenses: Computer" category, depending on whether the transaction is for phone or ADSL.

Process could be something like this:

  1. "TPG" payee selected. Transaction details populated as: Amount = $59.99, Category = Work Expenses: Computer, Memo = ADSL Broadband
  2. Amount changed to $20
  3. Category changed to Telephone: Home. Memo changes to Home phone pre-payment

This implies that: getLastTransaction(payee) => populates amount, category & memo getLastTransaction(payee, category) => populates memo only

Do we also need to be smarter about the account context? For example, if we make payments to the same payee from different accounts, should the lookup be getLastTransaction(payee, account), and if no matches try getLastTransaction(payee)?

Do we need a better UI to allow the user to see recent transactions and pick one?