-
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
[ON-HOLD Payment 4/16] [$500] Android/iOS - Chat - New chat shows time zone for Unvalidated Accounts #38581
Comments
Triggered auto assignment to @CortneyOfstad ( |
We think that this bug might be related to #vip-vsb |
@CortneyOfstad 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. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Android - Chat - New chat shows time zone. What is the root cause of that problem?We don't use Line 93 in 34fa987
We do have a check in ReportActionCompose .App/src/pages/home/report/ReportActionCompose/ReportActionCompose.tsx Lines 177 to 180 in 34fa987
What changes do you think we should make in order to solve the problem?Add a check for const currentUserPersonalDetails = useCurrentUserPersonalDetails();
const shouldShowLocalTime =
!ReportUtils.hasAutomatedExpensifyAccountIDs([accountID]) &&
!isEmptyObject(timezone) &&
ReportUtils.canShowReportRecipientLocalTime(personalDetails, report, currentUserPersonalDetails.accountID); We might also want to hide other fields like ResultAlternativelyShow local time above composer also. |
Don't think this is a bug actually |
📣 @hayes102! 📣
|
@kbecciv This is not a bug. We show timezones by default so people are aware of what time it is for the person they attempt to message. This is not personal information, and only provides a very broad location of where that person is at the moment the message is sent. Going to close this 👍 |
@CortneyOfstad, but why do we hide the local time above the composer than? Just want to confirm because we did intentionally hide the localtime above the composer. |
@Krishna2323 can you clarify what you mean by "the composer"? Sorry for the confusion on my part! |
@Krishna2323 I did some additional testing on this, and realized the "composer" refers to the text box — so all good there. However, I am surprised that we would hide that information, as it is not private by any means. I'm going to bring this to the room to discuss further and will follow up 👍 |
Post in #VIP-VSB is here |
We had a issue few weeks back which actually made all this data public, so maybe closing this bug is a choice, I will link the issue if i find it :) |
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
Job added to Upwork: https://www.upwork.com/jobs/~01ebbabe514d6a178d |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mollfpr ( |
Thanks for your patience! So after a deeper discussion with @puneetlath and @quinthar, we found that the scope of the issue is different that we originally thought. We're showing timezones for unvalidated accounts per this: I've adjusted the main comment above (just a heads up @kbecciv) and changed this to reflect that it also shows in iOS, as well as Android 👍 We would like to hide the timezone for unvalidated accounts to maintain consistency, as we do above the compose tool. @Krishna2323 feel free to adjust your proposal to reflect this (if needed) and we can get this reviewed. Thank you! |
I might have overlooked the issue of using @aldo-expensify We can go with @GandalfGwaihir's proposal for simplicity. |
@mollfpr I'm not sure why we can't use |
@Krishna2323 I don’t have any case in mind, but since the issue is on the profile detail page, it is not necessary to have a check for a report. |
@mollfpr @aldo-expensify, I was looking for a case where my solution fails and found it does fail on workspace members page. You can assign @GandalfGwaihir here. |
Thanks @Krishna2323 for checking, and sorry for the slow replies, I'm quite busy with other high priority stuff for the moment. I'll assign @GandalfGwaihir then. |
📣 @mollfpr 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @GandalfGwaihir 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
@GandalfGwaihir any update on the PR progress? Thanks! |
Would be up before EOD today, sorry for the delay... |
@mollfpr — PR is ready for your review — thanks! |
Launched to staging yesterday! |
Production 20 hours ago! |
Payment is set for tomorrow, so not overdue! |
No offending PR.
The regression step should be enough.
@CortneyOfstad Could you create the payment summary? Thank you! |
Payment Summary@GandalfGwaihir — paid $500 via Upwork |
Regression test created here — closing! |
$500 approved for @mollfpr |
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.54.0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4434326
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
New chat must not show time zone.
Actual Result:
User is not part of same private workspace/domain nor had sent a DM, yet time zone showing in details page for unvalidated accounts.
New chat shows time zone.
Workaround:
n/a
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6418748_1710821663189.hi.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: