...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Table of Contents
⌙> Scope
⌙> Tasks
⌙> Visuals
⌙> Q&A
Scope
Previous related sprint technical document - Manage custom expense types tasks
Parent Product Scope: Finances V2.0
manage custom revenue types - 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
...
Custom revenue spotlight
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.
Nice-to-haves - on the fly if easy 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
- (optionalnice) update sale name to revenues and update references
- (nice) Add Spotlight booleans
- (nice) crop Crop generated revenues boolean to revenue type
Endpoints/controllers
- 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 containers(nice) crop form container
- Crop generated revenues - Add custom revenue type radio
- Add Revenue Type Selection container and Route
- Custom expense form container and route
- nice) crop Add custom revenue type creation, edit, readonly
- Update Revenue Type selection to include custom revenue types and manage button
- Crop generated revenues - Custom expense revenue form container and route
- (nice) Spotlight
...
- for custom revenue types
# | 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 Create APIs for custom revenue type endpoint to get, create, edit, retire revenue type. |
| 2 | ||||||||||||||||||||||||
4 | 2 | M: Update add revenue flow State + sagas | LF-3581 | M: View custom revenue types
| ||||||||||||||||||||||||
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) |
LF-3586 M:
| 0 | ||||||||||||||||||||||||
7 | 5 | M: Manage custom revenue types Custom tile view (and adding to revenue type selection tiles and manage button?) |
| 3,4 | ||||||||||||||||||||||||
8 | 5 | M: Manage custom revenue types 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 | M: Update add revenue flow Add custom revenue form |
| N: Is this needed also? | Spotlight for managing revenue types on updated multi-select expense type view | Add Expense Flow
| 7,8 | |||||||||||||||||||||
10 | 6 | M: Add option on create custom revenues to select if it is a crop generated revenue |
| 8 | ||||||||||||||||||||||||
11 | 6 | M: Dashboard implications for new types |
| |||||||||||||||||||||||||
12 | 7 | N: Spotlight for managing revenue types on updated multi-select expense type view. (Is this needed?) |
| 9 | ||||||||||||||||||||||||
13 | LF-3586 | Add Revenue Flow- | N: Update table names Moving to concept of revenues vs sales |
| Add Revenue Flow |
Visuals
*Note: these visuals are not kept up to date see resource links below for more up to date info.
...
Updated:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
...
Spotlight custom revenues: MISSING see expense for inspiration
...
Questions & Answers
Are there any placeholders tickets for Readonly expense detail view(from dashboard) update, edit expense update, and dashboard update?
Unique challenges
adding value to “sale” table
Jira Legacy server System JIRA serverId 815f41e5-e5fb-3402-8587-82eccc3ffab0 key LF-3581 , and “notes”? -
Jira Legacy server System JIRA serverId 815f41e5-e5fb-3402-8587-82eccc3ffab0 key LF-3581 Reusing add expense form may not be practical because of customer name
Is a spotlight need for both custom revenues types and custom expenses types?
Yes, as per David - the more spotlights the better. It was proposed to end both revenues and expenses spotlight if either was “seen” but the decision is to have many spotlights.
For revenue types specifically - duplicate old patterns or implement new pattern?
try new pattern first?