Mobile - Select organization on registration

[palisadoes]

Is your feature request related to a problem? Please describe.

We are working on migrating the approval of requests to join organizations to a new Admin screen as outlined in this issue:

• Add membership request feature for ADMIN  talawa-admin#1416

Prior to this the process was:

1. New registrants joined the Community
2. Super Admins would approve the request
3. Approved registrants would login and select an organization

There were disadvantages to this approach:

1. This gave too much responsibility to the Super Admin who may not necessarily know people requesting to join in the way an Admin would.
2. The two step process where the organization was selected post approval, could have been reduced to a simpler single step.

Describe the solution you'd like

TALAWA API

• This new requirement means that:
  1. New USERs and NON_USERs will need to select an organization when registering so that the request can be directed to the correct organization's Admin screens.
  2. The setup script needs to create a single organization with a generic name on installation to facilitate registration to choice of at least one organization
  3. There can never be less than one organization in the DB
  4. The registration mutation must include organization ID information that issue Add membership request feature for ADMIN  talawa-admin#1416 will be able to detect.
  5. The current GitHub action pull request workflow needs to be updated so that the default organization is created successfully. This is in addition to the already existing test data importation test.
  6. The default organization creation mode mutation needs set the registration approval required flag to True to err on the side of caution.

TALAWA MOBILE

• This new requirement means that:
  1. The user registration screen(s) will need to prompt for the organization and use the updated Talawa API registration mutation.
  2. The screen(s) design must follow the guidelines of our Design System found here:
     • https://docs.talawa.io/docs/design/ux/ux-design-system

TALAWA ADMIN

• This new requirement means that:
  1. The user registration screen(s) will need to prompt for the organization and use the updated Talawa API registration mutation.
  2. The screen(s) design must follow the guidelines of our Design System found here:
     • https://docs.talawa.io/docs/design/ux/ux-design-system

OTHER

1. You will need to write tests for the updated code
2. All other functionality must be maintained

Describe alternatives you've considered

• N/A

Approach to be followed (optional)

• See above

Additional context

1. Related issues:
   1. API - Select organization on registration talawa-api#1703
   2. Mobile - Select organization on registration #2330
   3. Admin - Select organization on registration talawa-admin#1440
2. User definitions in the DB schema
   

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

• Student Internship Programs #359

[Dante291]

@palisadoes @Cioppolo14 I would like to work on this, please assign me

[AVtheking]

I would like to work on this issue please assign me this issue

[abhisheksharma010]

Hello, can you assign this issue to me? I can easily resolve this.

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

[palisadoes]

Removing issue assignment. No activity. No PR.

[Dante291]

@palisadoes @Cioppolo14 this need to be fixed from backend side first only then i could work on this, waiting for this PR to get merged, please assign me again.

[palisadoes]

@Dante291

1. The blocking API PR for this issue has been merged.
   1. Signup route changed talawa-api#1741
2. Please proceed with your work on this with urgency

[Dante291]

@palisadoes since you reverted the PR, I am going to wait for it to get merged again and then will start working on this

[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]

@Dante291 Are you working on this?

[Dante291]

@Cioppolo14 Yes, this need to be fixed from backend side first only then i will be able to work on this though.

[palisadoes]

1. Be aware of this too. The name and functionality of a mutation will soon change
   1. Support for user to join organizations talawa-api#1859 (comment)

[Azad99-9]

@Cioppolo14 if this issue is vacant, I would like to work on this. Please assign me.

[Azad99-9]

@palisadoes please clarify, will the generic organisation always have userRegistrationRequired field set to false. So that the users can directly register into the app.

[palisadoes]

You cannot assume this. The Admin team may change that at any time after installation.

[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]

Unassigning due to no activity or open PR.

[Azad99-9]

@Cioppolo14 this issue has a backend dependency. Please have a look, the PR blocking this issue is PalisadoesFoundation/talawa-api#1770

[Cioppolo14]

@Azad99-9 We are working on getting that one merged.

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

[palisadoes]

@Azad99-9

The API PR is now complete. You can proceed, if you are available.

PalisadoesFoundation/talawa-api#1703

[Azad99-9]

Sure @palisadoes ,@Cioppolo14 please assign me this issue.

[Azad99-9]

The backend bug needs to be fixed to proceed with this issue.

[Azad99-9]

PalisadoesFoundation/talawa-api#2242

There is a prerequisite backend issue raised for this issue.

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

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

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