Author: |
Therp BV |
License: |
no license |
Branch: |
8.0-security_and_groups_revamp_project_and_definitions |
Repository: |
aurestic/Therp-Addons |
Dependencies: |
document_definition,
project_scrum,
project_timesheet,
and
trp_external_user |
Languages: |
Markdown (20, 4.8%),
Python (201, 48.6%),
and
XML (193, 46.6%) |
Other branches: |
10.0,
10.0-5597-sorting,
10.0-before_logging_fix,
10.0-better-configuration,
10.0-minimal,
10.0-override_mail_recipients,
10.0-override_mail_recipients-improvement,
10.0-trp_project_scrum,
10.0-trp_project_scrum-travis_fluke,
10.0-trp_project_scrum-travis_fluke2,
10.0-trp_project_scrum-travis_fluke3,
10.0-trp_project_scrum2,
10.0-trp_project_scrum3,
10.0-update-autoinstall,
10.0-update_travis_yml,
10.0-update_travis_yml2,
8.0,
8.0-dead_mans_switch_therp-dont_break_with_demo_data,
8.0-new_res_fiscal_position,
8.0-project_direct_access_ext_user,
8.0-update-travis,
8.0_sale_multishop,
9.0,
and
lfreeke-patch-1 |
Other repositories: |
Bloesum/Therp-Addons,
EssentNovaTeam/Therp-Addons,
ICTSTUDIO/Therp-Addons,
InstaERP/Therp-Addons,
Mefistous/Therp-Addons,
Ray11101976/Therp-Addons,
StefanRijnhart/Therp-Addons,
Therp/Therp-Addons,
Upsyd/Therp-Addons,
alanljj/Therp-Addons,
apertoso/Therp-Addons,
asavalia/Therp-Addons,
daramousk/Therp-Addons,
diagramsoftware/Therp-Addons,
eboelsums/Therp-Addons,
garzadekoster/Therp-Addons,
gfcapalbo/Therp-Addons,
hbrunn/Therp-Addons,
iacsvrn/Therp-Addons,
intechbgd/Therp-Addons,
janverb/Therp-Addons,
kossovo/Therp-Addons,
lfreeke/Therp-Addons,
mgielissen/Therp-Addons,
mohamedhagag/Therp-Addons,
ntsirintanis/Therp-Addons,
odoobgorg/Therp-Addons,
odoousers2014/Therp-Addons,
opengest/Therp-Addons,
sunflowerit/Therp-Addons,
and
yasmanycastillo/Therp-Addons |
<h1>Therp specific adaptations for scrum</h1>
<p>Extra security for projects.</p>
<p>Depends on trp<em>external</em>user module.
Creates a new collaborator group for all those users who are collaborating
to Therp projects and sprints.
This module depends on project_scrum, the user will see: sprints,
stories, tests, meetings that are connected to projects he is a member of.</p>
<p>The "collaborators" will have only read access to all these models, except for
the tasks where they will have also write access.</p>
<p>A user that belongs to collaborator will have read access to:</p>
<ul>
<li>Projects</li>
<li>Sprints</li>
<li>Stories</li>
<li>Tests</li>
<li>Meetings</li>
</ul>
<p>that are connected to a project he is "MEMBER" of</p>
<p>and read/write access to:</p>
<ul>
<li>tasks assigned to him</li>
</ul>
<p>Group can read and create attachments.</p>