You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tasks have a forecast date, we want milestones to also have a forecast date which is (in groovy pseudo code) milestone.tasks*.end_date.last(). Although this is denormalising the db, it might be useful to store. We could go slightly further and add the time estimate to the task_start date, extrapolated over the scheduled work hours for the assigned user.
We need to display this date in the UI in both the milestone list view and in the task edit view (next to the milestone dropdown).
The text was updated successfully, but these errors were encountered:
Tasks have a forecast date, we want milestones to also have a forecast date which is (in groovy pseudo code) milestone.tasks*.end_date.last(). Although this is denormalising the db, it might be useful to store. We could go slightly further and add the time estimate to the task_start date, extrapolated over the scheduled work hours for the assigned user.
We need to display this date in the UI in both the milestone list view and in the task edit view (next to the milestone dropdown).
The text was updated successfully, but these errors were encountered: