Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove full list of work projects in admin interfaces #1187

Open
prioux opened this issue Dec 8, 2021 · 2 comments · May be fixed by #1238
Open

Remove full list of work projects in admin interfaces #1187

prioux opened this issue Dec 8, 2021 · 2 comments · May be fixed by #1238
Assignees
Labels
Admin Features or bugs related to administrative features Enhancement Priority: Normal User Interface

Comments

@prioux
Copy link
Member

prioux commented Dec 8, 2021

We have a few places in the admin interface where the full list of all user projects is shown either in selection boxes or in tables of checkboxes. In the old days of CBRAIN when the number of users was small, it was thought the admin would use this to assign stuff to private projects. But now there are so many thousands of projects, these lists are cumbersome.

Those lists should be trimmed down to remove all private work projects. Leave only public projects, invisible projects and 'non-assignable' projects of the admins.

The view code should not be altered for normal users, presumably they don't have thousands of projects themselves.

Todo:

  1. modify the helpers for selection lists for groups
  2. check all the pages where the partial shared/_group_tables.html.erb is rendered; make sure it makes sense
@prioux prioux added Enhancement User Interface Priority: Normal Admin Features or bugs related to administrative features labels Dec 8, 2021
@MontrealSergiy
Copy link
Contributor

MontrealSergiy commented Apr 27, 2022

@prioux

1 Does phrase "public projects, invisible projects and 'not-assignable' projects of the admins." means projects owned by admin which are public, non-assignable or invisible? (that is public projects of users are should not be shown) ?

2 the size of selection boxes is actually fixed, so would putting NonAssignable, Public and Hidden projects ahead of other in select boxes might be better solution, or do you prefer just remove?
image
One use case for having usual (assignable/not-hidden/private) project listed in group_select is restricting experimental tools to their author/interested parties

@MontrealSergiy
Copy link
Contributor

@natacha-beck any opinion on that?

MontrealSergiy added a commit to MontrealSergiy/cbrain that referenced this issue May 9, 2022
MontrealSergiy added a commit to MontrealSergiy/cbrain that referenced this issue May 9, 2022
MontrealSergiy added a commit to MontrealSergiy/cbrain that referenced this issue May 11, 2022
MontrealSergiy added a commit to MontrealSergiy/cbrain that referenced this issue Jun 7, 2022
MontrealSergiy added a commit to MontrealSergiy/cbrain that referenced this issue Aug 30, 2022
@MontrealSergiy MontrealSergiy linked a pull request Sep 27, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Admin Features or bugs related to administrative features Enhancement Priority: Normal User Interface
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants