Feature area
Services/automations
Problem or use case
Some chores are only relevation during certain periods of the year such as mowing the lawn, which starts somewhere in spring and then ends in fall. During that time, it should be done once every week but outside of that timeframe, no mowing is required.
Proposed solution
I see two ways to solve this. Either during the creation of a chore, allow for the selection of an "active window". The chore will be active during that window and will be disabled/hidden/invisible outside of that window.
Option two would be the capability to disable and enable chores via a service call. Right now you's have to delete and create chores but that means you lose track of statistics.
Expected outcome
choreops.enable_chore / choreops.disable_chore that enables and disables a chore based on the chore ID. The chore is still there, can be editted, etc. but will otherwise not show on any chores, cannot be claimed, completed, approved, etc.
The option for an activity window for a chore would basically do the same thing as enable/disable but handled by the backend so it's less of a hassle for the end user.
Alternatives considered
Writing automations to create/delete a chore based on inputs from other integrations that indicate that a season has started or that temperatures are high enough that the lawn needs mowing (or the hedge needs trimming, or the car needs washing, etc.) This is possible and would achieve the desired result but feels like overkill.
Additional context
No response
Feature area
Services/automations
Problem or use case
Some chores are only relevation during certain periods of the year such as mowing the lawn, which starts somewhere in spring and then ends in fall. During that time, it should be done once every week but outside of that timeframe, no mowing is required.
Proposed solution
I see two ways to solve this. Either during the creation of a chore, allow for the selection of an "active window". The chore will be active during that window and will be disabled/hidden/invisible outside of that window.
Option two would be the capability to disable and enable chores via a service call. Right now you's have to delete and create chores but that means you lose track of statistics.
Expected outcome
choreops.enable_chore / choreops.disable_chore that enables and disables a chore based on the chore ID. The chore is still there, can be editted, etc. but will otherwise not show on any chores, cannot be claimed, completed, approved, etc.
The option for an activity window for a chore would basically do the same thing as enable/disable but handled by the backend so it's less of a hassle for the end user.
Alternatives considered
Writing automations to create/delete a chore based on inputs from other integrations that indicate that a season has started or that temperatures are high enough that the lawn needs mowing (or the hedge needs trimming, or the car needs washing, etc.) This is possible and would achieve the desired result but feels like overkill.
Additional context
No response