Skip to content

[HOLD for payment 2021-12-06] Change Password - Error message not displayed in red for incorrect new password #4995

Closed

Description

@isagoico

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Launch the app and login
  2. Navigate to settings by clicking on the user avatar over LHN
  3. Click on change password
  4. Enter correct old password
  5. Enter password not meeting the requirement for new password

Expected Result:

Error message displayed in red

Actual Result:

No error message displayed and only message displayed in black about password requirement

Workaround:

None needed, visual issue.

Platform:

Where is this issue occurring?

  • Web
  • iOS
  • Android
  • Desktop App
  • Mobile Web

Version Number: 1.0.92-0

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

image

Expensify/Expensify Issue URL:

View all open jobs on GitHub

Activity

  1. MelvinBot commented on Sep 1, 2021

    @MelvinBot
    Contributor

    Triggered auto assignment to @Jag96 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  2. mananjadhav commented on Sep 2, 2021

    @mananjadhav
    Collaborator

    I had worked on the confirm password error message on this page. I would propose a very small fix here,

    We should retain the prompt and only change the color of the message when the password doesn't match the requirement. So basically remove this.state.isPasswordRequirementsVisible and change the block to the following:

    {(
          <Text style={[styles.textLabelSupporting, styles.mt1, !this.isValidPassword() && styles.formError]}>
              {this.props.translate('passwordPage.newPasswordPrompt')}
          </Text>
      )}
    
  3. PrashantMangukiya commented on Sep 3, 2021

    @PrashantMangukiya
    Contributor

    Here is my suggestion. We need to start validating (i.e. 1 capital letter, 1 lowercase letter, 1 number) new password as soon as some character entered. So as soon as start entering character in new password field, it will show message in red color due to password not match with rule initially. Now user go on typing new password and as soon as it become valid, the message shows in normal color.

    So based on my thinking I will suggest to add condition at line 150 (within PasswordPage.js file), So overall behaviour remain same and it will just show message in red color whenever new password input value is not valid.

    Code Before Update:

    {this.state.isPasswordRequirementsVisible && (
    <Text style={[styles.textLabelSupporting, styles.mt1]}>
    {this.props.translate('passwordPage.newPasswordPrompt')}
    </Text>
    )}

    Code After Update ( condition added at line 150):

    {this.state.isPasswordRequirementsVisible && (
        <Text style={[styles.textLabelSupporting, styles.mt1, (this.state.newPassword && !this.isValidPassword()) && styles.formError]}>
            {this.props.translate('passwordPage.newPasswordPrompt')}
        </Text>
    )}

    Below is the screen recording how its looks once the suggested solution implemented.

    Screen.Recording.2021-09-03.at.7.23.58.PM.mov

    I understand that External label not set with this issue. So at present consider this as my suggestion. I hope it will be helpful to someone who handle it internally. If this issue considered as external and my solution accepted then kindly invite me on Upwork once project posted. Here is my upwork profile: https://www.upwork.com/freelancers/~01c718889ed7821f82 Thanks.

  4. Jag96 commented on Sep 3, 2021

    @Jag96
    Contributor

    @isagoico was there a slack thread for this one? I didn't see one but just double-checking so I can have all the context

  5. isagoico commented on Sep 3, 2021

    @isagoico
    Author

    @Jag96 This was raised as part of our internal QA that's why there's no slack thread linked in this one.

  6. isagoico commented on Sep 5, 2021

    @isagoico
    Author

    Issue reproducible during KI retests

  7. MelvinBot commented on Sep 7, 2021

    @MelvinBot
    Contributor

    @Jag96 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  8. Jag96 commented on Sep 7, 2021

    @Jag96
    Contributor

    I think for this one we should keep the same convention from #5093, where:

    1. Initially, the passwordPage.newPasswordPrompt message shows with grey text, even when the user hasn't typed anything
    2. When the user starts typing, the passwordPage.newPasswordPrompt message shows w/ formError styles
    3. Once the requirements are met, the passwordPage.newPasswordPrompt message shows w/ grey text again, even when the user goes to the next field

    So the message will always be shown if that makes sense. @mananjadhav @PrashantMangukiya can you post updated proposals to match that convention?

  9. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Sep 7, 2021
  10. MelvinBot commented on Sep 7, 2021

    @MelvinBot
    Contributor

    Triggered auto assignment to @puneetlath (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

  11. 44 remaining items

  12. puneetlath commented on Nov 22, 2021

    @puneetlath
    Contributor

    @mananjadhav @Jag96 how's this going?

  13. mananjadhav commented on Nov 22, 2021

    @mananjadhav
    Collaborator

    PR is on the finish line. Hopefully it should get merged today.

  14. mvtglobally commented on Nov 29, 2021

    @mvtglobally

    Issue not reproducible during KI retests. (First week)

  15. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Nov 29, 2021
  16. changed the title [-]Change Password - Error message not displayed in red for incorrect new password[/-] [+][HOLD for payment 2021-12-06] Change Password - Error message not displayed in red for incorrect new password[/+] on Nov 29, 2021
  17. botify commented on Nov 29, 2021

    @botify

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.1.16-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2021-12-06. 🎊

  18. mvtglobally commented on Dec 6, 2021

    @mvtglobally

    Issue not reproducible during KI retests. (Second week)

  19. puneetlath commented on Dec 6, 2021

    @puneetlath
    Contributor

    Paid along along with n6 hold bonus. Thanks @mananjadhav!

  20. mananjadhav commented on Dec 7, 2021

    @mananjadhav
    Collaborator

    @puneetlath I received $250 for PR and $250 for n6-hold. But I guess I am eligible for company-offsite hold bonus as well.

    Also while this PR was done for a specific requirement, we also updated the form validation styles and @Jag96 mentioned here #5130 (comment) if I take it up, there'll be additional bonus, so that should be an additional $250. @Jag96 Can you please help here?

  21. Jag96 commented on Dec 7, 2021

    @Jag96
    Contributor

    @puneetlath @mananjadhav is right, we should also pay out another $250 for the company-offsite hold and then an additional $250 for the updated scope of work agreed upon in #5130 (comment). So a total of $500 additional.

  22. puneetlath commented on Dec 7, 2021

    @puneetlath
    Contributor

    Got it, no problem! @mananjadhav I've sent you an offer through Upwork for the additional $500.

  23. mananjadhav commented on Dec 7, 2021

    @mananjadhav
    Collaborator

    Thanks @puneetlath, applied.

    Thanks @Jag96

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionEngineeringExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions