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?)
Tasks
...
Strategy - edges inward
Deal with migrations and components first to clarify missing features.
Write state editors for frontend backend as soon as possible (ASAP).
Add container views last as the “middle” piece connecting frontend state to backend state.
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
...
- endpoints and controllers to retire or add custom revenue types
- endpoints and controllers to get custom revenue types
Sagas
- sagas to retire, add, edit custom revenue types
- editing existing sagas to accommodate task types
...
- new slice for revenue_type table
- selectors for default revenue types, custom revenue types, retired custom revenue types
- reducers to handle retiring and addition of custom revenue type state change
- updates to existing sale state to handle new columns for existing sale table
...
Containers/Frontend Routes
- Update add expense form container
- Add Create add custom revenue type containersform container
- (nice) crop generated revenues - Add custom revenue type radio
- Add Revenue Type Selection container and Route
- Custom expense form container and routeAdd custom revenue type creation, edit, readonly
- Update Revenue Type selection to include custom revenue types and manage button
- (nice) crop generated revenues - Custom expense revenue form container and route
- (nice) Spotlight
Priority # | Priority | M: must have N: nice to have | tasks | blockers | |||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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: Create APIs to get, create, edit, retire revenue typeUpdate add revenue flow Get revenue types endpoint |
| 1 | |||||||||||||||||||||||||||||||
3 | 3 | M: View Manage custom revenue types 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: Implement custom revenue types using reusable components (from custom expense) for Add, Read-only, Retire, Edit and Customisable IconUpdate add expense flow Re-style add expense form |
| ||||||||||||||||||||||||||||||||
6 | 4 | M: Update add revenue flow Revenue type selection view (default) |
| ||||||||||||||||||||||||||||||||
7 | 4 | M: Update add revenue flow |
| LF-3584 | N: Is this needed also? | Spotlight for managing revenue types on updated multi-select expense type view | Add Expense Flow
| ||||||||||||||||||||||||||||
8 | 5 | M: Manage custom revenue types Custom tile view |
| 3,4 | |||||||||||||||||||||||||||||||
9 | 5 | M: Manage custom revenue types Add, 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
| LF-3586 | Add Revenue Flow | (read-only + retire)
| 3,4 | ||||||||||||||||||||||||||||
N: | |||||||||||||||||||||||||||||||||||
N: Spotlight for manage custom revenue types. Is this needed? | Spotlight for managing revenue types on updated multi-select expense type view |
5
Visuals
*Note: these visuals are not kept up to date see resource links below for more up to date info.
...
Updated:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Questions & Answers
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