Skip to content

[HOLD for payment 2024-01-11] [$500] Status - Unable to set custom time after selecting the duration #33423

Closed

Description

@kbecciv

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


Version Number: v1.4.15-4
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

  1. Go to Settings > Profile > Status.
  2. Click Clear after.
  3. Select 30 minutes.
  4. Click Clear after.
  5. Click Date under Custom.
  6. Select a different date.

Expected Result:

The selected date is saved.

Actual Result:

The selected date is not saved.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6322802_1703170066823.bandicam_2023-12-21_21-40-14-801.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01f4c9ce5463b9747c
  • Upwork Job ID: 1737863065032630272
  • Last Price Increase: 2023-12-21
  • Automatic offers:
    • paultsimura | Contributor | 28067990
Issue OwnerCurrent Issue Owner: @tylerkaraszewski

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 21, 2023
  2. changed the title [-]Status - Unable to set custom time after selecting the duration[/-] [+][$500] Status - Unable to set custom time after selecting the duration[/+] on Dec 21, 2023
  3. melvin-bot commented on Dec 21, 2023

    @melvin-bot
  4. melvin-bot commented on Dec 21, 2023

    @melvin-bot

    Triggered auto assignment to @adelekennedy (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  5. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Dec 21, 2023
  6. melvin-bot commented on Dec 21, 2023

    @melvin-bot

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  7. melvin-bot commented on Dec 21, 2023

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat (External)

  8. paultsimura commented on Dec 21, 2023

    @paultsimura
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Changing date in Status' DatePicker does nothing.

    What is the root cause of that problem?

    When selecting the date value, the actual form's value of the wrapping <FormProvider> is not updated because the DatePicker is not properly wrapped in the <InputWrapper>

    What changes do you think we should make in order to solve the problem?

    We should use <InputWrapper> here:

                    <InputWrapper
                        InputComponent={DatePicker}
                        inputID="dateTime"
                        label={translate('statusPage.date')}
                        defaultValue={DateUtils.extractDate(customClearAfter)}
                        minDate={new Date()}
                    />

    <DatePicker
    inputID="dateTime"
    label={translate('statusPage.date')}
    defaultValue={DateUtils.extractDate(customClearAfter)}
    minDate={new Date()}
    />

    What alternative solutions did you explore? (Optional)

  9. parasharrajat commented on Dec 22, 2023

    @parasharrajat
    Member

    @paultsimura's proposal looks good to me.

    🎀 👀 🎀 C+ reviewed

  10. melvin-bot commented on Dec 22, 2023

    @melvin-bot

    Triggered auto assignment to @tylerkaraszewski, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

  11. 25 remaining items

  12. melvin-bot commented on Jan 11, 2024

    @melvin-bot

    Issue is ready for payment but no BZ is assigned. @michaelhaxhiu you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!

  13. adelekennedy commented on Jan 15, 2024

    @adelekennedy
    Contributor

    @parasharrajat bump on the checklist

  14. adelekennedy commented on Jan 15, 2024

    @adelekennedy
    Contributor

    Payouts due:

    Contributor: $500 @paultsimura (Upwork)
    Contributor+: $500 @parasharrajat (NewDot)

  15. parasharrajat commented on Jan 16, 2024

    @parasharrajat
    Member

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    Regression Test Steps

    1. Go to Settings > Profile > Status
    2. Click "Clear after"
    3. Click Custom > Date
    4. Select a date in the future
    5. Click "Save"

    Do you agree 👍 or 👎 ?

  16. adelekennedy commented on Jan 17, 2024

    @adelekennedy
    Contributor

    I'll kick it to @tylerkaraszewski for any changes/other thoughts on the regression test but that makes sense to me

  17. tylerkaraszewski commented on Jan 22, 2024

    @tylerkaraszewski
    Contributor

    I think that's fine.

  18. parasharrajat commented on May 13, 2024

    @parasharrajat
    Member

    Payment requested as per #33423 (comment)

  19. JmillsExpensify commented on May 19, 2024

    @JmillsExpensify
    Contributor

    $500 approved for @parasharrajat

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 productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions