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

Fix the UserPortal/Organizations Screen in the develop-userTypeFix branch #1685

Closed
palisadoes opened this issue Mar 8, 2024 · 6 comments
Closed
Assignees
Labels
bug Something isn't working unapproved

Comments

@palisadoes
Copy link
Contributor

palisadoes commented Mar 8, 2024

NOTE

  1. This issue will require close coordination with persons assigned issues in the reference section.
  2. This work will need to be done on the develop-userTypeFix branch

Describe the bug

  1. The schema doesn't apply a person's userType by organization.
  2. The userType is currently a part of the User definition not part of a userOrganization definition or something similar.
    1. This means that an Admin is an Admin for all organizations which grants the same rights as a SuperAdmin. This is not the intention.
    2. This has created historical confusion in the Admin and SuperAdmin roles.
  3. We have created the develop-userTypeFix branch from the develop branch to fix this.
    1. All remedial work is being done on the develop-userTypeFix branch
    2. When the development work is complete on the develop-userTypeFix branch it will be merged back into develop
    3. This is planned to be completed shortly
  4. This issue was created to apply the desired functionality for the screen in this issue's title

This needs to be resolved as it is a showstopper bug.

Expected behavior

These conditions must apply:

  1. The userType must be applied per person per organization.
  2. Each SuperAdmin must be a SuperAdmin for all organizations
  3. All other userTypes would be on a per organization basis
  4. This has already been implemented in the develop-userTypeFix branch of Admin and the API. Your role will be to apply the change to the screen in this issue's title to the develop-userTypeFix code.
  5. The new functionality of userType must be unchanged.
  6. No other features must be affected
  7. All tests must be valid and pass

Screenshots

The current API schema:

image

The new API schema:

image

Describe alternatives you've considered

  • N/A

Approach to be followed (optional)

  • See above

Additional context

  1. This is going to require someone with experience with the repo, or proven long term experience with typescript, MERN, and / or graphQL in their GitHub profile
  2. Research these issues for context with the new userType functionality:

Related issues:

  1. API: Fix the usage of userType talawa-api#1711
  2. Mobile: Fix the usage of userType talawa#2373
  3. Admin: Fix the usage of userType #1445
  4. Update the Organization People Screen Design and Functionality #1451
  5. Update the Community Users Screen Design and Functionality #1452
  6. Update adminApproved to expected functionality in the develop-userTypeFix branch talawa-api#1862
  7. Update thedevelop-userTypeFix branch with the latest features from develop - Fundraising / Recurring Events talawa-api#1904
  8. Admin: Fix the usage of userType #1445
  9. Fix the MemberDetail Screen in the develop-userTypeFix branch #1682
  10. Fix the OrganizationPeople Screen in the develop-userTypeFix branch #1683
  11. Fix the User/Users.tx Screen in the develop-userTypeFix branch #1684
  12. Fix the UserPortal/Organizations Screen in the develop-userTypeFix branch #1685
  13. Fix the UserPortal/Home.tsx Screen in the develop-userTypeFix branch #1686

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

@Anubhav-2003
Copy link

@palisadoes Respected sir, I want to work on this issue. Thank you.

@Anubhav-2003
Copy link

Anubhav-2003 commented Mar 10, 2024

@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.

@adi790uu
Copy link
Contributor

@Anubhav-2003 you need to remove the usage of userType field in the particular screen.

@adi790uu
Copy link
Contributor

@Anubhav-2003 ping me on slack, we can coordinate there.

@Anubhav-2003
Copy link

@adi790uu OK got it mate. Coordinating with you on slack. Thank you.

@adi790uu
Copy link
Contributor

@palisadoes we don't need fixing in this screen we can close this issue.

@palisadoes palisadoes closed this as not planned Won't fix, can't repro, duplicate, stale Mar 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working unapproved
Projects
None yet
Development

No branches or pull requests

3 participants