action #117
closed
Reimbursement and ReimbursementExpense models
Added by ancorgs about 11 years ago.
Updated about 11 years ago.
Description
Implement the Reimbursement model with all needed fields and a nested model ReimbursementExpense with cocoon
- % Done changed from 0 to 100
Finally, a ReimbursementExpense model was not implemented. The original plan was open to the possibility of having different reimbursements for each request, but finally it was implemented as a singleton nested resource. Request and corresponding Reimbursement objects share now the same ExpenseRequest objects list. So implementation tooks longer than expected.
- Status changed from New to Closed
Forgot to close the issue on previous update
Also available in: Atom
PDF