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.
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 /code.launchpad .net/~openerp- community/ openobject- addons/ fix_726185_ trunk/+ merge/88996
[2] https:/