Aakrity Tibrewal added a comment - 27/Apr/2025 12:38 PM Atlassian Update - 27 April 2025 Hello, Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself. Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap. Please note the comments on this thread are not being monitored. You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here. To learn more about our recent investments in Crowd Data Center, please check our public roadmap . Kind regards, Crowd Data Center

Rob Kooper added a comment - 08/Jul/2010 5:21 AM This would be helpful in our case. We use crowd to manage jira as well as subversion and I would like to give the admin of a jira project the right to edit members in the group. This group is then used to give write access to subversion.

Preston Tollinger added a comment - 19/Dec/2009 1:50 AM To get event fancier (thought the basic concept is good as well), allow the administrator to delegate approval of group additions to specific users or groups. e.g. Allow members of dev_managers to approve/edit membership in group 'developers' but not in other groups. This would be great to decrease the admin load in confirming a person should have group membership.