USER REDESIGN: redesign the organization screen for the talawa user portal

[aashimawadhwa]

Is your feature request related to a problem? Please describe.
we are planning redesigning the user portal, this issue is a part of that redesigning.

Describe the solution you'd like
we want to redesign the organizations screen for the user portal and follow a theme similar to the talawa admin portal.

Screenshots

• Attaching the screenshots for reference.
  current situation :
  
  Desired Result:
  

  Please refer the figma file for a detailed understanding :
  https://www.figma.com/file/WksD4uIa5sQJMIk3pR4l0c/Talawa-Design-System-(Official)?type=design&node-id=3447%3A59&mode=design&t=fkgMPaaz67qLwmMz-1

Related issue : #1510 (sidenavbar is covered in this issue)

Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship PalisadoesFoundation/talawa#359

[disha1202]

Hi,
I would like to work on this

[takshakmudgal]

I'd like to work on this issue.

[aashimawadhwa]

@disha1202 assigned 👍🏼

[palisadoes]

@aashimawadhwa @disha1202

The design will need an update:

1. In the User portal the user will want to join the organization, not manage it.
2. The tiles should therefore have some way of indicating whether the user has already joined or not.

[AnshulKahar2729]

I'd like to work on this issue. Any updates?

[Cioppolo14]

@AnshulKahar2729 If the issue has already been assigned, please don't ask to be assigned. We want everyone to get a chance.

[disha1202]

Hi @palisadoes @aashimawadhwa

Here's the design for organization screen for user portal

Please take a look.

[palisadoes]

1. This is OK
2. Submit a PR when ready

[disha1202]

• This is OK
• Submit a PR when ready

Sure, I'll create a PR soon.

[palisadoes]

@disha1202

1. How will you handle the case where a person has requested to join an organization but it hasn't yet been approved? What API modifications would be required for this?

[disha1202]

@disha1202

1. How will you handle the case where a person has requested to join an organization but it hasn't yet been approved? What API modifications would be required for this?

As per my observation,

1. There are two types of organisations, one which requires the user to register and other one does not. The organisations that does not requires the user to register have the userRegistrationRequired flag defined as False.

2. For organisations with userRegistrationRequired flag defined as True the user needs to be approved by the ADMIN of the organisations.

3. When a new user registers they are supposed to select an organization to join, if the organization that the user wants to join requires users to be approved then a request is sent to the ADMIN of the organization.
   If the user does not selects any organization then they are made to join the default organization and a request is sent to the ADMIN of the default organization.

4. When an admin approves a user the adminApproved flag is set to True and the organisationId is appended to the joinedOrganizations Array.

As shown in the sample users data below

Although it will be difficult to manage the state of multiple organisations with a single adminApproved flag.
Instead it should be something similar to

joinedOrganizations: [ { organizationId: '6537904485008f171cf29924', status: 'pending'}, { organizationId: '6537904485008f171cf29924', status: 'approved'}, { organizationId: '6537904485008f171cf29924', status: 'rejected'}]

What do you think about this?
Also please let me know if I am missing something or misunderstood anything.

[palisadoes]

Thanks,

How will you handle the case where the:

1. approval is pending?
2. user wants to withdraw their join request?

Does the API support providing the necessary queries and mutations for this?

[palisadoes]

Regarding this:

• USER REDESIGN: redesign the organization screen for the talawa user portal #1511 (comment)

Yes, this will need to be done. The registration process will benefit greatly.

joinedOrganizations: [ 
  { organizationId: '6537904485008f171cf29924', status: 'pending'}, 
  { organizationId: '6537904485008f171cf29924', status: 'approved'}, 
  { organizationId: '6537904485008f171cf29924', status: 'rejected'}
]

1. You should open an issue in the API describing what you want in detail.
2. Ask to be assigned if necessary.

[disha1202]

Regarding this:

• USER REDESIGN: redesign the organization screen for the talawa user portal #1511 (comment)

Yes, this will need to be done. The registration process will benefit greatly.

joinedOrganizations: [ 
  { organizationId: '6537904485008f171cf29924', status: 'pending'}, 
  { organizationId: '6537904485008f171cf29924', status: 'approved'}, 
  { organizationId: '6537904485008f171cf29924', status: 'rejected'}
]

1. You should open an issue in the API describing what you want in detail.
2. Ask to be assigned if necessary.

Sure I'll create an issue in Tarawa API and also share the updated designs to handle pending state and option to withdraw request.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[Cioppolo14]

@disha1202 Are you working on this?

[disha1202]

@disha1202 Are you working on this?

Yes I'm working on it

[disha1202]

Hi
Here is the updated design

@aashimawadhwa @rishav-jha-mech
Please take a look

[disha1202]

Regarding this:

• USER REDESIGN: redesign the organization screen for the talawa user portal #1511 (comment)

Yes, this will need to be done. The registration process will benefit greatly.

joinedOrganizations: [ 
  { organizationId: '6537904485008f171cf29924', status: 'pending'}, 
  { organizationId: '6537904485008f171cf29924', status: 'approved'}, 
  { organizationId: '6537904485008f171cf29924', status: 'rejected'}
]

1. You should open an issue in the API describing what you want in detail.
2. Ask to be assigned if necessary.

@palisadoes
We might not require this. We already have membershipRequests in user schema which will provide the status of the requests.

And we can completely remove the adminApproved flag.

Also, I came across this comment which states that we have removed support for privateOrganizations.

joinPublicOrganization mutation which throws error if the userRegistrationRequired flag is true does not makes sense.

It should be updated to joinOrganization mutation which which creates a membershipRequest with ACTIVE status if userRegistrationRequired flag is true else works as is.

[palisadoes]

1. Take a look at this PR. It may answer your questions. If not, create an issue to implement your suggestion.
   1. Sign up route changed with bug fix and proper data importation talawa-api#1770
2. Yes, adminApproved should be removed

[palisadoes]

1. My mistake on the PR above.
2. Yes, please open an issue to fix the expected behavior

[disha1202]

Hi Here is the updated design

@aashimawadhwa @rishav-jha-mech Please take a look

@aashimawadhwa @rishav-jha-mech
Any update on this?

[aashimawadhwa]

@Disha can you make buttons like this?

[disha1202]

@Disha can you make buttons like this?

@aashimawadhwa Updated the buttons