Link transfers for more useful editing
Currently when a transaction is made, it is done by making two transactions, one in the destination for $x and one in the source for $-x. They are not linked together in any way however. Editing the amount, date, or description of one does not affect the other. Sometimes this is the desired behavior, but sometimes it is not.
It would be optimal, however, if when editing a transaction which was a transfer, wxBanker asked if you wanted to apply the changes to the sister transaction as well.
This could be done edit-time by detecting if a transaction is a transfer from the description, and possibly amount.
Another, perhaps better solution would be to actually link transfers, by adding a field to each transaction which contains an optional transaction ID, which corresponds to a linked transaction. This way we know for sure, and don't have to do any searching on each edit.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Low
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Michael Rooney
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
-
0.7
- Started by
- Michael Rooney
- Completed by
- Michael Rooney
Related branches
Sprints
Whiteboard
2010.01.09 mrooney: the link was implemented as part of 0.6, via Transaction.
2008.10.12 michael: perhaps another solution is to just implement transaction metadata, so we can have tags like "link-213" signifying this is linked to transaction 213. This can also be used to link recurring transactions to their recurrance object.
