Problem description 20130412-220400
With Yogi-Group adding sanghamitta-group, by automatically system assignment setting sanghamitta to the main group, the sanghamitta authorization is coming to access, but the PM limit of the sanghamitta group isn’t set, the PM limit of the Yogi group authorization is still activ.
By leaving the Yogi group there isn’t also any change for the PM limit. It still stays and reacts as it will be Yogi fact .
Assumption:
The lowest PM-Limite should never be activ, if the lowest access authority group is not main group.
Reason fpr the assumption is, that if it should be in opposition to the assumption, there hast o have for ever the PM Limit tob e set of the lowest PM-Limite of the „ordinary member“ group.
Priority level low, of cause there is a workaround.
Workaround
If you are assigned only to « regular member » and « Yogi » and wants to assign too the sanghamitta group, then please leave the Yogi group and then send a PM to the administrator that he can assign you to the sanghamitta group. If the sanghamitta group then is assigned, please leave the group again and send again a PM to the administrator, that he can assign you again to the sanghamitta group. Now the sanghamitta group is your main group and if you want, aou can assigna gain the Yogi group but please don’t change the yogi group to your main group, otherwise your PM limit is set to 5 for the Yogi Group.
What happens here :
The sanghamitta group has a PM limit of 200, the Yogi group of 5.
If the Yogi group is set as main group and the assignment to sanghamitta as main group will be done, the Yogi PM limit is not dropped and the sanghamitta PM limit is not set.
If you leave the Yogi group, that means, that there is missing a programm step for the backtracking and so the assignment to the Yogi PM limit, fomally main group) is still in access.
There is no change, if you leave the Yogi group, the PM limit of Yogi is still in affect.
So if the Yogi group is left and the assignment of the sanghamitta group as main group is done, the problem still exists. And if you now leave the sanghamitta group, the system is evaluating, which Limit has now to be set. There it finds for example the regular member group and sets it’s limit. In this way the Yogi PM limit comes overwritten, or the assignment to this limit cancelled.
So if now again an assignment to the sanghamitta group as main group will be done, the PM Limit of the sanghamitta group comes installed. If now the Yogi group will be assigned again and it will not be main Group, but sanghamitta, there it should be set the sanghamitta PM Limit, but this is not the case, the Problem still exists. Of cause this, don't choose Yogi additional to sanghamitta, if you don't wants to be limited by Yogi PM max. Limit until the Problem is solved. Thank you.
Problem description 20130413-005047
When PM limits für the Yogi group are activ, there are green and red bars onto them appearing informations about the PM limt usage in percent. If the red bar appears, the information is also in red characters written, so you can not read the text.
Priority low, of cause there is no risk at all and the Information nice to have.
Pardon for the inconvenience.