[ 
https://issues.apache.org/jira/browse/VCL-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14188631#comment-14188631
 ] 

ASF subversion and git services commented on VCL-696:
-----------------------------------------------------

Commit 1635216 from [~jfthomps] in branch 'vcl/trunk'
[ https://svn.apache.org/r1635216 ]

VCL-747 - editOrAddGroup can have $ownerid undefined for add mode
VCL-696 - Improve resource group deletion options and information

groups.php:
-modified editOrAddGroup: if user has user groups available for owning resource 
groups, but all of those groups have a different affiliation from the user, use 
the full list of user groups for what can be selected as the owning user group; 
added check for user group being a special (system) group, and if so, do not 
allow the name of the group to be modified
-modified processGroupInput: do not perform checks of name of group if 
$editname == 0
-modified confirmEditOrAddGroup: display name same way as federated and 
courseroll groups if $editname == 0
-modified confirmDeleteGroup: do not allow special (system) user groups to be 
deleted

> Improve resource group deletion options and information
> -------------------------------------------------------
>
>                 Key: VCL-696
>                 URL: https://issues.apache.org/jira/browse/VCL-696
>             Project: VCL
>          Issue Type: Improvement
>          Components: web gui (frontend)
>            Reporter: Andy Kurth
>            Priority: Minor
>             Fix For: 2.4
>
>
> If you attempt to delete a resource group which is defined in the privilege 
> tree the following message appears:
> This group is currently assigned to at least one node in the privilege tree. 
> You cannot delete it until it is no longer in use.
> It would be helpful if:
> 1) The message contained information about where in the tree the group is 
> assigned.
> 2) There was a checkbox option to delete the resource group anyway.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to