Should we hide the ability of setting delivered status for a phase which has timeline

[vikasrohit]

Once we have a phase controlled via milestones, should we allow user to mark the status of phase as delivered or should we let milestones control that? IMO, later is better option and we should disable the option in the status dropdown for phase.

fyi @rmjmccormick @acshields @RishiRajSahu

Aha! Link: https://topcoder.aha.io/features/TCCONNECT-293

[vic-georgiev]

The idea is to use the Timeline milestones flow to deliver/close the milestone. I'd prefer we do not allow switching the progress outside of the regular flow, this is confusing, as the goal is to use the milestones (progress and deliver).

The same logic applies for the phase "active" status - as soon as the first work milestone is switched as active, the phase should go into 'Active" status from 'Planned'.

Based on the milestone definition from Kyle, there is always the preparatory phase (where the copilot completes the work specification), so this one should still count for planning vs. work we're doing, but we have to confirm with Kyle (@acshields @rmjmccormick).

[rmjmccormick]

@vikasrohit @vic-topcoder Agree with both of you.

[vikasrohit]

Just fyi for

The same logic applies for the phase "active" status - as soon as the first work milestone is switched as active, the phase should go into 'Active" status from 'Planned'.

Right now there is no option to activate a milestone in our UI. So, rather, when phase is marked as active (in progress), we mark the first milestone active.

[vic-georgiev]

That is good. Our first milestone is always closing the work specification - this is the work preparatory state that Kyle calls "requirements gathering" and said it usually lasts ~2d. The preparatory milestone doesn't really affect the work execution so if it takes a long time for the customer to reply back we don't want to be counting days of delay as progress. That is the intended design to not calculate time until preparatory milestones are closed - urges the customer to do the job of closing the specification with the Copilot.

[vikasrohit]

Didn't quite get it. Our milestones starts as soon as phase is made active and it would start counting the milestones for the progress calculation.

Our first milestone is always closing the work specification

If this is added as milestone to the phase/product, it would be used for calculating the progress as soon as phase is made active. Any thing that is done before making the phase active, is not being counted for progress.

[maxceem]

Done.
For tests:
Example of a project with timelines http://local.topcoder-dev.com:3000/projects/6975/plan
Example of a project without timelines http://local.topcoder-dev.com:3000/projects/6375/plan