#3598 Improve project permissions admin
closed
Admin
2015-08-20
2012-01-17
No
During testing, users were very confused by the usergroup and permissions screens. They had trouble figuring out how to add a user to their project and what the various permissions meant. One suggestion was to combine the screens and explain how the two areas interacted. Whatever we decide to do here, we should add much more explanatory text about how the permissions system works. If we do keep the pages separate, there should be a link on each explaining that some related changes need to be made on the other page.
I made the inheritance checking a little smarter and added a test for it.
Those thing are fixed, but there is still a problem with the event handling. I took a video capture this time - figured that would be easier than explaining: http://screencast.com/t/YcefEPhVqyEO
This was only showing up in Chrome for me.
Looks like the double-event problem is gone, but I found something else.
When deleting, things work as expected if you click the name of the user to delete, but if you click the delete icon, the click event is sent to the row below. Example: http://screencast.com/t/8gUUmnrgCb
Also, it might be worthwhile to put a 'Cancel' link to the right of the new user text box.
Ok, it's really fixed for real this time. There was some overlapping of the icons that was making that happen if you clicked the icon near the bottom. Updates are on both sftheme and allura branches.
Okay, don't kill me. There's just one more thing: http://screencast.com/t/OyhRcdj4U
At the end of the video, you can see that Admin is clearly inheriting that permission from Developer, but the tooltip says it's inherited from Member. That could end up being confusing for users.
If you could fix that I swear I'll merge it next time. :)
Looks great. Merged to dev.