Open adam-jw-casey opened 11 months ago
There are two ways this could be implemented:
The UI for both of the options above would be approximately the same. The only difference might be that the existing optimistic/mid/high estimates would be displayed when clicking on the time estimate for an existing task.
But this would be much easier to implement with no interaction with the database, i.e. as a feature the user can (or must) use for time estimation, but that doesn't exist at rest.
Convert time needed to an enum, with a struct variant that takes an optimistic, mid, and pessimistic time estimate, and produces a best estimate using (O+4M+P)/6