WIP - work in progress
Table of Contents
⌙> Scope
...
manage custom revenue types - (nice) Also crop generated revenues
updated create expense flow (
select expense type(last sprint), updated expense form)updated create revenue flow (select revenue type, add custom revenue form )
(nice) Spotlight (do we need this?)
Strategy - edges inward
Deal with migrations and components first to clarify missing features.
...
Add container views last as the “middle” piece connecting frontend state to backend state.
Nices to haves - on the fly or last.
Tasks
Migrations
- making table revenue_type
- updating sale to add revenue_type_id, and total_value columns
- add role permissions for add/delete/get/edit:revenue_types, and their associated permissions
- (optional) update sale name to revenues and update references
- (nice) Spotlight
- (nice) crop generated revenues
...
- Update add expense form container
- Create add custom revenue form container
- (nice) crop generated revenues - Add custom revenue type radio
- Add Revenue Type Selection container and Route
- Add custom revenue type creation, edit, readonly
- Update Revenue Type selection to include custom revenue types and manage button
- (nice) crop generated revenues - Custom revenue form container and route
- (nice) Spotlight
# | Priority | M: must have N: nice to have | tasks | blockers | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0 | 0 | Previous Sprint | Reusable Components | |||||||||||||||||||||||||
1 | 1 | M: Update add revenue flow M: Manage custom revenue types Combined migrations for all sprint features. Update db schema to allow for revenue types |
| |||||||||||||||||||||||||
2 | 2 | M: Update add revenue flow Get revenue types endpoint |
| 1 | ||||||||||||||||||||||||
3 | 3 | M: Manage custom revenue types Custom Create APIs for custom revenue type endpoint Create APIs to get, create, edit, retire revenue type. |
| 2 | ||||||||||||||||||||||||
4 | 2 | M: Update add revenue flow State + sagas |
| |||||||||||||||||||||||||
5 | 4 | M: Update add expense flow Re-style add expense form |
| 0 | ||||||||||||||||||||||||
6 | 4 | M: Update add revenue flow Revenue type selection view (default) |
| 7 | 4 | M: Update add revenue flow |
| 8 | 0 | |||||||||||||||||||
7 | 5 | M: Manage custom revenue types Custom tile view (and adding to revenue type selection tiles and manage button?) |
| 3,4 | ||||||||||||||||||||||||
98 | 5 | M: Manage custom revenue typesAdd, edit, readonly, view And State + sagas required to implement Implement custom revenue types using reusable components (from custom expense) for Add, Read-only, Retire, Edit and Customisable Icon (And State + sagas required to implement?) |
| 3,4 | ||||||||||||||||||||||||
9 | 6 | NM: | N: Spotlight for manage custom revenue types. Is this needed? | Update add revenue flow Add custom revenue form |
| 7,8 | ||||||||||||||||||||||
10 | 7 | N: Spotlight for managing revenue types on updated multi-select expense type view |
...
. (Is this needed?) |
Visuals
*Note: these visuals are not kept up to date see resource links below for more up to date info.
...
Are there any placeholders for Readonly expense update, edit expense update, and dashboard update?
Unique challenges
adding value to “sale” table, and “notes” -
Jira Legacy server System JIRA serverId 815f41e5-e5fb-3402-8587-82eccc3ffab0 key LF-3581 reusing add expense form may not be practical
Is a spotlight need for both custom revenues types and custom expenses types?
For revenue types - duplicate old patterns or implement new pattern