| Age | Commit message (Collapse) | Author |
|---|
|
Purpose
=======
Access group terminology is missleading. Yous have to be manager to administrate
an application. This task consists to rename groups to be understandable for everyone.
Groups should be reorganised on the users form to be more explicit.
Specification
=============
1/ Rename 'Manager' to 'Administrator' in users groups.
2/ Define a hierarchy on access groups by using the category_id in the manifests
A category 'Operations/Project' will create a category Project with a parent
category 'Operations', and something smart is already developed (in modules/db.py)
to avoid duplicating categories.
3/ Add a group in expenses to be able to approve expenses reports for my team.
4/ Add a group in timesheets to be able to approve timesheets for my team.
5/ Remove partially the useless crap in ir_module_category_data.xml
6/ Sort access rights groups on users form according to its parent category
closes odoo/odoo#29362
Signed-off-by: "Yannick Tivisse (yti)" <yti@odoo.com>
|
|
User 1 simply becomes a technical user (inactive, no password).
|
|
OPW 1859364
|
|
* reporting: remove report.event.registration as it can be replaced by
pivot and graph views on event.registration model directly. The
custom SQL view does not add any valuable information;
* event: correctly take limitations from event category and check
minimum seats is lesser or equal to maximum seats;
* event: reorganize a bit the form view
* avoid some kind of random ordering of buttons;
* move seats availability directly in the form view;
* ticket page is now used only for ticketing purpose, not a mismatch
with seats;
* registration: attendees can be set as done only for confirmed events
to avoid confusion when working with draft events;
Misc usability
* event.type: rename event type to event category to have a unified
term across various event addons;
* event: stop tracking active field as it does not add interesting
information; it should not toggle everyday;
* event: track location as it does add valuable information;
* event: rename some labels to ease user experience;
* event.mail: add missing description and rec name;
|
|
* event, website_event, website_forum,
* website_hr_recruitment, website_sale
Website access rights were buggy. The editor assets and website editor
assets have to be loaded together to work so the previous behavior
which only loaded one with the restricted access right was not right.
Also, people which had the "Manager" access right for model like event
or job only got access to creation and edition of those objects if they
had the full access to website access rights.
Now the website module creates the two same groups :
* group_website_publisher: load all editor assets, give access to
page creation for model the user has access (event, job, ...) and
edition of those pages
* group_website_designer: implies the first one and give access in
creation and edition of all pages + access of all website menus
The manager access rights for event, product, jobs, etc now implies
the group_website_publisher group for the user (so that the manager
have the editor assets and editor ui).
Note: some python codes use the group_website_publisher for no right
reason, this has to be adapted.
|
|
Add a link in the general settings to access easily the default_user form view in order to modify the default access rights
The default_user manager rights declarations in all the applications have been move in a noupdate="1" definition to avoid the manual configuration overwrittings
|
|
event management
In the interface using the email scheduler of events is limited to a group
that is not activated by default. However by default emails are sent and
therefore cannot be configured by the event maanger.
As managers should always be able to configure sent emails we decided to
remove the group and always give access to the email scheduling tab of the
event form view.
|
|
|
|
Changed term 'subscription' to 'registration' in event, event_sale,
website_event, website_event_sale modules
|
|
Coming from a bug in web_settings_dashboard. Invited user didn't have any rights
when created from the dashboard, which was leading to an error.
This bug leaded to a new discussion. Better to have basic employee having user
rights for all main applications. For bigger entreprises there is an admin that
will carefully remove extra rights, if necessary. The target is small businesses,
it makes sense that every way to create a user gives the same result.
In conclusion, each new user has a full access to the applications by default
How is it implemented ?
We added an inactive default user which original access right to the groups
'base.group_user' and 'base.group_partner_manager' in base. Each
application will extend the default user's access right by adding the maximal
access right for this application.
On user creation, we will use by default the 'group_id' field from the default
user. We will in the same time remove the ugly 'default_groups_ref' key which
was passed sometimes in the context for some fields in some views, and sometimes
nothing.
So, the user can modify the access rights for the default user, but he should be
aware that removing project user access rights for a default user will prevent
a *created on the fly in a task* user will not be able to access the task.
|
|
Move the module category declaration in base to fit the other categories
declaration. Use event groups instead of marketing groups.
|
|
|
|
- New filter "not cancelled" for attendees management
- No more readonly nor invisibility on "minimum number of seats"
- Event questions and mail scheduling have been put under an optional
tab
|
|
bzr revid: sgo@tinyerp.com-20130626111029-e6szwugpewn3cd2g
|
|
removed now unnecessary files.
bzr revid: tde@openerp.com-20130410125117-m9ir36qhkp9fqax1
|
|
bzr revid: fka@tinyerp.com-20130222072757-0fain23pzyb8dzk9
|
|
Alexis de Lattre (Akretion)
ir.rule records are in noupdate data blocks to let the admin
alter them without fear of them being reset at next update.
Other records such as groups are in normal mode, so they
can be updated whenever necessary
bzr revid: odo@openerp.com-20121218232001-t425t4hi7qbmsip2
|
|
bzr revid: hsa@tinyerp.com-20120919085103-mmen7f0vzqvmp9bx
|
|
bzr revid: abo@openerp.com-20120725144039-o3kjxo065qhode33
|
|
- ir.rule objects are noupdate="1"
- all other objects are noupdate="0"
bzr revid: alexis@via.ecp.fr-20120713170838-pjsysliyt6twazrc
|
|
bzr revid: sgo@tinyerp.com-20120628064005-zuerrpazumf5lf1q
|
|
inclusion explicit in groups
bzr revid: rco@openerp.com-20120404090830-nteimn2kvz8nkk7h
|
|
manager group implies being in the user group too
bzr revid: qdp-launchpad@openerp.com-20120329085703-419271p8s81cl6zo
|
|
bzr revid: sgo@tinyerp.com-20120326124825-xewmd0qc82k9hk11
|
|
bzr revid: qdp-launchpad@openerp.com-20120301114523-8rrplgaojxhwdn51
|
|
bzr revid: qdp-launchpad@openerp.com-20120224133302-w3fr4nxju54zs4nh
|
|
redefinition of sale groups
bzr revid: rco@openerp.com-20111212145128-zx64v0uwf8n0lwyu
|
|
bzr revid: rco@openerp.com-20111212134354-49p2gyf93qozplll
|
|
bzr revid: rco@openerp.com-20110802130811-pkdmw43ufifz0tpj
|
|
bzr revid: rpa@tinyerp.com-20101119102525-8gyj1gmm1w29rwxu
|
|
bzr revid: hmo@tinyerp.com-20101114134821-7djwpr6nmmxu584q
|
|
bzr revid: vth@tinyerp.com-20101101124606-ia3nqngu19u8b7oa
|
|
bzr revid: fp@tinyerp.com-20101016164709-8w551aaosqx0dufu
|
|
bzr revid: psi@tinyerp.co.in-20101008105948-1qflslhcp1qla6qo
|
|
bzr revid: vir@tinyerp.com-20100809060226-jx6plkn6mafiplyz
|
|
bzr revid: amp@tinyerp.com-20100806135358-yapv8rqd34ac6oms
|
|
bzr revid: amp@tinyerp.com-20100730130247-1hvssj5z0f9gvd3a
|
|
bzr revid: amp@tinyerp.com-20100729133057-gdhqqohzpkdnq8vl
|
|
bzr revid: hmo@tinyerp.com-20100716081957-0gnd1eilovf01sbf
|
|
bzr revid: hmo@tinyerp.com-20100716064714-ivuu3ux3sayo28fh
|
|
Event :
* Change button icon for all searchview.
* Develop 'group by partner' functionality in make invoice wizard of registration form.
* change yaml as per changes in make invoice wizard.
* remove 'List of register event' wizard and put link on in event form.
* ADD 'Send a new mail' button for mail
* Improve history functionality.
* add group : event/manager and event/subscriber.
Membership .
* merge two sql query in one repor_membership file.
* develop search view of that report.
* change icon for search view.
bzr revid: hmo@tinyerp.com-20100626101340-bt77wjb8ug3a3flj
|
|
bzr revid: atp@tinyerp.co.in-20100622110023-5w6fnbtiwqyq7f6u
|
|
guidlines.
bzr revid: atp@tinyerp.co.in-20100607064312-3cl1vc0gfal7wvhe
|
|
* Removed dependency on crm.case as it is removed
* Fixes in event/registration computation as per ner changes
* Improvement in wizard
bzr revid: rpa@tinyerp.com-20100517133114-jjp82khn32m5zvjr
|
|
bzr revid: christophe@tinyerp.com-20081024070849-cjjlrvz52t67ll0m
|
