Improve User Management Add and Remove Actions
Maintainers usually reply within 2 days
Assessment
This issue has not been assessed yet.
Description
Issue Description: In User Management, the Add and Remove actions for Program Chair, Division Chair, and Administrator are not clearly associated with the users they affect. The current layout can make it confusing whether the buttons apply to the available users or the current users.
Update the interface so the Add action is clearly associated with available users, while the Remove action is only associated with current users. Another option is to display current users in a table with a delete icon beside each user and place a single Add User button in the top or bottom corner of the section.
For Program Chair and Division Chair, these controls should appear after a program or division is selected. For Administrator, the controls can be displayed by default.
Expected Behavior:
Users should be able to clearly understand which action adds a new user and which action removes an existing user. The layout should visually separate adding users from removing current users and reduce the chance of selecting the wrong action.
UI Alternative 1:
UI Alternative 2:
Errors that can happen with cofusion:
- Dominant language
- CSS
- Stars
- 0
- Forks
- 9
- Avg merge
- 9d 22h
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from BCStudentSoftwareDevTeam/bcsr
-
Copy administrator menuPossibly taken @Ayeyomeday claimed this 1 day ago. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BCStudentSoftwareDevTeam/bcsr#135 · 1 assignee ·
Maintainers usually reply within 2 days
-
Enforce input type for course searchPossibly taken @johnsont7 claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BCStudentSoftwareDevTeam/bcsr#130 · 1 assignee ·
Maintainers usually reply within 2 days
-
Add Github Pull Request TemplatePossibly taken @praveendse claimed this 18 days ago. Opengood first issue
Difficulty 1/5 Under an hour Newbie friendliness 88/100
BCStudentSoftwareDevTeam/bcsr#115 · 1 comment ·
Maintainers usually reply within 2 days
-
Add CODE_OF_CONDUCT.md for Community ExpectationsPossibly taken @Dumisani-C claimed this 15 days ago. Opengood first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BCStudentSoftwareDevTeam/bcsr#110 · 1 assignee ·
Maintainers usually reply within 2 days
-
Add CONTRIBUTING.md for Contributor GuidelinesPossibly taken @mathew2005 claimed this 16 days ago. Opengood first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
BCStudentSoftwareDevTeam/bcsr#109 · 1 assignee ·
Maintainers usually reply within 2 days