The main information is contained in following question:http://fogbugz.stackexchange.com/questions/1199/does-project-milestones-report-take-into-account-other-projects-work/1249#1249
Note: Global milestones are not used or discussed there, because it's still uncertain to me what is this and how this really works.
We have a developer team with multiple unconnected projects. The project milestones are also unconnected with each other (except, maybe, milestones in same project with hard dependencies).
What we want is a way to tell EBS to use global priorities for work ordering instead of milestones.
So this would look like this:
Each person should do all of their cases in order of priority (with hard milestone dependencies satisfied) and putting a single low-priority case into an early milestone will make it finish at some time far in the future.
On the contrary, putting a single high priority case in late milestone (but with no unsatisfied dependencies) should make this task delay other ones, even in the earliest milestones.
The work management will be done with active priority rearangement (perhaps, with a case context menu :) ). That way a team can effectivly manage multiple projects simultaneously and at any given moment have a good calendar date predictions for each of per project milestones (and not just burn down as today).
So i can adjust some priorities in global case list and immideately check how this changes ship dates in different projects, and then adjust it again and again, cutting / delaying the features to finally satisfy all of the ship dates.
The hard per project time protection should not be used in this case. Means user must complete all his 1st priority tasks before moving to priority 2 tasks regardless of project or milestone of this tasks (except, again, hard stated milestone dependencies)
