Hi,

First, thanks for your feedback. :blush:

I'm now using for a large project with several resources and hundread activities; everything went well but for the planning.
I'm using Fixed Duration for all the activities since it's the only one that considers dependencies (i.e. asap totally ignore dependencies don't know why).

1) If only fix duration shows dependency, it is because you did not set work.
ProjeQtOr is work driven, so you need to define some assigned work (or at least someleft work).
Then run planning : you'll see dependencies are taken into account !

Apart from that, I have a lot of activities assigned to a single resource (1 FTE) that starts at the same moment. The planner should take priority into consideration when planning those activities. However, I notice that quite often the planner tend to start an activity, then stop it, start another, then complete the first, instead of complete opened activities (the most reasonable option).

2) The behavior you face is because of "fix duration" planning mode.
This mode is designed to define fixed duration that you will not manage with your resources.
For instance, if you deliver a software to a customer, this one will have some testing period before you can deploy the software (but you won't know the work onvolved for customer, and possibly won't care about it)
If you set some work on "fix duration" task, it is planned like "regular beetween dates". This explains the behavior your face : ProjeQtOt tries ti dispatch the work during the hole period.
What you expect is behavor of "as soon as possible" tasks.
Try and change planning mode and run planning : you'll get what you want :woohoo:
You can use multiple update for that (will be quicker thant one by one) 😉

I'm quite confident with PHP; can you tell me how to change the planner in order to make it works like that?

Sorry, you will not need to play with the code 😛

Hi Babynus, very fast reply!!!

I set work for all the elementary activities but ASAP still didn't consider the dependencies, that's why I used fixed duration.

Any hint why asap should not take dependencies in consideration?

Any hint why asap should not take dependencies in consideration?

It does !
But it is not visible until you set some work and run planning.

Yes, it should 🙁

Maybe I got the point. Looking at the picture attached taken from my plan, planned with ASAP, seems dependencies have not been taken into consideration. Looking at table "plannedwork" cames out that activity on gantt start even if no work has been planned for; that should not be.

Apart from that, I still have problem with resource allocation I was mentioning. Below picture is taken from the resource planning.

activity 31.4.1.4.3 has 400 of priority, while ALL the other have 500.

Any idea?

About first picture, what can be source of issue :
- planning has not been run on project (check that "fix planning" is not checked and you run planning for this project)
- there is already some real work : so start date is real start date
- dependency has some negative delay that allows second task to run in parallel

About priority of task 31.4.1.4.3, it should be planned before others (as there is no other constraint)
- it really looks like planning has not been run.

Take care that to run planning on a project :
- you must select this project or one of its parents or no project (will run for all) where running planning
- "fix planning" must not be checked (this prohibs change on planning)
- project type is not "Template" (or any project type with code TMP)

If project persist, could you concider anonymising your database and send it to me (support@projeqtor.org) ?

Hi Babynus,
none of listed causes fits my case.

- None of the projects is set as "fix planning"
- ALL projects are OPE
- No real work yet (I'm in plannig)
- No negative delay on dependencies

I ran planning on topmost project many times, but still problem with resources is present.

Just another point: version I'm using was upgraded from 4.1 at every release; can be a problem on the DB?

Babynus,
I re-created the DB and re-insert all the activities to have a clean situation.

Problem arise again.

I notice that it happens in this situation:
- A1: allocated RES1 for 24hrs
- A2: allocated RES1 for 8hrs
- A3: allocated RES1 for 8hrs

The system schedule in following way:
- Monday: A1 for RES1 8hrs
- Tuesday: A2 for RES2 8hrs
- Wednesday: A3 for RES3 8hrs
- Thursday: A1 for RES1 8hrs
- Friday: A1 for RES1 8hrs

I think he schedules activities A2 and A3 since the will be completed shortly wrt A1 using ASAP.
There is a way to tell the system that, when an activity is started, this activity must be completed (is ASAP for each activity, not for the whole plan), in order to not put those activities "on-hold".

Thank You Thank You Thank You Thank You Thank You!!!!

Really cannot reproduce.
Have a look at http://demo.projeqtor.org/view/main.php (connect as manager/manager).
I created project PRG, ressource RESS1 and activities A1, A2 and A3 assigned as you describe (in days but it's the same).
Result is exactly as expected.

If you can reproduce your issue on Demo, I'll have a look.

:(:(:( Consider my project includes more then 800 activities ... very difficult to debug

Here another screenshot:

I will try to reproduce the issue, but takes a lot of time to import all the stuff...

And why not try breaking it down into sub-project in the first place (a sub project per month)
this might be a solution.
-------------------------------------------------------------------------------
Et pourquoi ne pas essayer en décomposant en sous projet dans un premier temps (un sous projet par mois)
cela serait peut être une solution.

Hi Babynus, protion, all.

First of all, is not a bug, nor a mis-configuration or whatever, just a behavior (proving how good is this tool).
I got what happened, and I would like to share it with all.

The algorithm, day-by-day, plan each activity according to:
- Previous dependencies
- Activity Priorities
- WBS position
- Planning Mode

Let us consider ASAP. See the project PRG in demo. There are 3 activities assigned to same resource; two of them have a predecessor activity executed by another resource, while the third free of dependencies. The tool then schedules A3 and the predecessor the first day, then second day, an activity with higher priority (smaller WBS) is available; the system set A3 on-hold and execute A1. Same for next day with A2. Then re-start with A3. Below a screenshot:

If we invert the WBS position, the behavior is different:

However, there are a plethora of activities (i.e. testing) that is better not to stop once started. I solved my plan by re-prioritizing the activities, however, there is a way to tell the system that, for specific activities, once a resource is booked, the activity must be completed?

Maybe an improvement suggestion.... 🙂

However, thanks for the support, this is the best PM tool I've used in my life. Congratulation!!!

It is clear that the creation of the task requires a minimum of reflection to optimize the use of the software.
But it is good that you are finding a solution to your problem.
-------------------------------------------------------------------------------------
Il est clair que la création des tache demande un minimum de réflexion afin d'optimiser l'utilisation du logiciel.
Mais il est bien que tu es trouver une solution à ton problème.

Hi prg,

Happy to read you solved your issue.

Your request about new planning mode "must not be interrupted" may look like a good idea, but would be a mess to implement and, I think, will lead to very frustrating results.
Let's concider a short exemple :
Activity A1 / Priority 1 / Resource R1 : 1 day
Activity A2 / Priority 1 / Resource R2 : 1 day , and predecessor A1
Activity A3 / Priority 2 / Resource R3 : 2 days, no predecessor planning mode "must not be interrupted"

The result would be :
Day 1 : R1 on A1
Day 2 : R2 on A2
Day 3 : R2 on A3
Day 4 : R2 on A3
As A2 is planned as "must not be interrupted", it cannot start on Day 1, as it would be interrupted on Day 2 by A2, with more urgent Priority.
So R2 has no work planned on D1.
So, if result expected is :
Day 1 : R1 on A1, R2 on A3
Day 2 : R2 on A3
Day 3 : R2 on A2
(which is the most optimized planning)
you just have to play with priorities (A1=>P1, A2=>P2, A3=>P1).

Eheh, I know.

Unfortunately there are a mess of possible planning criteria (that's why project mgmt is fantastic!!).

Mine was just an idea; let's keep it in the whish list.