Recurring transactions

Registered by Michael Rooney on 2008-10-06

Have a way to configure recurring transactions.

Features of a recurring transactions:
- account
- isTransfer
 - sourceAccount
- description
- amount
- start date
- end date (optional)
- frequency (inspired by GCal, as flexible)
- action [automatic, ask first] (inspired by http://www.turtlesoft.com/Goldenseal-Software-Reference/recurring.htm)

Issues:
Since wxBanker isn't necessarily going to be running constantly, when run, it needs to look at its list of recurring transactions and figure out which transactions to make. What is the best way to remember this state? Checking for all transactions which "should" exist won't work since it should be possible to remove or edit recurred transactions, and we don't want wxBanker to re-enter these.

Something like GCals editing would be optimal where, when editing or removing one transaction, you can choose to apply it to just this instance, all future, or all past and future. In order to do this, transaction metadata linking to the recurring transaction would be necessary.

However a still decent option would be to record with each recurring transaction setting, the last time the transaction was entered. Then when wxBanker is run, it can look at the last date the recurring transaction was made, and make all appropriate ones from then to the present.

Blueprint information

Status:
Complete
Approver:
Michael Rooney
Priority:
High
Drafter:
None
Direction:
Needs approval
Assignee:
Michael Rooney
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
milestone icon 0.6
Started by
Michael Rooney on 2009-06-17
Completed by
Michael Rooney on 2009-12-05

Related branches

Sprints

Whiteboard

2008.11.20 mrooney: Targeting this for wxBanker 0.5.
2009.03.23 mrooney: re-targetting to 0.6, I need to get 0.5 out!
2009.06.17 mrooney: I think I have the basic UI in place for creating them, so now I need to make it do something. For editing, I imagine a special right click action for recurring transactions which pops down a panel from the top using the same panels (but not instances) as the new one, but with a save and cancel button.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.