A "Milestone" (hand off of document from copy to proof) is at 10 am on wednesday, then another "milestone" (handoff of the same document from proof to production) is at 2pm on wednesday; after review/edits.
Production's task cannot start until the two milestones are finished...roughly 2pm on wednesday...but they all happen on the same day.
It would be nice if the dependencies didn't push the production task to 2 days out to begin on Friday.
I agree... My votes were in this thread that I started:
...but I will move them to here as they are very VERY closely related.
Or in conjunction with percentages, offer assignments based on hours. 25% of an 8 hour day is 2 hours, but if it is a 6 hour work day or 10 hour work day the hours change. To be able to assign specific, set hour amounts would be helpful ( a "milestone" meeting for example that is part of the workflow for proofing... setting it as a 1.5 hour meeting located within an 8 hour day is eas1er to set up rather than "18.75%" of a work day. It seems more logical from a UI standpoint.)
22 votesChad shared this idea ·
ALSO ... To build on the color coding idea...functionally we should be able to color code any item entered: Groups, milestones, Tasks and projects. Often times I have sub-sub groups and milestones relevant to those that don't necessarily apply to the other sub-sub groups. And much like Brad stated... Colorizing the project views on the dashboard would be nice.