Work in progress
For retired expense types:
...
Delete text should describe that expense categories will no longer be selectable once deleted but can be filtered for on reports and will show up in reports where that category has at least 1 expense within the filter criteria
...
As a farmer I want to be able to add, use, and remove types of expenses that are useful for my particular operations so that I can accurately mirror and understand my operations financially
Screens
https://www.figma.com/file/96NZ02oYe3jpet1roUp0s0/Mockups?type=design&node-id=1712-37203&mode=design (see Finances tab, Manage custom expense types section)
Requirements
Must have
Updated multi-select expense category type view
Including ability to add / manage custom expense categoriestypes
View custom expense types
(tile view)View custom expense categoriestype (individual view)
Read-only view
Add custom expense category (only name)
Retire custom expense category
...
type flow
Only user editable attribute is “Custom expense type name” and “Short description” (added )
Retire custom expense type (see https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/1341259816/Manage+custom+expense+types#Other-context)
Nice to have
Spotlight for managing expense types on updated multi-select expense type view
Search bar for expense types
Filter for default / custom expense types
Edit custom expense type flow
Customize an icon for an expense categorya custom expense type
Migration of all expense types of type “Other” to be custom expense types
Whomever takes this, if we get this far, please check with David Trapp before completing.
Shouldn’t have
Other context
Closely follows the pattern for custom task types - check that functionality out first!
...
We’ve eschewed the term “categories” in favour of “types” throughout finances. Any time you see “categories”, it’s out of date and should be replaced. Logic for this:
Types is shorter than categories in most of our supported languages
farmExpenseType table already exists - reducing tech debt
...
Changes to the model are hopefully minimal in this epic (though this isn’t the case for Manage custom revenue types - so take note of the structures for that upcoming epic). farmExpense and farmExpenseType tables already exist in the database.
For farmExpenseType, should use the existing convention around NULL or populated farm_id as to whether the type belongs to a specific farm or is universal
...
Discussion on -
Decision to retain “Miscellaneous” described here:Investigation into "Other" category of expense types
...
For retired expense types:
Retiring is a soft delete
Retired expense types must…
Not be selectable on the multi-select expense type view for new expenses created post-retirement
Still appear as a potential filter (with some sort of visual treatment, e.g. “Mechanical (retired)”) elsewhere in Finances V1.5
Continue to show up as a category in reports, lists, tables elsewhere in Finances V1.5
Previously created expenses of the retired type must…
Be visible in lists and tables elsewhere in Finances V1.5 (per filter criteria)
These treatments☝️ are not in scope for this epic, but are helpful in framing future work in the Finances V1.5 module.
...
When creating a new expense type, we should …
Check if the exact name and farm_id exist in the database and if so, don’t POST a new one but just set delete = FALSE
...
Should we have a separate section for retired expense types where they can be “un-retired”?
Not initially. We’ll do a check a few months after releasing this feature to see if that is a use case we need to support.