...
Updated multi-select expense type view
Including ability to add / manage custom expense types
View custom expense types
(tile view)View custom expense type (individual view)
Read-only view
Add custom expense 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)
...
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
Customize an icon for a 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.
...
Discussion on -
For purposes of this discussion “Misc” and “Other” are equivalent. David feels strongly that “Miscellaneous” is better.
When a user clicks to add a “Misc” expense, we highlight
...
For retaining “Other” or “Misc”
...
For removing “Other” or “Misc”
...
Makes user experience for one-off expenses simpler
...
Makes data messy and difficult to categorize for the user
...
Feels right
...
Makes data messy and difficult to categorize for the researcher
...
Users may end up with a large list of one-off expense types that aren’t re-used
...
Will reduce usage and efficacy of configurable expense types
...
If there is a single “Misc” category for all users, this makes it easier for scientists to review
...
Users can create their own “Miscellaneous” if they wanted
...
For a future integration with Quickbook like tool, they will likely have a “Miscellaneous”
...
Against adding legacy “Other” entries to custom expense types
...
For adding legacy “Other” entries to custom expense types
...
Assumes the Note entered is a re-usable type (which is only partially supported in the data)
...
Introduces user to new feature automatically
...
M
V1.0 has an “Other” type that should be removed in favour of documenting custom expense types. Ideally, each of these would be migrated to be custom expense types for the farm where they are created.
| Code Block |
|---|
SELECT DISTINCT note FROM "farmExpense" WHERE expense_type_id = '7ce971b4-1590-11ea-9019-22000b628b95' |
...
Decision to retain “Miscellaneous” described here:Investigation into "Other" category of expense types
...
For retired expense types:
...