...
This sprint will primarily be concerned with wrapping up custom revenue and custom expenses
Joyce Sato-Reinhold Expenses readonly / edit / delete & Sale API + saga update – DESIGNS EXIST
Revenue needs readonly / edit (non-crop type) / delete (= update to new modal) designs David Trapp – but we have a newly refactored edit view to work off of
We also want to prepare for these new requirements + user stories which remain in Finances 2.0 and will the the focus of our next sprint.
Generate income statement: “As a farmer I want to be able to generate an income statement so that I can understand if my farm has been profitable over a set timeframe”. Should include revenues, expenses, and gross profit (Priority: Highest)
Finances dashboard: “As a farmer I want to be able to understand my financial position at a glance when landing on the finances page so that I can quickly understand the financial footing of my operation” (Priority Medium)
...
| tasks | notes | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
1 | Preliminary Dashboard Task | Convert the following class-based components into functional components:
| |||||||||
2 | Create reusable summary tile component
| Low risk (consistent throughout design document) | |||||||||
3 | Create/update existing transactions list
| Slightly risk design might change, particularly the top and bottom table frame | |||||||||
4 | Create swipeable summary icon tiles component. Please use the existing icon tile component as your guide / base.
| Low Medium risk (– consistent throughout design document) BUT Duncan doesn’t like it and Loïc may not either | |||||||||
5 | Update | Blocked by 1 Requires at least one of 2, 3, or 4 - ticket owner should feel free to subtask and apply whichever component(s) are available | |||||||||
6 | Update | Blocked by 1 Requires at least one of 2, 3, or 4 - ticket owner should feel free to subtask and apply whichever component(s) are available Please do not implement “Last 30 days” filtering before checking in with product (it doesn’t appear on the homescreen tiles) | |||||||||
7 | Update | Requires at least one of 2, 3, or 4 - ticket owner should feel free to subtask and apply whichever component(s) are available Please do not implement “Last 30 days” filtering before checking in with product (it doesn’t appear on the homescreen tiles) | |||||||||
8 | Build container and component to filter export report data. Add three-dots menu to Finances homescreen to trigger export. | BLOCKED BY PRODUCT – Older design; I would prefer to get this confirmed before working. PDF export is not part of scope so that radio button should not exist | |||||||||
9 | Export structure / POC | Build saga, API route, controller, and utility function to generate and return an xlsx file | See technical notes above. Only send and write to file three values (revenue, expenses, balance) and trigger download automatically as in current uploaded document functionality. | ||||||||
| |||||||||||
| |||||||||||
| |||||||||||
|
|
...
What’s the relationship between the old Labour view and the new Labour expense tile? Is there a migration covering this? For now is the old Labour summary view removed?
Related comment:
Jira Legacy server System JIRA serverId 815f41e5-e5fb-3402-8587-82eccc3ffab0 key LF-3553
ticket to add type “Labour”:Jira Legacy server System JIRA serverId 815f41e5-e5fb-3402-8587-82eccc3ffab0 key LF-3564 Is estimated revenue removed? Where should it go now?? David Trapp
Does document export need to be recorded somewhere (e.g. in the database)?