Themes and priorities for this sprint: 

1. Complete animal removal flow LF-4116 - Getting issue details... STATUS LF-4117 - Getting issue details... STATUS

   1. Final integration work

   2. Addition of removal date field

2. Dashboard filters

   1. Implementation of new filters component LF-4100 - Getting issue details... STATUS

   2. Implementation of dashboard filters LF-4074 - Getting issue details... STATUS

3. Search LF-4073 - Getting issue details... STATUS

4. LF-3060 - Getting issue details... STATUS

5. LF-4149 - Getting issue details... STATUS

6. Animal creation flow (Lite Farm)

7. Tech debt tickets

   1. Final decision on LF-4022 - Getting issue details... STATUS

   2. LF-4021 - Getting issue details... STATUS

   3. Final decision on component library

Pre-reading for this sprint 

Intro reads:

• Getting started! [10 minutes]

• Tips and tricks [5 minutes]

• Intro to the LiteFarm app [20 minutes /w videos]

• A brief tour of the codebase and tech stack [5 minutes]

• Source control and the developer’s workflow [5 minutes]

Animals specific reads:

We should be wrapping up Detailed livestock records V1 and /wiki/spaces/LITEFARM/pages/1428750337, so those are a good place to start.

Other readings haven’t been significantly updated since S79. However, they’re listed below from most high level to most detailed:

• Livestock [10 minutes]

• /wiki/spaces/LITEFARM/pages/1368227863 [10 minutes]

• Detailed livestock records V1 [15 minutes]

• /wiki/spaces/LITEFARM/pages/1309999105 [10 minutes]

• /wiki/spaces/LITEFARM/pages/1404567587 [reference]

• /wiki/spaces/LITEFARM/pages/1394835499 [5 minutes, reference]

What’s the definition of done for a story? 

• Code

• Language tags - (run pnpm i18n script in /webapp )

  • If En copy changes on a ticket please set all the non-En tags to “MISSING”

  • Es version of the language tag as “MISSING”

  • Pt version of the language tag as “MISSING”

  • Fr version of the language tag as “MISSING”

• Unit testing

• Check in with Loic Sans if there’s a visual component to the story

• Open up a PR, and leave it unassigned. Two reviewers from the core team will be automatically added. Core team to incorporate feedback given during peer review. (Check if this is working well for PRs from forks from contributors).

• Passes peer review x 2

  • Anto will review all PRs

  • Second reviewer will be auto-added

• Merged

• Passes verification

• Passes validation

Team availability

S82 runs from … to …

Days in sprint: 9