Why is copying crop plans important?
Creating a crop plan is a time investment. Each plan can take 1 - 2 minutes to complete if the user is familiar with the crop and much longer if they’re not. Asking the grower of a diversified farm to do this potentially dozens of times every growing cycle, or potentially multiple times each growing cycle for sequentially planted crops is a non-starter. Farmers need to be able to easily copy over what worked from previous seasons, and modify what didn’t.
Requirements
When copying crop plans the user should be able to…
… see the following:
Crop plan cards, including:
Plan name
Varietal
Current status
Date range
(Maybe?) # of pending tasks
(Nice to have) Card view and calendar view
… do the following:
Filter according to the following characteristics:
Date range
Statuses (multi-select)
Locations (multi-select)
Rating
Indicate that a plan should be copied or not
Set an offset or select a date for the crop plan to start
Modify the location for copied plan
(Nice to have) select multiple locations for the plan
(Nice to have) Expand the plan to view individual tasks that are part of the plan
(Nice to have) Select / unselect whether particular tasks should be included in copy
(Nice to have) Modify offset / dates for individual tasks
(Nice to have) copy the plan more than once
For example: copy this lettuce plan ever 15 days for 5 iterations
Open questions
Should we focus on a bulk copy instead (or in addition to) to allow the modification of many existing plans at once? For example, if there’s a last minute cold spell - all plans may be pushed back by a week.