Cannot create applicant address as hr/officer

Bug #806522 reported by Aline (OpenERP)
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Fix Released
Low
OpenERP R&D Addons Team 1
Odoo Web Client
Won't Fix
Low
OpenERP R&D Web Team

Bug Description

tested in web, chrome (trunk)
in a db with hr_recruitment installed, create a user with groups hr/officer. Log you as this user. Go to Human Resouces / recruitment / applicant. Create a new one. then click on "create partner" and create partner in the popup. bug which occurs only the first time you are loged as officer. The second time, you have this error :

You can not read this document (crm.claim) ! Be sure your user belongs to one of these groups: Sales / Manager, Sales / User.

this error is wrong because the user is by default in the partner manager group ... as partner manager, he should be able to create a partner from the applicant view

Related branches

Changed in openerp-web:
assignee: nobody → OpenERP R&D Web Team (openerp-dev-web)
Changed in openerp-web:
assignee: OpenERP R&D Web Team (openerp-dev-web) → nobody
affects: openerp-web → openobject-client-web
Revision history for this message
Vishal Parmar(Open ERP) (vpa-openerp) wrote :

Hello,

I have checked this issue and I have faced the following two problem.

@Web-Team: The attrs does not work properly in "Create Partner" button.

@Addons-1 Team : When I am assigned the "Partner Manager" group to the user it will allow to create a partner.

But When I am installed a crm_calim module then it will shows the "Access Error :You can not read this document (crm.claim) ! Be sure your user belongs to one of these groups: Sales / Manager, Sales / User"

So give this object's rights to "Partner Manger" groups.

Thanks.

Changed in openobject-addons:
assignee: nobody → OpenERP R&D Addons Team 1 (openerp-dev-addons1)
importance: Undecided → Low
status: New → Confirmed
Changed in openobject-client-web:
assignee: nobody → OpenERP R&D Web Team (openerp-dev-web)
importance: Undecided → Low
status: New → Confirmed
Changed in openobject-addons:
status: Confirmed → In Progress
Revision history for this message
DBR (OpenERP) (dbr-openerp) wrote :

Hello Aline,

Its fixed in lp:~openerp-dev/openobject-addons/trunk-bug-806522-dbr
branch. It will be merge soon with trunk addons.

Revision ID : 4888 <email address hidden>
Revision No : 4888

Thank You.

Changed in openobject-addons:
status: In Progress → Fix Committed
Revision history for this message
OpenERP Majordomo (openerp-majordomo) wrote : OpenERP Majordomo Message

**automated message**
Thanks a lot for reporting this bug and contributing to OpenERP. Unfortunately the OpenERP Web Client project is not going to be developed further after the 6.0 series. As of 6.1 a newer and better web frontend known as the OpenERP Web project[1] will be available.
Our R&D developers normally work in Launchpad to fix bugs for the next release, but there will be no next release for the current OpenERP Web Client. As our resources are limited, all further R&D efforts from the Web team are dedicated to finish the new 6.1 OpenERP Web project[1].
This bug will be closed as "Won't Fix" to show that R&D won't be able to work on it.

Bugs affecting customers in production of course continue to be handled via the OpenERP Enterprise (OPW) maintenance service, and this is the recommended way to have them corrected directly in the 6.0 LTS stable branch.
You can find more details about all of this in the FAQ of our Bug Management Policy documentation[2].

If you are interested, you should soon be able to beta-test the new OpenERP Web 6.1 (this will be announced on OpenERP Community channels).

Thank you for your contributions and for your understanding!

[1] https://launchpad.net/openerp-web
[2] http://bit.ly/openerp-bugs-faq (FAQ #4)

Changed in openobject-client-web:
status: Confirmed → Won't Fix
Changed in openobject-addons:
status: Fix Committed → Fix Released
Revision history for this message
qdp (OpenERP) (qdp) wrote :

fix released at revision 5096. (see the life of merge proposal for the history)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.