Hi,

I cannot reproduce this issue.
The case you describe seems not an issue if you have a meeting after last activity of the project (king of "project closure meeting").

1) did you recalculate planning ?
2) can you provide print screen ?

Hi,
Here are the screenshots ...

Hi,

This seems correct to me :
- you define a meeting, with some work (assigned and left)
- you define no other work for the project
- you calculate planning
=> the planning calcutation gives you start and end dates of project at the date of the meeting.

1) eitehr you define work for all tasks so that calculation gets correct
2) either you don't enter work for the meeting.

The thing that is really strange is that before I created this meeting, there was not end date of the project. But when I recorded the date of the meeting, I wanted to check if the meeting was clearly visible on the connection of the person responsible of the meeting.
It was then that I noticed that there was suddenly an end date of the project, which is exactly the date of the meeting!

I didn't not personally click on the calculation of planning :woohoo: !

It seems, in any case, that there is a "collateral" effect from the date of meeting that impact on the date of the project: it is as if it triggers "strangely" the calculation of the project planning :silly: .

I confirm that just creating a meeting updates the planned dates.
You don't have to run calculation.

Meeetings are some kind of "auto-planned" : a meeting is automatically planned at the date of the meeting.
So it updates the planned start and end dates of all upper planned elements (activity if any, sub-projets if any, up to top project).
It is pointed out in your case besause you have nothing "planned' in your items.

There is nothing strange : it is Project'Or RIA way of working - work driven planning.

At the beginning of the life cycle of a project or a sub-project, it is absolutely normal to plan a meeting without necessarily that the end date has been determined for this project.

For example, in fact, it makes sense to have a scoping meeting or brainstorming to determine the key dates and project milestones: number of delivery, documentation, installation, testing, end date, the duration of the observation of the stability, etc.

It is very odd that the management function of the date of a meeting "imposes" itself, the end date of the project !

This is , in my opinion , an exception to implement around this feature of management/planning of meetings.

As long as the end date of a project is not registered or approved by the Project Manager, a meeting must remain a " meeting."

A meeting should not be able to force the end date of the project without even display a warning popup to the project manager :sick: !!!

Because the risks and the consequences are simply very important.

The end date of a project is not a trivial event :ohmy: !

So this is extremely inconvenient for any Project Manager.

In summary, it would be useful , at least:
- To add a function that displays an alert pop-pup to the Project Manager or triggers a validation workflow before going further 🙂 .
- Allow to the user the choice to distinguish the meeting date and the end date of the project.

Sincerely,