generated from hackforla/.github-hackforla-base-repo-template
-
-
Notifications
You must be signed in to change notification settings - Fork 97
Closed
Labels
complexity: largep-feature: APIp-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 productready for dev leadAdd to issue when dev lead needs to take some actionAdd to issue when dev lead needs to take some actionrole: Back Endsize: 2ptCan be done in 7-12 hoursCan be done in 7-12 hours
Milestone
Description
Dependency
- This issue is cleared to be assigned/worked on until Create filtered permissions data component #1754 has been completed, and API issues (Create API call to get all users who are listed as VRMS Admins #1770 & Create API call to get all users who are listed as managers on a project #1771) PRs have been approved.
- This issue should be worked on and resolved from the feature branch user_permissions_search. Please pull down that branch to work on this issue.
git fetch vrms # or "git fetch upstream" depending on your remotes configuration
git branch user_permissions_search
git checkout -b [new branch name]Overview
This issue represents the final step in the User Permission Search Epic. The objective is to remove the placeholder dummy data currently used in the "User Permission Search" screen and integrate the APIs developed earlier in the Epic. Once completed, the filtered permissions data component will be fully functional and ready for production.
Action Items
- Remove Dummy Data
- Identify and remove all instances of dummy/placeholder data from the "User Permission Search" screen and filtered permissions data component.
- API Integration
- Hook up the previously created APIs to the filtered permissions data component within the following feature branch: https://github.com/hackforla/VRMS/tree/user_permissions_search:
- For Admin: Added an API that fetches all the admins #1774
- For Project Leads: 1771 - API for Fetching Project Managers #1799
- Ensure the API responses are correctly mapped to the UI elements and behave as expected.
- Hook up the previously created APIs to the filtered permissions data component within the following feature branch: https://github.com/hackforla/VRMS/tree/user_permissions_search:
- Fix Projects listed on User Profile Page
- Ensure that when a user clicks on a user's name in the search results (via both "Admins" or "Project Leads" searches) and navigates from the permissions search page to the User Profile page (e.g., https://www.vrms.io/useradmin), that the projects the user is associated with are displayed correctly.
- Currently, when a user navigates from User Permission Search, projects are not displayed on the User Profile page. The user's projects are only showing up when we navigate via
User Search - See:
file: client/src/components/user-admin/UserManagement.jsx - See comment on PR: User permissions search #1853 (comment)
- Currently, when a user navigates from User Permission Search, projects are not displayed on the User Profile page. The user's projects are only showing up when we navigate via
- Ensure that when a user clicks on a user's name in the search results (via both "Admins" or "Project Leads" searches) and navigates from the permissions search page to the User Profile page (e.g., https://www.vrms.io/useradmin), that the projects the user is associated with are displayed correctly.
Screenshots of current & expected behavior
User Profile page when navigating from User Permission Search (note that NO projects are displayed)

User Profile page when navigating from User Search (note that projects are correctly displayed)

- Testing
- Verify the full flow from user input to permission search results.
- Ensure that the search results update dynamically based on input filters.
Resources/Instructions
- Low-fi mockups created by Bonnie / Jack - see page 2 of mockups
- This issue is part of this epic: Epic - User Permission Search #1737
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
complexity: largep-feature: APIp-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 productready for dev leadAdd to issue when dev lead needs to take some actionAdd to issue when dev lead needs to take some actionrole: Back Endsize: 2ptCan be done in 7-12 hoursCan be done in 7-12 hours
Type
Projects
Status
Final QA (product)

