Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

WIP - work in progress

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 - (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.

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.

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

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

State Management

  • 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

Components

Containers/Frontend Routes

  • 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


LF-3581 - Getting issue details... STATUS

2

2

M: Update add revenue flow

Get revenue types endpoint

LF-3591 - Getting issue details... STATUS

1

3

3

M: Manage custom revenue types

Create APIs for custom revenue type endpoint to get, create, edit, retire revenue type.

LF-3584 - Getting issue details... STATUS

2

4

2

M: Update add revenue flow

State + sagas

LF-3586 - Getting issue details... STATUS

5

4

M: Update add expense flow

Re-style add expense form

LF-3582 - Getting issue details... STATUS

0

6

4

M: Update add revenue flow

Revenue type selection view (default)

LF-3583 - Getting issue details... STATUS

0

7

5

M: Manage custom revenue types

Custom tile view

(and adding to revenue type selection tiles and manage button?)

LF-3585 - Getting issue details... STATUS

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?)

LF-3588 - Getting issue details... STATUS
LF-3589 - Getting issue details... STATUS (read-only + retire)
LF-3590 - Getting issue details... STATUS

3,4

9

6

M: Update add revenue flow

Add custom revenue form

LF-3592 - Getting issue details... STATUS

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.

Finances 2.0 UX: LUX-82 - Getting issue details... STATUS

Figma (Finances Sketch): https://www.figma.com/file/96NZ02oYe3jpet1roUp0s0/Mockups?type=design&node-id=1712-37203&mode=design

Custom revenue type

Current - None (new feature)
Updated: LUX-77 - Getting issue details... STATUS

Add expense flow

Current:

Updated: LUX-74 - Getting issue details... STATUS

Add revenue flow

Current:

Updated: LUX-75 - Getting issue details... STATUS (Screen 1 existing, screen 2 new, screen 3 nice to have)

Questions & Answers

  1. Are there any placeholders for Readonly expense update, edit expense update, and dashboard update?

  2. Unique challenges

    1. adding value to “sale” table, and “notes” - LF-3581 - Getting issue details... STATUS

    2. reusing add expense form may not be practical

  3. Is a spotlight need for both custom revenues types and custom expenses types?

  4. For revenue types - duplicate old patterns or implement new pattern

  • No labels