Adding ability of requesting extension for each milestone

[RishiRajSahu]

We should allow each milestone to request for extension.

fyi @vikasrohit

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

[maxceem]

Do we need the ability to extend Delivery milestone?

[maxceem]

@vikasrohit Done for each milestone except Delivery one as we probably don't need it there. Please let me know if we also need an extension for the delivery milestone.

[vic-georgiev]

@acshields FYI

I think we do not need extension for delivery

[vikasrohit]

Agreed with both @maxceem and @vic-topcoder. However, the purpose of this ticket is to add that capability to every milestone component (or rather in the common Milestone component) so that we can enable disable that as per requirements.
@maxceem as we discussed that we are going to have metadata on milestoneTemplates which would give us the capability of adding more configuration options for milestones. We would use that to enable/disable the Request Extension feature to be generic.

[vikasrohit]

@maxceem I think we are okay for now, we would take care of moving it to a common place which is controllable via config, later after we are done with ability of metadata and started using it in at least one other use case.

[maxceem]

@vikasrohit so far all the logic for extension moved to one HOC, but we still has to insert variables in each milestone type into the places where we want to show extension requests dialog, extension confirmation dialog and a button to show extension request as places can be different depend on milestone type structure.

Also we have to control the blue line and dots which goes along these dialog for each milestone type individually. We can still try generalize this in the future if there is need.

We can for sure implement control the visibility of this feature by metadata as you mentioned above.

[vikasrohit]

Agreed on all points. 👍