Inconsistent Field Labels in Change Password Section - Enatega Multivendor Customer App

Open Beginner friendly
#1,478 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript
Domain
mobile

Research direction

Start by locating the Change Password section in the Enatega Multivendor Customer App and inspect the two password-field labels. Verify the screen on Android and iOS, then confirm that the first field reads “Current Password” and the second reads “New Password.”

Written by the indexing model from the issue text.

Description

Describe the bug
In the Change Password section of the Enatega Multivendor Customer App, there is an inconsistency in the labeling of the password fields. The current configuration has the first field labeled as "Change Password," which is confusing and doesn't align with standard password change procedures.

To Reproduce
Steps to reproduce the behavior:

Navigate to the Change Password section in the Enatega Multivendor Customer App.
Observe the labels of the password input fields.
Expected behavior
The first field should be labeled as "Current Password," and the second field should be labeled as "New Password."

Screenshots
image

Smartphone:

Device: Android and iOS

Dominant language
JavaScript
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gray-mueller/restaurant-online-ordering-app-using-java

All issues in gray-mueller/restaurant-online-ordering-app-using-java

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.