...
Passcode: 2@6T$8nn
Agenda
Jira Legacy server System Jira serverId 815f41e5-e5fb-3402-8587-82eccc3ffab0 key LF-3060 To complete a task while creating it:
Day: today or in the past;
Assignee: who is creating it or an user with an account
New tasks screen
Extract task sorting into a top level interaction (e.g. “Happening first”)
Happening first: today first, tomorrow, later in the week
What about late tasks? TBD Loic Sans
Pre-made date filters (e.g. “This week”)
Should they be dynamic and based on today + 6 or static and Su - M? Loic Sans : The tasks set to upcoming week, should list task for today + following 6 days.
Sorting needs some thought (esp around how to incorporate late tasks)
Time link should be combined with date
Repeating tasks (https://www.figma.com/file/eMffC0h3JPlWtzNttxJpil/Litefarm-Updated?type=design&node-id=9615-151666&mode=design&t=ynDtgPceIJT9KvS6-4)
Is “Repeat Settings” a good name to describe modifying the sequence?
Repetition option can also be selected when creating the task
What are occurences?
Additional instances of the same task on the same day at different times
Animal movements (see https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/edit-v2/1421312001 ) / https://www.figma.com/file/eMffC0h3JPlWtzNttxJpil/Litefarm-Updated?type=design&node-id=7841-58807&mode=design&t=ynDtgPceIJT9KvS6-4 )
Remove the restriction on moving from one location to the same one, perhaps just show some text if they set the same start and destination location, e.g. “Some or all of your animals are already at <location>. Do you want to proceed?”
Can we simplify the table to remove the checkboxes? Just show the animals and their locations
Do we need a checkbox to indicate an animal isn’t in the location LiteFarm thinks they are?
Feeding task (https://www.figma.com/file/eMffC0h3JPlWtzNttxJpil/Litefarm-Updated?type=design&node-id=9615-151666&mode=design&t=ynDtgPceIJT9KvS6-4)
Didn’t discuss!
Discussion points
Are completed / abandoned tasks impacted by changing a repetition?
If I create a repetition and modify the individual tasks in that repetition then modify the repetition, what happens to those customizations?
Loic Sans says we destroy tasks and then regenerate new tasks
Others not so sure of this…
Should occurences be aware of each other?
Should occurences show “Occurence 1 … n”
When repeating a task that has been assigned to someone, should those repetitions be assigned or unassigned?
Perhaps default to unassigned?
Maybe add this as a user prompt?
How to differentiate animal and crop (or both) tasks?
TO DO
Task | Owner | Due date | Notes |
---|---|---|---|
Could we do a technical implementation where the sequence is saved and displayed to the user but individual instances of the tasks are only created when modified? | This would support | ||
What is the relative level of effort for the “template” implementation vs. a “dumb” approach similar to copying crop plans | Should we do a SPIKE on this? Joyce Sato-Reinhold is interested | ||
What attributes overlap between a sequence and a concrete task?
| |||
What is a reasonable limit to the number of tasks you can create in a sequence? | |||
How do notifications happen when creating sequences? | |||
To decide whether on mobile view: Should we show how many animals match your current search, filter, and KPI selection criteria? | From S82 Grooming Joyce was in favour. | ||
To investigate how other apps support csv upload for animals - how user friendly / aligned with csvbox flow is it? | From S82 Grooming | ||
To create a refactor tickets to update search behaviour in other pages in the app
| From S82 Grooming |
...