There are some rules I'm try to learn better, so I ask for more informations about what I'm experimenting.
1) I have created a new project, with a project manager (a direct attribute of project using the drop down menu), but the project manager is not able to create or modify anything in the project until I assign him to the project as project manager.
Should this assignment be automatic, or I am always forced to make this duplicated action?
2) I've created a project in which I assign two rules to the same resource, one rule as project manager, and one as developer.
But, finally, he may only act as developer, because no project manager permissions are ever permitted to him by projeqtor.
Shouldn't he have the sum of permissions, instead, and act both as project manager and developer?
Thanks,
Tonino
You must read: Stakeholder definition and Project affectation sections.
http://manual.projeqtor.org/html_en/Concept.html#stakeholder-definition
You will have a explaination about profile define to the user level and project affectation level.
I've read carefully those pages, but they do not answer to my question.
They only cover assigning one rule to a resource in a project, or different rules in different projects.
But projeqtor permits a user having more rules in same project, but it uses always the last assigned rule.
I did two different tests, assgning two rules to the same user in same project.
In first test, I've assigned first a rule as project manager, then a rule as internal developer: user cannot manage project.
In second test, I've assigned first a rule as internal developer, then a rule as project manager: user is now able to manage project.
So, when there are more rules for the same person, the last one wins (while I feel if should have both permissions enabled in same time).
Regards,
Tonino
What defines access to screens and features is the user profile (defined in user screen).
Profile defined in project affectation give to resource (user), project data visibility and access rights.
In your case, if a human resource is affected to one project as project leader and a other project as a project member.
This human resource doesn't have the same access rights for each project.
So, if you want that this human resource got all functionalities to project leader, you must set the user profile to "Project leader".
May be, an issue that will be fixed in version 5.3 can have you mislead.
https://track.projeqtor.org/view/main.php?directAccess=true&objectClass=TicketSimple&objectId=1903
I'm speaking of a well different case.
In my case, a human resource is affected to one project as project leader and to the same project as project member.
He has two rules: project leader and developer in same project.
Projeqtor permits to do that, only, the last rule assigned wins and overrides the permissions of first rule assigned.
So, it would not be allowed to play as project leader and developer, but only as the last rule assigned.
your use case is very specific and was not thought about.
have 2 affectations on same project for same resource but each with different profile.
the use case was not planned, but in my opinion behavior is correct.
if resource has several affectations for one project then the last one give the current rights. otherwise, there is no need to create several affectations
In this case it is not important because one rule is project leader, but it could be important if same person has two minor rules with different permissions.
Anyway, it is important I have seen how to repeat the problem, so I know I can look for a solution playing around rules.
Regards,
Tonino
If you need to have an addition of two profile rights, you have to define the profile that cumulates these rights.
If it was a fixed schema, it would be right, like project leader + developer.
But if rules may be various, it would not be conveninet to multiply combined rules.
Let's think about :-)., it is not urgent nor blocking.