| Age | Commit message (Collapse) | Author |
|---|
|
Purpose
=======
Avoid to show to much information to leave responsibles.
Specification
=============
- Dynamically add/remove the leave_manager_ids on the group
group_hr_holidays_responsible, on employee creation/modification
- Retrict the available employees when creating a leave. For
manager/users : Everyone. For responsibles: The employee for
who the user is responsible. Otherwise: Only me.
- Don't obfuscate the leave name on employees for who I'm the
responsible.
- Add a new SQL view for "Everyone" report. To select only the
information we want to share instead of showing the hr.leave
model directly.
closes odoo/odoo#47659
closes odoo/odoo#49765
Taskid: 2206862
Related: odoo/enterprise#9239
Related: odoo/enterprise#10021
X-original-commit: 781147dcaf1552b8f2ab687ed73034b8fd1f7352
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
|
|
Following changes needing ir.model.access on transient models too.
Remove groups declaration on the action to move it to ir.model.access
when possible.
Rules are strict by default with no unlink access by default and high
priviledge asked. Adaptations may be needed later.
Write access is given as a wizard may need to be modified in case the
action triggers an error and the user has to correct a value
account*: use account.group_account_user for all transient by default
remove account.print.journal relic
stock*: use stock.group_stock_user by default
survey: survey user can send invitations
mail: allow any employee to execute wizards
additional verifications are made to ensure they are executed
only on the documents the user has access to you
give portal access to mail.compose.message as portal still does
some actions like posting messages on the forum
add ir.rule to avoid reading somebody else messages
increase the query count because of undeterminist count
crm: saleman for lead2opp, manager for massmailing
partner manager for actions linked to partners
avoid a write in test_lead_lost
sms: any employee can send sms
mrp: mrp user can execute wizards
give unlink access as making write during do_produce operation
base_import: employees can import files
delivery: stock user can deliver
event_sale: sale user can configure the wizards
event user inherit from sale rights
gamification: employee can give badge
google_service: resolve FIXME
hr: add specific rights
manager can set a plan according to group on button
anyone who can write on an employee can register a departure
hr_expense: set rights based on buttons
hr_holidays: an approver can make a summary report
hr_recruitment: recruiter can refuse a candidate
hr_timesheet: can use the wizard if can create a timesheet
l10n_eu_service: managers can create fiscal positions
mass_mailing: same group as on mass.mailing.list
membership: accountant can create invoice from membership
payment: accountant can create a link
as the source is an account.move
keep the payment.acquirer.onboarding.wizard to system user
only as it is called during company configuration
point_of_sale: PoS manager only can use wizards
never create closing_balance_confirm_wizard records
product_expiry: stock user has rights on stock.picking
product_margin: access from accounting menus
repair: same rules as for above models
sale: set ir.rule for self wizard only
add rule from model introduced in payment to add salesman group
sale_crm: saleman can create a quotation from a lead
sale_coupon: any saleman can generate coupon
add self ir.rule
sale_product_configurator: salesman can select product variants
snailmail: employee can send letters
website: designers can write on website
website_crm_partner_assign: same rule as group on action
website_sale: sale ACL as for payment.acquirer.onboarding.wizard
website_slides: anyone can send invitation
base: base.language.*: allow employee (cf lang_install)
change.password.user: can not read change password wizard of
other users
test.*: no access is needed
Courtesy of Damien Bouvy, William Andre and Antoine Prieëls for review
of acl
|
|
We need to have a clear distinction between holidays managers and
holidays officers.
For this a number of improvements have been done in hr_holidays.
For more informations about the changes see the docstrings of hr.leave
and hr.leave.allocation.
Task #34222
Closes #19270
|
|
This commit improves leave request and allocation management through a
better integration of activities and addition of automated activities.
Several things are done in this commit :
* leave and allocation models do not inherit from mail.activity.mixin.
This commit adds the inherit so that HR users and managers can now
schedule and manage activities on leave and allocation requests. This
will help them in their daily job;
* automatic activities generation is added for leave and allocation.
Activities are generated for approval and second approval. They are also
automatically set as done when validating or unlinked when refusing or
resetting to avoid bloating users with unnecessary activities;
* a menu to configure activity types is added. Indeed HR managers should be
able to see and configure activity types related to their job;
* filters are added to be able to use the systray and to filter the kanban
view based on activities
Having automated activities allow to replace some messages and tracking
that were implemented to warn people of leave and allocation to approve
or validate. This commit therefore
* simplifies the tracking as only approved or refused state now trigger
a subtype;
* removes to approve and to validate subtypes on leave and allocation
model as well as their parent subtypes on the department. This allows
to simplify chatter a lot in hr_holidays app;
|
|
Purpose
=======
Have a clear distinction between leave and allocation requests instead of
using the same model to mix 2 different concepts.
Splitting the model will allow different business code to be run on each
model as allocations and leaves are not exactly the same thing; this
will add some code but simplify future improvements
Specification
=============
1/ Completely separate the models
Model hr.holidays has been split into leave.request and
leave.allocation.
2/ Make reporting working again by using an SQL view aggregating data
from leaves and allocations
A new report has been added in order to aggregate
datas from both allocations and requests. The views have been modified
accordingly.
|
|
PURPOSE
=======
For each and every Hr application there should be one user category (One app = one category).
SPECIFICATION
=============
HR remains as it is : Employee, Officer, Manager
Each Application should have 2 access rights: User and Manager. Example for Recruitment:
- The user has access to the recruitment process
- The manager has access to the job position configuration
Each Application should grant the employee user access right (Namely the 'HR Officer')
|
|
Several modules defines records with the external ID `base.foo_bar` while it is
created inside this module (typically menus and groups).
While there is no technical reasons to do so but this may introduce issues:
- these records will not be deleted during uninstall
- if a language is loaded before the installation of the module, it won't be
translated
The uninstallation will only remove the records with an external id linked to
this module (these would only be removed when removing base).
Installing a language before the module will drop the translations not linked
to an existing external id (as it can not be resolved).
This commit correct all the external ids tagged as from base or other incorrect
modules.
|
|
Remove 2 unsused field from calendar.event model (dir,sequence)
bzr revid: jke@openerp.com-20140115093805-1g1j1oymyxsb6kgh
|
|
bzr revid: jke@openerp.com-20131219160620-kcjrqv0uald99qqe
|
|
bzr revid: jke@openerp.com-20131126190610-ow8qwiajddi7gvdy
|
|
- added a workflow transition from refuse to draft, to allow resetting
a refused request
- resetting is now based on a can_reset field, taht is based on whether
it is my own request or I am an hr manager
- added an access right on crm_meeting that was preventing hr officers
to validate some requests
- improved form view to show reset to draft button accordingly
- added tests that helped trigerred the various bugs and improvements
bzr revid: tde@openerp.com-20130809144752-o21pjbc56o0t8fym
|
|
bzr revid: qdp-launchpad@openerp.com-20120831144244-40apxljf6juyv3nv
|
|
bzr revid: mtr@tinyerp.com-20120731103215-vc0wx0kiy7d8x6ka
|
|
bzr revid: mtr@tinyerp.com-20120731070125-n8mza516sbpta515
|
|
bzr revid: mtr@tinyerp.com-20120726123517-l9gc3tn9efl8wwep
|
|
bzr revid: stw@openerp.com-20120726114321-xx4j4acudjmgeoe6
|
|
bzr revid: fp@tinyerp.com-20111212181113-mhnnbps3ip8ls6pp
|
|
bzr revid: fp@tinyerp.com-20101229165130-jfr2h23jo7mrjqzu
|
|
bzr revid: fde@openerp.com-20101229143849-03lpmdpu5fkc6e86
|
|
bzr revid: fde@openerp.com-20101228153417-ps9ql3h4lij87jx8
|
|
bzr revid: amp@tinyerp.com-20101013132317-do4ylbfso07qdc66
|
|
bzr revid: dbr@tinyerp.com-20101007071157-z52414z1sz9h85qh
|
|
bzr revid: dbr@tinyerp.com-20101006135154-oovxhs611nk4tzso
|
|
bzr revid: amp@tinyerp.com-20100923071913-32cv0gf0l2r61s0x
|
|
bzr revid: amp@tinyerp.com-20100922062331-gchm37fo6oq60wgz
|
|
bzr revid: vir@tinyerp.com-20100922053937-5gah2r12uvewy210
|
|
bzr revid: amp@tinyerp.com-20100913131824-1au2kx7na9czsh4z
|
|
bzr revid: amp@tinyerp.com-20100906063006-gcuxdswiunwokvn4
|
|
bzr revid: amp@tinyerp.com-20100901132905-hslnywxf4zxogxdo
|
|
bzr revid: vir@tinyerp.com-20100813133645-w8nex9k1he2zjq9h
|
|
bzr revid: dbr@tinyerp.com-20100804133252-vh4vbkhmvsev0pnw
|
|
bzr revid: dbr@tinyerp.com-20100804085628-58nplf4yw8zp80dj
|
|
bzr revid: dbr@tinyerp.com-20100803131117-jkvf2a7pe955en2u
|
|
bzr revid: amp@tinyerp.com-20100727113352-r343qcc2fux21an7
|
|
bzr revid: rpa@tinyerp.com-20100628134938-23kiccr4355jfhmg
|
|
bzr revid: fp@tinyerp.com-20100611125528-mlhkzlditz2awk1k
|
|
bzr revid: nel@tinyerp.com-20100408142924-j4vvkcbcw20gdtzy
|
|
bzr revid: vir@tinyerp.com-20100407133731-6599szskqnsso9de
|
|
bzr revid: qdp-launchpad@tinyerp.com-20100317170926-zyw5frdscx3kpi1p
|
|
bzr revid: vir@tinyerp.com-20100315122750-bofdomun28eqw2ky
|
|
bzr revid: uco@tinyerp.co.in-20091212065410-1pgd5ywl3fyxtqkn
|
|
bzr revid: hda@tinyerp.com-20090924104621-7p53erkfs9xa0bev
|
|
bzr revid: mra@tinyerp.com-20090313062553-azyc55dpa7d20mit
|
|
bzr revid: fp@tinyerp.com-20090124131329-635ywxv5i4hdsh16
|
|
bzr revid: fp@tinyerp.com-20090124020317-pvob47mthxi3omf7
|
|
bzr revid: christophe@tinyerp.com-20081021153441-af1qtobtazu7rs28
|
|
bzr revid: christophe@tinyerp.com-20081017084109-i1r4zigf7wp3o6i5
|
|
bzr revid: fp@tinyerp.com-20080903224650-u1oadqv9x75atmyl
|
|
bzr revid: fp@tinyerp.com-20080903180400-df7l6wxg1zpirmmi
|
