Track All Expenses as Discrete Entries

[bradley-holt]

There has been feedback from multiple sources on several challenges to the new expense tracking feature (#31). The issues can be summarized as:

• It's difficult to work into my workflow, as I don't know my expenses for an event while I'm at the event.
• It's difficult to remember to go back and edit an event entry after the fact once I've completed an expense report.
• Even if I do remember, I will likely have multiple expense reports associated with an event. I need to remember to go back and edit the event multiple times, and there's no easy way to know which expenses I've added to the total and which I haven't added to the total yet.

I propose that we:

1. Remove the expense fields from events (negating #26).
2. Extend the new expenses collection (#27) to add the following:
   1. An optional dropdown to associate the expense with an event.
   2. An optional "Expense Report Reference #" field.
3. Optionally, we aggregate the above entries on an event page for reference purposes (i.e. a list of all expenses associated with the event and totals).

This will make it easier for team members to integrate expense reporting into their workflow. Team members can be trained to use /advocated immediately after they file an expense report and can simply enter the data from each individual expense report as a discrete entry in /advocated rather than needing to remember to update an event every time a new expense report is completed for that event.

[bradley-holt]

How to handle flight expenses where there is no event entry yet?