How to get the planned end date not to change with time sheet entries, when activity is not a status done. Or actual time entered is less than assigned.

Just avoid replaning (do not execute planning calculation).

We are having a problem with planning changing when we do not wish them too.

We NEVER wish to.
But if you recalculate, ProjeQtOr will show you the reallity, not what you wish.

In this case it was planned to start on the 3rd June and first actual time recorded was 19th August and planned and real start time updated to 19th August. Which is fine. However the last recorded time was 22nd August and there is still work to be done on the activity. The user did not change the status of activity to done or closed. However the planned end date has been change from 30th August to 22nd August?

There is no left work, the real end date is set to last input date.
If task is not finished, user should add some left work.

Thanks for your response. However I am now trying to monitor this, as we are having difficulties with time sheets.

In the example I understood re-planning had not been run. However I have tested again as there are times when we do have to run re-planning as new activites are added to the plan during projects and we do not want planned dates for other activities to change in appropriate ways.

I have added a document with screen shots of the issue I just had.

The activity had a planned start of 19th Aug and end 23rd Aug. We recorded some time not all the time required for activity on 20th Aug. It updated the planned dates to 20th Aug start and 23rd Aug end. Which is ok. This activity has no dependencies.

I then added a new activity. Then re-ran planning with start date 9th January 2019 of the project as I did not want to change the planned dates for other activities, just create some for new activity. However the first activity changed and the from a planned start date 20th aug (when first timesheet record was) to 31st January 2019!!? No idea where this date comes from. Plus a planned end date of 26th August., which might come from 5 day duration from 20th August?

The auto planning flag is not set for this project and was not set through out all this testing.

How is this supposed to work. Users are getting a bit frustrated with trying to get accurate planned dates.

I have retested after fix was applied and still getting random dates created with replanning for the start dates and therefore end planned dates.

Please see attached document with screen shots of the issue.

Re-ran plan after time sheet entry, still remaining assigned time for activity. Replan, gave start date in January. Not the start date of project when re-plan was set for?

It is normal, if you replan the project from far in the past (1/1/19) . If the assigned resource has a small availability (even 0,1 is enough) then the task is planned from the date of this availability.

Hi Babynus, That does not work for us. If we have a validated start date and duration, when you first create the activity with auto planning ticketed. It takes the start date as the planned date (ie. validated start and planned start are the same and then calculates based on duration and availability the end date for the activity, plus availabity of assigned resource from the validated start date. There will always be activities which we wish to plan in with out a dependence and not start at the very beginning of a project which could be months before, todays date. If the person has not recorded time on timesheet then the planned start and end dates must not change with a re-planning of project.

We found before the upgrade that if when re-planning we used the project start date which could be in the past it would leave the independent activities where nothing has been recorded as actuals with no changes to planned start and end dates. Which is what we need so users can see when an activity was required. (and prioritize their work).

If some time has been recorded but not all time assigned in a timesheet then I would expect the planned start date to reflect either the original planned date or the real start date. The re-planned end date could then be based on the duration of the activity and availability of resources from the start date.

Do I need to raise this a bug? Enhancement, I really do not have to make a decision that projeQtOr is not workable with time sheets it would loose a lot of the benefits of using it.

If we have a validated start date and duration, when you first create the activity with auto planning ticketed. It takes the start date as the planned date (ie. validated start and planned start are the same and then calculates based on duration and availability the end date for the activity, plus availabity of assigned resource from the validated start date.

No.
Planned start date is not the validated start date, unless you select planning mode "must not stat before validated start date".

There will always be activities which we wish to plan in with out a dependence and not start at the very beginning of a project which could be months before, todays date.

If the task does not start at the beginning of the project, there is a reason, and IMO it is a good option to define it with a dependency.
OR possibly you can use planning mode "must not stat before validated start date"

If the person has not recorded time on timesheet then the planned start and end dates must not change with a re-planning of project.

It may in many ocasions :
- if resource is also assigned to new activity with higher priority
- if planned start date is passed and real work not entered (so task is late...)

We found before the upgrade that if when re-planning we used the project start date which could be in the past it would leave the independent activities where nothing has been recorded as actuals with no changes to planned start and end dates.

If no other new constraint changes the availability, you are right.
And this has not changed since many versions (at least V5.x)

If some time has been recorded but not all time assigned in a timesheet then I would expect the planned start date to reflect either the original planned date or the real start date. The re-planned end date could then be based on the duration of the activity and availability of resources from the start date.

The duration is used for planning only for planning mode "fix duration". All other modes don't care about duration.

Do I need to raise this a bug? Enhancement, I really do not have to make a decision that projeQtOr is not workable with time sheets it would loose a lot of the benefits of using it.

I'm afrait I don't understand what you call a bug.
What you describe seems for me a normal behavior.
Real work follow up and it's planning need to follow up the rules of effort driven capacity planning.
Planning is calculated to take into account constraints, availability and real work.
It will not always reflect what you want it to show, it will reflect the reality.

Maybe if you can describe (possible with screenshots or drawing) what you get (which data on which screen) and what you expect to get, I could understand what you need.
Also to understand what you get, I would have ot know the planning mode of your activities.