Work in progress
Why is copying crop plans important?
...
TBD; not covered in this initial salvo.
When copying a crop plan that has been completed, should we use the due dates or the completed dates of the source tasks?
TBD; there are arguments for both directions.
You could argue that the original plan (the due dates) should be followed even if the completed dates don’t align because that was the plan and different completed dates could represent an uncharacteristic event that isn’t likely to be repeated and shouldn’t be propagated to repeated plans.
However, you could also argue that the plan (due dates) are forecasts and that the completed dates represent the truer version of events and the version of events that should be propagated.
Can I delete a copied plan?
...
When repeating a crop plan when is the first “new” copy?
It depends! Since we’ll always have an existing crop plan we’re repeating from, we need to be conscious of how we repeat it. I see two primary cases:
...
As designed on the source is never part of the repetition group. Repetitions generated at the same time are always grouped into repetition groups.
A better approach may be to remove the ambiguity from the process and allow the user to specifically define which plans are part of the group with a summary and confirmation screen (see
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
|
How should name copied crop plans?
...
Kevin’s gut: Yes, as long as it isn’t the planting task.
When copying a plan that has tasks that target many plans, how should that task be copied?
Kevin’s gut: Cloned tasks should only target the newly created crop plan, not historical plans or (attempt to find) newer versions of those previously targetted historical plans. This feels like more of a use case for a repeating task, rather than a repeating crop plan. For example, I might set up a monthly task to check the fences on all pastures on the farm. It’s harder (for me) to imagine a task that is part of a plan and references many other plans as well that should be repeated on a schedule.
Context:
...