Skip to content

[HOLD for payment 2024-06-03] [$250] Start chat - No Recent section in Start chat list #42189

Closed

Description

@lanitochka17

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: 1.4.74-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/cases/view/1971079
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Log in with a new account (so that there is no recent list in Sart chat)
  3. Open DM with any user
  4. Send a message
  5. Go to FAB
  6. Go to Start chat

Expected Result:

User in Step 3 will appear under Recent section in Start chat list

Actual Result:

There is no Recent section in Start chat list

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

Bug6481504_1715771311261.recent_list.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0124d68db208e5d895
  • Upwork Job ID: 1790830447129296896
  • Last Price Increase: 2024-05-15
Issue OwnerCurrent Issue Owner: @jayeshmangwani

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on May 15, 2024
  2. melvin-bot commented on May 15, 2024

    @melvin-bot

    Triggered auto assignment to @dangrous (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  3. melvin-bot commented on May 15, 2024

    @melvin-bot

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open Staging deploy checklist to see the list of PRs included in this release, then work quickly on the following:

    1. If you find which PR caused the issue/bug, you can reassign it to the person responsible for it.
      • If the author is OOO or won’t get online before the daily deploy is due, you are responsible for finding the best fix/path forward. Don’t hesitate to ask for help!
    2. Try to reproduce the issue, if the bug is on production, remove the DeployBlocker label but stay assigned to fix it (or find out which PR broke it to get help from the author).
      • You can adjust the urgency of the issue to better represent the gravity of the bug.
      • If the issue is super low priority, feel free to un-assign yourself.
      • Be careful with PHP warnings, sometimes it is more complex than just adding a null coalescing operator as they might be uncovering some bigger bug.
      • If it was a one-off issue that requires no action (for example, Bedrock was down or it is a duplicated issue), you can close it.

    Remember rule #2: Never un-assign yourself from a real DeployBlocker unless you are 100% sure someone else is assigned and will take care of it.

  4. github-actions commented on May 15, 2024

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  5. lanitochka17 commented on May 15, 2024

    @lanitochka17
    Author

    @dangrous FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

  6. dangrous commented on May 15, 2024

    @dangrous
    Contributor

    Yeah seems like a bug unless there was a design change that I'm not aware of (which is possible). I'll make this external but also investigate!

  7. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on May 15, 2024
  8. changed the title [-]Start chat - No Recent section in Start chat list[/-] [+][$250] Start chat - No Recent section in Start chat list[/+] on May 15, 2024
  9. melvin-bot commented on May 15, 2024

    @melvin-bot
  10. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on May 15, 2024
  11. 14 remaining items

  12. changed the title [-][$250] Start chat - No Recent section in Start chat list[/-] [+][HOLD for payment 2024-06-03] [$250] Start chat - No Recent section in Start chat list[/+] on May 27, 2024
  13. melvin-bot commented on May 27, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.75-1 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 2024-06-03. 🎊

    For reference, here are some details about the assignees on this issue:

  14. jayeshmangwani commented on Jun 3, 2024

    @jayeshmangwani
    Contributor

    @dangrous We are good close this Issue, It was a regression from a PR, no payments for this issue

  15. melvin-bot commented on Jun 3, 2024

    @melvin-bot

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

  16. melvin-bot commented on Jun 3, 2024

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@abekkala)

    • I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1790830447129296896/hired)
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  17. abekkala commented on Jun 3, 2024

    @abekkala
    Contributor

    Not sure why Melvin Bot assigned me to process payment

    @dangrous We are good close this Issue, It was a regression from a PR, no payments for this issue

  18. dangrous commented on Jun 4, 2024

    @dangrous
    Contributor

    Yeah I think it just is automatic. Will close!

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 productionDailyKSv2EngineeringExternalAdded 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