Question

I am thinking the following would be a good feature.

Say I have 10 tasks assigned to me with so many hours estimated on each task. This means that there would be an 'implied' deadline of so many hours from today that things would get done.

The system would recognize this and if someone tried to assign me a case with a deadline of tomorrow it would not let them, it would tell them that the due date must be at least so far away considering the work load that is already there. This way people won't be able to assign you a ton of stuff overlapping already existing stuff and would have visibility over when you could possibly get to their task.

Beyond that the whole 'implied deadlines' could be an interesting feature of it's own. If I could view a calendar of generated 'implied deadlines' based on priority and estimate that would be pretty awesome.

Answer 1

The implied deadline you speak of is the developer completion date for the milestone in question (given to you by EBS). The actual deadline is the milestone completion date.

The EBS reports let you see in a flexible way whether your devs are going to hit their completion dates. Rejecting an assignment based on your current workload would probably create more headaches than it would solve.