Fix the Admin and User Portal's User Profile Screen

[palisadoes]

Describe the bug

1. Improper capitalization and spacing with the drop down values.
2. Many pre-populated values are not required

To Reproduce
Steps to reproduce the behavior:

1. Log into the relevant portal
2. Select the User Profile
3. View the user's profile screen values

Expected behavior

1. The bug issues should be rectified in all supported languages
2. All other functionality must be maintained
3. Complete and valid tests must be added to verify your changes

Actual behavior

• See screenshot section

Screenshots

1. Improper capitalization and spacing with the drop down values. Translations for each are required
   
   
   
   
2. These pre-populated values are not required
   

Additional details

• N/A

Potential internship candidates

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

• Student Internship Programs talawa#359

[AnshulKahar2729]

Proper capitalization and spacing are correct but why prepopulated is not required.

[palisadoes]

It has very little relevance to the end user. The headings are sufficient.

[Shrijan125]

I believe there might be some confusion here. The pre-populated values are not placeholder text; they actually represent the user details stored in the database. For example, "Line1" refers to the admin's address stored in the database and it must be visible to him for making changes. Could you please clarify this further? Thank you!

[syedali237]

Can I be assigned this issue?

[akathedeveloper]

I would like to work on this issue. Could you please assign it to me?

[AnshulKahar2729]

It has very little relevance to the end user. The headings are sufficient.

@palisadoes assign me this, I will fix it but once again those pre-populated values are required. They are just looking the same in the screen shot because someone has entered the label as values.

[Abhinav232004]

@palisadoes ,Could you please assign it to me ?

[AnshulKahar2729]

It has very little relevance to the end user. The headings are sufficient.

@palisadoes assign me this, I will fix it but once again those pre-populated values are required. They are just looking the same in the screen shot because someone has entered the label as values.

@palisadoes @varshith257

[palisadoes]

@AnshulKahar2729

Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. We sometimes give exceptions for more urgent cases and sometimes we lose track, but the policy stands. You have reached your limit, please wait until your existing issues are closed before requesting more issues. You could unassign yourself from one of the other issues too.

[prashantrai-30]

Hey @palisadoes can you assign this to me.

[AnshulKahar2729]

@AnshulKahar2729

Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. We sometimes give exceptions for more urgent cases and sometimes we lose track, but the policy stands. You have reached your limit, please wait until your existing issues are closed before requesting more issues. You could unassign yourself from one of the other issues too.

Ok, you can re-assign me this, one of my PR is going to be merged soon.

[duplixx]

@palisadoes I am working on it recently in my GSoC timeline

[palisadoes]

@prashantrai-30 We have to reassign this to @duplixx

[yashaghane21]

@duplixx please assign this issue to me .

[duplixx]

Hey @yashaghane21, I have already fixed this issue in my GSoC idea

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