Hey Jernae, Do you go by whole days in your projects or does the timestamp matter? For me I go by whole day but we've run into this type of stuff as well. I think there's something in a project schedule that can be setup at the admin level where you can state which days are available for a project and the times that people work. I'm wondering also if at the resource level the team members have to state their work hours and then the system pulls from this against the timing of task? I'll put items due the following day when I have room to do so in the schedule to try to avoid these items. You could also set the project status to manual so that you can flip it from in trouble to on track instead of having the application do it, but I wouldn't recommend it. If it's late, it's late basically but looking at timestamps may assist with giving more breathing room there to show it correctly. In your scenario, if the item for me got done that day (for 9 times out of 10 depending on project constraints), I would flip it manually if it were truth that the item was completed on the estimated due date but went past the time on the task.
Does anyone know, can time be disabled on a project so that there is a focus only on the date? I haven't heard if there's a switch for that but maybe that's a path to take as well. Tim Greek IEHP
