generated from hackforla/.github-hackforla-base-repo-template
-
-
Notifications
You must be signed in to change notification settings - Fork 97
Closed
Copy link
Labels
complexity: mediump-feature: User PermissionsFeature includes how user access levels / user permissions will be implemented in the productFeature includes how user access levels / user permissions will be implemented in the productrole: Back Endrole: Front Endsize: 1ptCan be done in 4-6 hoursCan be done in 4-6 hours
Milestone
Description
Overview
The "Project Leads" filter in the User Permission Search should return all users associated with a project, regardless of their access level. Currently, it only displays users with accessLevel = admin, omitting users with accessLevel = user who are also linked to projects. This results in an incomplete list of Project Leads.
Action Items
- Change the name of "Project Leads" to "Project Members" (make sure updated name fits, if not increase size of component to fit with sufficient padding)
- Update the logic powering the "Project Members" filter to include users with
accessLevel = useras well asadmin, as long as they are attached to at least one project. (refer to this issue for information about how API was previously handled Create API call to get all users who are listed as managers on a project #1771)- (Previously, it appears this was limited to only
accessLevel = admin)
- (Previously, it appears this was limited to only
- Ensure the list is displayed in the following format:
- A list of all users that are linked to projects on VRMS (only return users who manage projects)
- Project names are alphabetically sorted (first step of sorting)
- Users within each project are also alphabetically sorted by first name (2nd step of sorting)
- If a user is on multiple projects, display the user name again for each project
- UI: User full name left-aligned, associated project right-aligned under the search bar (existing UI is sufficient)
- Ensure that when a project is searched, only users within that project are displayed (sorted alphabetically, sorted by first name).
- Add/update any relevant tests to validate that both user types are returned and rendered correctly (feel free to
Resources/Instructions
- Review and update the filtering logic in the
UserPermissionSearchcomponent or API query responsible for generating the Project Leads list. - Check project-user relationship logic to confirm users with both
userandadminaccess levels are included. - Previous issue with API call: Create API call to get all users who are listed as managers on a project #1771
- Previous User Permission Search Epic
- How to test that it is working:
- Search for the project:
VRMS - Verify that both
Jack Haeger-PM(accessLevel = user) andJack Haeger(accessLevel = admin) appear in the Project Leads list - Both are linked to the
VRMSproject on the DEV build - Ensure correct alphabetical ordering of projects and users, and confirm the alignment of name/project in the UI.
- Search for the project:
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
complexity: mediump-feature: User PermissionsFeature includes how user access levels / user permissions will be implemented in the productFeature includes how user access levels / user permissions will be implemented in the productrole: Back Endrole: Front Endsize: 1ptCan be done in 4-6 hoursCan be done in 4-6 hours
Type
Projects
Status
Final QA (product)