/
S110 Grooming!

S110 Grooming!

Recording link: https://ubc.zoom.us/rec/share/Uk0-9xipqdMnyU8BUr5qbWFjexbJDaMD6mu2LkjhlCZT67ga1eJq_-a6drh5w6jP.5OOF_DMxJ71GtMpm

Passcode: Qm7@9P5=

 

Agenda

  • Reviewing designs for re-completing Completed tasks https://lite-farm.atlassian.net/browse/LF-4737

    • Will users be able to re-trigger the completion flow an indefinite amount of times?

  • Requirements for Calendar view for tasks (@Loic Sans can you add the Jira ticket link here if you create one?)

    • Which details from tasks do users need to see in the calendar view?

    • Reviewing what users have been saying about this feature request in Support messages

    • Is this a presentational only change? (no changes needed to the backend)

    • The final user flow will be conditioned by which UI library we pick to implement this

      • Strongest candidate is https://fullcalendar.io

        • Pros

          • Open source

          • Supports localization

          • Supports custom styling

          • Multiple types of calendar views supported

          • Extensive documentation and examples

        • Con:

          • Timeline view is a premium (paid) feature, so probably not a feasible option if that’s something we need

      • Alternative inspired by FullCalendar https://github.com/jquense/react-big-calendar?tab=readme-ov-file

        • Pros:

          • Also open source

          • Also supports localization

          • Also supports custom styling

          • Also multiple calendar views supported

          • Apparently supports timeline view without paying

        • Cons

          • Seems to have less options for calendar view types

          • Documentation is scarcer than FullCalendar’s

Discussion points

  • Re-opening of completed tasks

    • Looking at screens:

      • “Fix it now” call to action → re-triggers flow from the very first screen of complete flow

      • Financial implications to editing the task duration – how to address/mitigate this?

      • Should store a status “revised” and the revision date should be visible on the task list

    • Editing task duration & assignee

      • Divya: we are not the main financial

      • Loïc: LiteFarm is used to keep track of verbal agreements about wage etc.

      • Denis: Has received communications from users interested in tracking all finances in LiteFarm and using the salary features

      • Looked at the assignee + wage selection modal and where it occurs in the flow

        • It is not part of completion, but part of creation / when viewing a task before it has been completed

        • Loïc may look into re-triggering this or forcing review of this during completion

          • This was discarded later in discussion

    • Is editing a completed task in this way really less work than deleting it and creating a new one?

      • For a lot of our tasks there is a lot of data to input

    • Keeping a record of the revision

      • Can we record the date and initiator of revision (technically)? – Yes

      • Can we revise a revised task? – Yes; would allow to correct some of the wage-related issues that are introduced in revision

        • What about the 24 hours limit? Is it a moving target?

        • We are going towards no limitation

    • Open questions

      • Should we allow editing the assignee? → we have gone with not allowing this at all

      • wage_at_moment – this is already a bit of a sketchy calculation, we can leave it as is

        • we will continue using the same logic for override, OR for wage_at_moment (the active user wage when the complete flow is submitted – the recorded date of completion has no bearing on this)

      • Finances value will re-calculate after revision; we are okay with this

    • Movement task?

      • The working logic to make sure that animals aren’t moved based on a completed task if a newer task has already been completed should be fine

  • Calendar view

    • See mockups here: https://www.figma.com/board/Ns6ZDQQSF085eXVJAUHdMO/Crop-Management-assessment?node-id=0-1&p=f&t=LPUH9ak0uRGkjbPD-0

    • As a starting point we are considering the weekly view to begin as this is most useful for planning your workday / workweek (as a worker)

    • Not entirely sure in which contexts calendar view has been requested

      • Duncan: it really seems the crop overview gantt chart is the most value-add to farmers

      • Team looked at Heirloom Gantt Chart and admired it

      • This view would go in crops, not in tasks

      • Loïc to design a view like this so we could evaluate; it would go in crops

    • Going forward, designs for two things that Loïc, Divya, and Anto will look at in their next group meeting

      • Calendar view (weekly view)

      • The crops annual view gantt chart

 

TO DO

Task

Owner

Due date

Notes

Task

Owner

Due date

Notes

 

 

 

 

 

 

 

 

 

 

 

 

 

Related content