long term scheduling doesn't work across projects

[Grzegorz Grzelak (OpenGLOBE.pl)]

When you have two projects with two phases each. Every phase has two tasks. You have only one the same resource for all tasks in both projects. This resource is in Resource Allocation in all phases. And user for the resource is a member of both projects. The resource-user has Working period from standard demo data. So it is only one resource-user for all 8 tasks. When you make "Compute Phase Scheduling" for all projects the system schedules for the same time tasks from two projects for the same resource-user. Scheduling works correctly only within project. Scheduling doesn't see that resource-user is busy on another project task.

[Lorenzo Battistini (elbati)]

Hello, is there any plan to correct this?
If wizard schedules more than 1 task for the same user at the same time, 'project_long_term' module is totally useless, right?

[maulik vadhar (er-maulikvadhar)]

Hi

Yes in resource screen we have a line named as Resource Allocation and in
that a field is Availability....
So you can try that one so that resource would not be allocated 100%
particular phase

So try this one as above may be it will be helpful to you, and pls revert
me back for this

On Tue, Jan 17, 2012 at 9:14 PM, Launchpad Bug Tracker <
<email address hidden>> wrote:

> You have been subscribed to a public bug by Lorenzo Battistini - Agile BG
> - Domsense (elbati):
>
> When you have two projects with two phases each. Every phase has two
> tasks. You have only one the same resource for all tasks in both
> projects. This resource is in Resource Allocation in all phases. And
> user for the resource is a member of both projects. The resource-user
> has Working period from standard demo data. So it is only one resource-
> user for all 8 tasks. When you make "Compute Phase Scheduling" for all
> projects the system schedules for the same time tasks from two projects
> for the same resource-user. Scheduling works correctly only within
> project. Scheduling doesn't see that resource-user is busy on another
> project task.
>
> ** Affects: openobject-addons
> Importance: Wishlist
> Assignee: OpenERP R&D Addons Team 1 (openerp-dev-addons1)
> Status: Confirmed
>
> --
> long term scheduling doesn't work across projects
> https://bugs.launchpad.net/bugs/726185
> You received this bug notification because you are a member of OpenERP
> Services Experts, which is subscribed to the bug report.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-expert-service
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~openerp-expert-service
> More help : https://help.launchpad.net/ListHelp
>

[Lorenzo Battistini (elbati)]

2012/1/18 maulik vadhar <email address hidden>:
> Hi
>
> Yes in resource screen we have a line named as Resource Allocation and in
> that a field is Availability....
> So you can try that one so that resource would not be allocated 100%
> particular phase
>
> So try this one as above may be it will be helpful to you, and pls revert
> me back for this

Hello,

the availability field does not help (in openerp 6.1 it does not even exist).
Two separate projects are always considered independent by the scheduler.

If you look at 'schedule_phases' method[1], you can see that 'faces'
library is called once for each project, independently by the others.

In OpenERP 6.1 it is a bit different. I proposed a patch[2]
With those changes, launching the 'schedule phases' wizard and
selecting 'compute all projects', faces should be able to avoid
resources overlapping.

Feedbacks are welcome :-)

[1] http://bazaar.launchpad.net/~openerp/openobject-addons/6.0/view/5005/project_long_term/project_long_term.py#L434
[2] https://code.launchpad.net/~openerp-community/openobject-addons/fix_726185_trunk/+merge/88996