| Age | Commit message (Collapse) | Author |
|---|
|
Steps to reproduce:
- Create a channels C with user A linked to an employee E
- Create project P with privacy_visibility='followers' meaning only visible for employees that follow P
- Add the channel C as a follower of P
- Log as user A go to Project app
Bug:
The project P is not readable for A
opw:1958386
closes odoo/odoo#32324
Signed-off-by: Simon Goffin (sig) <sig@openerp.com>
|
|
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>
|
|
|
|
This reverts commit 382fbd35204ff947c16b795ca090c97d6741fb1d.
|
|
User 1 simply becomes a technical user (inactive, no password).
|
|
The categories other extra rigths and hidden are not used now.
|
|
'remaining_hours' is defined in project as a simple
float field, manually updateable, only displayed
when the group "Time Estimation on Task" is activated.
But for now, there is no setting to active this group.
Those are legacy useless stuff, so we can remove it.
The purpose is to make 'time estimation' feature only
available when timesheet is installed.
Thie commit also split the compute methods of
'remaining_hours' and 'progress' fields to make
'remaining_hours' updateable, though inverse method.
Without splitting the compute method, the calculation
of the progress was done correctly during onchange
but not when saving.
|
|
Impacted modules: project, rating_project,
sale_service_rating and website_rating_project.
Removed modules: rating_project and sale_service_rating.
Move code to empty 'rating_project' module, in order
to kill it.
Code is not modified, simply copy/paste at the right
place in 'project' module code.
However, 'enable rating on task' options is convert
into a res.groups that can be activated from the
project settings.
|
|
|
|
Making project depending on portal, makes website_project
useless. So move all feature from one module to the other.
|
|
-> Move Subtasks mechanism from hr_timesheet to project.
-> Various functional improvements:
- Add new 'Sub-tasks' setting and 'Sub-task Project' field based on
this setting.
- Relabel 'Team Collaboration' section to 'Task Management'.
- Remove 'Customer Satisfaction' section and move setting
'Rating on Tasks' into 'Task Management' section.
- Add customer name on the project's kanban view.
- Set default value of 'Sub-task Project' field is the same project.
- Add 'Parent Task' stat button on task form view.
- Make 'Sub-Tasks' stat button visible when no parent task
|
|
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
|
|
Split project to move portal features to a new module named website_project.
Portal users may now access their projects and tasks throught the
website_portal My account page. The Backend portal menuitem is removed.
Simplify the privacy settings of project, to be visible to portal users the
project must be in 'portal' mode.
Original authors: Vipul Bhatt, Florian Wintjens
|
|
|
|
- Hide account_id field and add a required project_id field on timesheet entries
- Remove is_timesheet field: as project_id is only required for timesheet entries and not for other analytic lines, it can be used to determine wether a line is a timeheet entry or not.
- Remove project_timesheet module as all its functionalities are moved to hr_timesheet
- Replace timesheets on contract option on products by timesheets on project
- Small fixes and improvements in timesheets and projects views and groups
|
|
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.
|
|
|
|
This change avoid to display the tasks
that a user is not permitted to see
in the reporting view 'Task analysis'
Closes #4399
Courtesy of jkei
https://github.com/jkei
|
|
Followers can now be partners or channels. Partners following a document
will receive needaction, as previously. However people can follow documents
through channels. Members of a channel are able to listen to a stream
of messages using the channel. Those messages do not create needaction
messages. It is therefore possible to follow documents without receiving
too much notifications. For interesting documents subscribing with its
partner will create notification.
message_follower_ids fields is udpated. It is now a many2many to
mail.followers, not to res.partner anymore. A subscription can be either
a partner (partner_id) or a channel (channel_id).
Some access rules have been updated accordingly.
|
|
visibility and access rights modifications
[REM] portal_project: move ALL the things
- move portal access rights from portal_project and website_project_issue to project and project_issue
- move portal menuitems back to their respective module
- remove public visibility of projects
- adapt demo data to have a 'Demo Portal' project
- add correct access rights for account.analytic.line for portal users
- small view tweak (do not display 'timesheet' tab if one can't see antyhing in it anyway)
|
|
Conflicts:
addons/project/wizard/project_task_delegate.py
|
|
|
|
For privacy_visibility 'followers' or 'portal', the user should be follower of the project (not the task).
Remove public access to portal task
Fixes #2372
If no project on the task (or other rule), an employee (not a portal) can access if is follower of the task.
Follower rule is not enough as a user creating a rule will subscribe to the rule but to subscribe to record, the user should have access to it in the first place.
To make sure the snake does not bit its tail, fallback to give access on task where the user is reponsible (user_id = user.id).
Fixes #139
Adapted the tests to the new behaviour (removed not relevant and added some on creation)
|
|
Allow access to task without a project defined if the user is follower.
Fixes #3450
|
|
bzr revid: chs@openerp.com-20140425170357-iqcqqfe71mm2z0qg
|
|
bzr revid: sgo@tinyerp.com-20130605071905-o2ldzc6vxqnoe099
|
|
users + added an help on privacy_visibility.
bzr revid: tde@openerp.com-20130426130259-35j0v7lg7unxhzzp
|
|
bzr revid: sgo@tinyerp.com-20130417060441-6vnz2tiym5fawr2n
|
|
improved privacy_visibility selection of project.project; improved access rules; added tests to enforce them.
bzr revid: tde@openerp.com-20130412143719-ztjo06r900l024dm
|
|
bzr revid: sgo@tinyerp.com-20130312112700-zamjzcjp5d9nv5n0
|
|
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: cha@tinyerp.com-20121010083548-lt8oncuanvcfpqk2
|
|
bzr revid: cha@tinyerp.com-20121008131720-v1573v9zitef1whp
|
|
message_follower_ids.
bzr revid: tde@openerp.com-20120910075850-0b5sg1vljcc8gba9
|
|
use follower_ids.
bzr revid: tde@openerp.com-20120822074924-bbb5lc1w48dtebeb
|
|
- ir.rule objects are noupdate="1"
- all other objects are noupdate="0"
bzr revid: alexis@via.ecp.fr-20120713170838-pjsysliyt6twazrc
|
|
bzr revid: qdp-launchpad@openerp.com-20120628121820-r8bxfzq38fy8pcgt
|
|
bzr revid: sgo@tinyerp.com-20120628064005-zuerrpazumf5lf1q
|
|
way + some cleanup and bug fixing related to contract management
bzr revid: qdp-launchpad@openerp.com-20120614100922-5g29ui88nhqojon2
|
|
bzr revid: apa@tinyerp.com-20120613131507-1yezuu5k7dc1h9s3
|
|
bzr revid: qdp-launchpad@openerp.com-20120613090855-9tpft9kutxzgwyze
|
|
bzr revid: rco@openerp.com-20120612095835-iisiv73hqbhe9l9w
|
|
bzr revid: dbr@tinyerp.com-20120604064419-3scxoolmyj8iskw3
|
|
bzr revid: cha@tinyerp.com-20120529073311-98bkx7jlisvinrba
|
|
bzr revid: cha@tinyerp.com-20120529061415-x8salptgz19hyop2
|
|
security xml, and apply group in project_view.xml
bzr revid: jap@tinyerp.com-20120427071701-obqjn71vu7dykjki
|
|
inclusion explicit in groups
bzr revid: rco@openerp.com-20120404090830-nteimn2kvz8nkk7h
|
|
redefinition of sale groups
bzr revid: rco@openerp.com-20111212145128-zx64v0uwf8n0lwyu
|
|
bzr revid: rco@openerp.com-20111212140528-g8oxverkipswionf
|
|
bzr revid: rco@openerp.com-20110802130811-pkdmw43ufifz0tpj
|
