Table of Contents
⌙> 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) Custom revenue spotlight
...
- Update add expense form container
- Create add custom revenue form container
- 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
- Crop generated revenues - Custom 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 |
| |||||||||||||||||||||||||
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) |
| 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 |
| 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 | - | N: Update table names Moving to concept of revenues vs sales |
|
...
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 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?