Milestones on specific days

[PSW]

Hi folks

The problem.
Management meetings (where finance decisions are made outside of the
project) are only held on Mondays - so a milestone exists, with no resources,
on the first Monday after a given task, the next task cannot begin until the
day after that meeting.

I thought I could get around this by creating a meeting calendar with just
Mondays as working days and assigning it to the milestone.

However, a zero time milestone seems to ignore the calendar constraint
completely and if I make it a task of 1 minute duration (marked as a
milestone) it throws out the stage by adding .75 of a day to elapsed
time......?

What am I missing?

 

[PSW]

Hmmm

Not really, bear in mind that I have to set up dependencies for scheduling
and I don't know when a preceding given task in the future will actually
end.

A recurrent task will create a separate task for each meeting throughout the
project lifecycle, regardless of whether or not it is relevant to the project.

So imagine the scenario -

Task X will probably finish at some point next february (but it could be
march)- I can't predict a date yet. The deliverable from that task has to be
signed off at one of these meetings on the first Monday following that point.
The following task (Task Y) can't start until the day after the meeting. So
the meeting has a predecessor of Task X and Task Y has a predecessor of the
meeting.

The way I see it, I need to set the meeting as a milestone (after all,
that's what it is) constrained to a Monday only calendar.

 

[PSW]

And that's where I started....

Now here's a bizarre thing - after wasting hours today trying to get exactly
this to work (it's now evening and I'm at home), it works perfectly!

User error, well probably but I've just remoted to the office - created a
new project with exactly the same details and as soon as I make a monday only
calendar I start getting the .75 days thing appearing. Working times are
identical and, at this stage, no resources are allocated - so I haven't a
clue what the issue is.

But at least I have a workaround.

Thanks