-
-
Notifications
You must be signed in to change notification settings - Fork 712
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
Fix the UserPortal/Organizations
Screen in the develop-userTypeFix
branch
#1685
Comments
@palisadoes Respected sir, I want to work on this issue. Thank you. |
@palisadoes Respected sir, I had some questions. As it stands currently in the develop-userTypeFix branches, the organizations screen in the userPortal is getting rendered. Is there anything in particular that you want me to fix in that layout or screen. Because as per my observation, it is the admin side of the Portal that is having issues in rendering. For instance the 'users' panel below MyOrganizations is not getting rendered. Also, the organization manage dashboards are also not opening. Should not I be fixing those? or the admin side of the portal? Thank You. |
@Anubhav-2003 you need to remove the usage of userType field in the particular screen. |
@Anubhav-2003 ping me on slack, we can coordinate there. |
@adi790uu OK got it mate. Coordinating with you on slack. Thank you. |
@palisadoes we don't need fixing in this screen we can close this issue. |
NOTE
develop-userTypeFix
branchDescribe the bug
userType
by organization.userType
is currently a part of theUser
definition not part of auserOrganization
definition or something similar.Admin
is anAdmin
for all organizations which grants the same rights as aSuperAdmin
. This is not the intention.Admin
andSuperAdmin
roles.develop-userTypeFix
branch from thedevelop
branch to fix this.develop-userTypeFix
branchdevelop-userTypeFix
branch it will be merged back intodevelop
This needs to be resolved as it is a showstopper bug.
Expected behavior
These conditions must apply:
userType
must be applied per person per organization.SuperAdmin
must be aSuperAdmin
for all organizationsuserType
s would be on a per organization basisdevelop-userTypeFix
branch of Admin and the API. Your role will be to apply the change to the screen in this issue's title to thedevelop-userTypeFix
code.userType
must be unchanged.Screenshots
The current API schema:
The new API schema:
Describe alternatives you've considered
Approach to be followed (optional)
Additional context
userType
functionality:Related issues:
adminApproved
to expected functionality in thedevelop-userTypeFix
branch talawa-api#1862develop-userTypeFix
branch with the latest features fromdevelop
- Fundraising / Recurring Events talawa-api#1904MemberDetail
Screen in thedevelop-userTypeFix
branch #1682OrganizationPeople
Screen in thedevelop-userTypeFix
branch #1683User/Users.tx
Screen in thedevelop-userTypeFix
branch #1684UserPortal/Organizations
Screen in thedevelop-userTypeFix
branch #1685UserPortal/Home.tsx
Screen in thedevelop-userTypeFix
branch #1686Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship
The text was updated successfully, but these errors were encountered: