c2c-oerpscenario team mailing list archive

[Normunds <718890@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

OpenERP stable 6.0.1

As ver. 6.0 openerp project object was linked to account.analytic.account there are logical inconsistence. When user opens parent project, analytic account view is displayed instead of parent project view (not like in project.tasks project.project relation, what is ok).
This is wrong, because it is NOT desirable, that project users view analytic accounts, even if project is almost the same as analytic account in ver.6 now.
This will also lead to browse problems in parent project for users with limited rights in certain multicompany setups for example:
Define project structure like:

instead setting one root "All Projects":
set:
Company A Root Project (Appropriate Analytic Account belongs to Company A)
Company B Root Project (Appropriate Analytic Account belongs to Company B)

It will lead for limited user, when browsing for parent project an error:
"
AccessError
Operation prohibited by access rules, or performed on an already deleted document (Operation: read, Document type: Analytic Account).
"
What is theorethically is right, because we do not want limited user see Analytic Accounts for another company. But then limited user cannot browse on projects - and this leads to broken functionality.

** Affects: openobject-addons
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/718890

Title:
  wrong logic in module Project in field parent_id

Status in OpenERP Modules (addons):
  New

Bug description:
  OpenERP stable 6.0.1

  As ver. 6.0 openerp project object was linked to account.analytic.account there are logical inconsistence. When user opens parent project, analytic account view is displayed instead of parent project view (not like in project.tasks project.project relation, what is ok).
  This is wrong, because it is NOT desirable, that project users view analytic accounts, even if project is almost the same as analytic account in ver.6 now.
  This will also lead to browse problems in parent project for users with limited rights in certain multicompany setups for example:
  Define project structure like:

  instead setting one root "All Projects":
  set:
  Company A Root Project (Appropriate Analytic Account belongs to Company A)
  Company B Root Project (Appropriate Analytic Account belongs to Company B)

  It will lead for limited user, when browsing for parent project an error:
  "
  AccessError
  Operation prohibited by access rules, or performed on an already deleted document (Operation: read, Document type: Analytic Account).
  "
  What is theorethically is right, because we do not want limited user see Analytic Accounts for another company. But then limited user cannot browse on projects - and this leads to broken functionality.