Update the “Add expense” screen to new design, which includes descriptions and checkboxes for expense types, handling the “Miscellaneous” option as a separate type visually and adding dates per expense.
Start working on the Finances dashboard with updated designs.
Continue work on the filtered transaction list export.
For this breakdown I’ve left out the “nice to haves” for now, as I think there’ll be enough work on the core goals for these features for us to work on during the sprint. We could tackle these nice to haves in an upcoming sprint if we have the time.
Add expense type descriptions to expense.json translation files, and make sure translations for expense type labels still work. Same for revenues (we think those have translations in the general translation file?).
My suggestion would be to reuse the existing translation keys and update them to be something like
Since we already have a tileType property, I'd suggest adding a new tileType for this new style and keeping the existing one as is in case we need it for future designs
4
Icons for default expense/revenue types have changed (designs for these are not yet final, will be updated during the course of the sprint)
“Miscellaneous” is now displayed visually as a separate option, and there are some styling changes to the “manage custom expenses” portion of the screen
Filter out “Miscellaneous” from default expense type list and update “Manage custom expenses” block
Should the entire expense type tile be clickable, or just the checkbox? Seems like entire tile from the prototype.
Answered : Entire tile. Loic Sans and I discussed this so I’m confident here.
Do we want to add the expense type description somewhere on add, edit, or read only views for expenses?
Answered - yes, the short description should be added to the read-only, create, and edit views for custom expense types.
Revenues don’t allow multi-select currently, should we not show the checkboxes for revenue?
Answered no change to revenue tiles for now - they remain single select (similar to tasks). We may update it to be a bulk documentation process in the future.
This component shouldn’t be specific to the Finances domain or to any of the contents we’ll be showing in the dashboard, so that we can reuse it in the future for other domains.
Since it seems we need to keep the contents of the card somewhat flexible, I’d suggest for this component to receive a spec of the cards, each card with a specified icon, background color and a child component for when the card is active. The component should take care of “switching” the cards when clicking on one of them, displaying the “hidden” card state with the icon and displaying the child component for the card that’s in the “active” state.
This component shouldn’t be specific to the Finances domain or any contents displayed in the transactions list, but something we can reuse in other portions of the app.
Contents will likely need to be flexible, so I’d suggest we maybe set it up so that it receives, for each item:
An icon
A flexible content component
A “expandable content” component
And it shows the chevron icon which on click should show/hide the expandable content.
Pull in transaction data from the new BE endpoint, and customize the component built above to display the list. The list should pull in paginated results and display a “Load more” button to get more results.
For this first iteration:
Don’t group by date or show dates (we’ll do this in a follow up ticket).
Don’t handle the “hidden” content for the transaction items (we’ll do this in a follow-up ticket – only show icon, label, description and amount).
6
6
Transactions with the same date should be displayed in a group
Other transactions also need to be able to be expanded and show a table with the details, although formatting and content will be different from Labour