-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2024-02-20] [$500] Task – User with the custom name is shown as Hidden in task assignee field #36341
Comments
👋 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:
|
Triggered auto assignment to @bondydaa ( |
We think that this bug might be related to #vip-vsp |
#35027 was deployed to production last week but this is deploy blocker |
🎉 tested that and 👍 seems to work @fedirjh can you get a PR up? will assign now |
Triggered auto assignment to @anmurali ( |
@anmurali nothing for you to do right now, just assigning bug for a BZ to handle payments when the time comes. |
Job added to Upwork: https://www.upwork.com/jobs/~0177663dcf0666e903 |
This was tested! NAB! |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.40-5 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-02-20. 🎊 For reference, here are some details about the assignees on this issue: |
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:
|
@bondydaa Issue is not reproducible on the latest build 1.4.41-4 Screenrecorder-2024-02-14-22-37-37-928.mp4 |
great thanks! |
Payment not due for another 4 days. Rotated the label since I will be OOO till 29th! |
Triggered auto assignment to @abekkala ( |
PAYMENT SUMMARY FOR FEB 20
|
Payment SummaryBugZero Checklist (@abekkala)
|
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.40-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?/tests/view/4301190
Email or phone of affected tester (no customers): [email protected]
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Expected Result:
The assignee with the custom name is displayed in the assignee field
Actual Result:
User with the custom name is shown as Hidden in task assignee field
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6376640_1707748629323.User_with_the_name_is_shown_as_Hidden_in_task_assignee.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @abekkalaThe text was updated successfully, but these errors were encountered: