What is your original issue/pain point you want to solve?
→ administering multiple groups (10+) and leaving the group permission checkboxes empty, after having clicked on “+add” = gets removed by clicking on “Submit” (even though the role given in the same move, gets saved as a setting).
Which are one or two concrete situations where this problem hurts the most?
–>I want to use the current configuration as a template and quickly create other roles based on it. I have to set at least one check mark for each line so that it remains - but that is not logical from the process. Would it be possible to correct it and also leave empty rows as soon as you have added them? Otherwise, if it is not intended, at least forbid +Add if no check marks are selected.
only the “Users” one and the role remain shown after clicking update
Why is it not solvable with the Zammad standard?
→ it is not obvious that the display is temporary, because you press the +Add button and the lines are added, so you expect it to stay that way after submit. Why should I assume that they disappear when they are empty? If I add empty rows in f.e. Google spreadsheet, then they remain even if they are empty when I access the spreadsheet next time.
If I had created an empty list for all groups, then I can quickly clone this role and mark the permissions for a pair of groups. For an agent I use role with 1 group with Full+10 groups ( Read, Write) permissions. If I had the empty list, I just have to check different 10 groups like in the lottery ticket. As it is implemented now, I have to always add these 10 groups anew with “+Add” for each role if earlier these 10 groups were not used and have no ticked checkboxes.
What is your expectation/what do you want to achieve?
→ would like, even if empty checkboxes are added to certain groups to the user profile or role, that they are not removed after submitting the change.
In our use case, we have potentially to define 300 roles, while each role has permissions for 20 groups out of 300 groups. If the groups are added to the interface and stay empty it’s much easier to assign the permissions, using just clone button for one role which shows all the groups and just changing the check boxes.
The approach to show all groups ( independently of either the group has permissions or not ) was used in the previous Zammad versions and was much better if someone has to handle complex permissions matrices.
In the current implementation I have to add the groups which are different for each role out of 300 by pressing +add button, the nested groups ( which is nice feature, also suppoted by us) complicates the procedure to add the groups once again. If groups have no permissions in other role we have to add them again to define the permissions in current role.
I think the possibility to keep emty groups in the role interface should be provided, as emty groups are part of configuration as well. If something has zero value, it doesn’t mean tthat it should be always hidden. Those who don’t want to see them, just don’t add them or can remove them with remove button.
And finally if the empty group is supposed to be automatically removed it’s not a good way first to allow to add it and then remove it witthout any notice. I understand that you allow to add the empty group in the role interface, just to let people to give the permissions after the group is added to the table as a next step, which is fine. But it would be much better to keep the empty groups shown and give the rights to admins to decide if they need them to be shown or not, finally as I wrote if the groups are not needed they can be removed by pressing “Remove” button.
