...
Initiated by … | From a … | Who should be notified? | Use case | Title | Body | Link to … | Notes | Release | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record edited | Task | Individual | A task has been assigned to me | “Task assigned” | “A <task_type> task has been assigned to you by <assigner>.” | the assigned task | May 2022
| |||||||||
Record edited | Task | Individual | A task that had been assigned to me has been reassigned to someone else | “Task re-assigned” | “A <task_type> task previously assigned to you has been assigned to someone else by <assigner>.” | the re-assigned task | Depending on the users role and their ability to see the re-assigned task, this may or may not have a “Take me there” button. | May 2022
| ||||||||
Record edited | Task | Individual | A task that is assigned to me has been edited | “Task changed” | “A <task_type> task assigned to you has been updated by <assigner>.” | the assigned task | May 2022 * May want to support granular history in the future, e.g. “Due date changed from May 2 to May 9”. | |||||||||
Record edited | Task | Individual | A task that is assigned to me has been abandoned | “Task abandoned” | “A <task_type> task assigned to you has been abandoned by <assigner>.” | the assigned task | May 2022 | |||||||||
Record edited | Task | Individual | A task that is assigned to me has been marked completed | “Task completed” | “A <task_type> task assigned to you has been marked completed by <assigner>.” | the assigned task | May 2022 | |||||||||
Record edited | Task | Individual | A task that I created has been marked “Ready for review” | |||||||||||||
Record edited | Task | Management | A task has been edited to be unassigned. | “Unassigned task” | “<Editor> has marked a task as unassigned.” | The unassigned task | May 2022 | |||||||||
Record created | Task | Management | A task has been created and left unassigned. | “Unassigned task” | “<Creator> has created a task and left it unassigned.” | The unassigned task | May 2022 | |||||||||
Record created | Weather event | Farm | A weather event that will impact the farm | |||||||||||||
Daemon / time based | Task | Management | A task due in X days has not yet been assigned | “Unassigned tasks” | “You have unassigned tasks due this week.” | Task homepage, with “unassigned tasks” and filtered for due date falling in this week. | Should fire Monday morning at 6AM (localized time) for all tasks due that week. | May 2022 | ||||||||
Daemon / time based If > 0 tasks due within next 24 hours | Task | Individual | A task due today has not yet been completed | “Tasks due today” | “You have tasks due today.” | Task homepage, with “my tasks” and filtered for due date = today. | Should fire at 6AM (localized time) the morning the task is due. | May 2022 | ||||||||
Daemon / time based | Task | Individual | A task due yesterday has not yet been completed | “Tasks overdue” | “You have tasks due today.” | Task homepage, with “my tasks” and filtered for due date = yesterday and earlier. | Should fire when the task transitions from planned to late. | May 2022 | ||||||||
Daemon / time based | Location | Management? | Location X has transitioned to Organic status | |||||||||||||
Record edited | Location | Farm | User A has retired Location X | “Farm location retired” | “<location_name> has been retired by <retirer> and will no longer be visible on the farm map.” | None | V2 | |||||||||
Record created | Location | Farm | User A has created Location X | “Farm location created” | “<location_name> has been created by <creator> and will now be visible on the farm map.” | Location detail page | V2 | |||||||||
Dev team | N/A | All users | Link to release notes for all users. | Input as a param | Input as a param | Input as a param | The link to for this use case is very likely a release notes page on the litefarm website. | May 2022 | ||||||||
Record created | Irrigation prescription | Management? | Your irrigation prescription is ready to be reviewed | V2 | ||||||||||||
Record created | Sensor reading | Management? | V2 | |||||||||||||
Daemon / time based | Document | Management? | A document has expired | |||||||||||||
Insights | Not exactly sure how this should go, but significant changes to Insights should spawn a notification. Ideally could set break-points on Insights as well. | |||||||||||||||
Record edited | User | Individual (invitor) Management? | User_A has accepted your invitation to join LiteFarm! | |||||||||||||
Record edited | User | Individual | Your wage has been changed to X | |||||||||||||
Record edited | User | Individual | Your email address has been changed to X. | This updated notification would apply to the user, not the user-Farm so may be a unique use case. | ||||||||||||
Record edited | Task | Individual / Management? | The last task on your crop plan has been completed. Would you like to mark that plan completed? | Individual would be the original creator of the crop plan. | ||||||||||||
Record created | Observation | Farm | Observation has been made | New observation | “<User> has made a new <observation_type> observation.” | Observation | ||||||||||
Record created? | Export | Individual | A certification export has successfully been completed | |||||||||||||
Record edited | Farm | Farm |
...