Skip to content

Profile - GMT time is not displayed #2097

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!


Expected Result:

GMT time is displayed as GMT -3

Actual Result:

"GMT" is not displayed, only the time and "-03" is visible.

Action Performed:

  1. Log in as account A
  2. Set the time zone of the account to America/Sao_Paulo
  3. Log out of account A
  4. Log in as another account and check account A's profile.

Attachments/Notes

Found while executing https://github.com//pull/1717

Device and OS: Huawei P20 Pro / 10.0

Is the issue reproducible in Prod: Yes

Build version: 1.0.6-1

Activity

  1. changed the title [-][Chat] - 1.0.6-0 - Profile - GMT time is not displayed[/-] [+]Profile - GMT time is not displayed[/+] on Mar 26, 2021
  2. kaushiktd commented on Mar 26, 2021

    @kaushiktd
    Contributor

    Hi,

    This is Kaushik here and this is my technical explanation for this issue.

    1. This is a time format issue it will be managed by moment js.
  3. added
    AutoAssignerTriageAuto assign issues for triage to an available triage team member
    on Mar 31, 2021
  4. MelvinBot commented on Mar 31, 2021

    @MelvinBot
    Contributor

    Triggered auto assignment to @muttmuure (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

  5. removed
    AutoAssignerTriageAuto assign issues for triage to an available triage team member
    on Mar 31, 2021
  6. MelvinBot commented on Apr 7, 2021

    @MelvinBot
    Contributor

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

  7. muttmuure commented on Apr 7, 2021

    @muttmuure
    Contributor

    I think I missed this because it's in the .cash repo.

    @stitesExpensify when you're happy with the review we'll need to create an External issue in E/E https://expensify.slack.com/archives/C01SKUP7QR0/p1617220984062300?thread_ts=1617218921.052600&cid=C01SKUP7QR0

  8. 31 remaining items

  9. kaushiktd commented on May 14, 2021

    @kaushiktd
    Contributor

    @stitesExpensify No prob. I managed to do it from Windows system. Did you get a chance to check it out?

  10. stitesExpensify commented on May 14, 2021

    @stitesExpensify
    Contributor

    @kaushiktd Yes I did, if you could take a look at my comment and update your PR description to match the template that would be great

  11. isagoico commented on May 17, 2021

    @isagoico
    Author

    Issue reproducible during today's KI retests

  12. isagoico commented on May 24, 2021

    @isagoico
    Author

    Issue reproducible during today's KI retests

  13. kaushiktd commented on May 24, 2021

    @kaushiktd
    Contributor

    @isagoico I just run the entire code in my system again and it not showing any issue. Can you please show me a video of it or a path to recreate this issue?

  14. Christinadobrzyn commented on May 24, 2021

    @Christinadobrzyn
    Contributor

    @stitesExpensify can you give an update on where we are with the final PR for this?

  15. stitesExpensify commented on May 24, 2021

    @stitesExpensify
    Contributor

    It looks like there are 2 very similar PRs
    https://github.com/Expensify/Expensify.cash/pull/2957/files
    https://github.com/Expensify/Expensify.cash/pull/2756/files

    @kaushiktd can you choose one and close the other one?

    I just run the entire code in my system again and it not showing any issue.

    Isabella is testing on production. Since your code has not been merged, the issue will continue to be reproducible 👍

  16. kaushiktd commented on May 25, 2021

    @kaushiktd
    Contributor

    https://github.com/Expensify/Expensify.cash/pull/2957/files

    This is the only one open now. I have closed another one. @isagoico Can you please check this again?

  17. stitesExpensify commented on May 25, 2021

    @stitesExpensify
    Contributor

    Isabella won't be able to check it because no PR has been merged yet 😄

    Basically the process is:

    1. Someone (Isabella in this case) finds a bug and makes an issue
    2. You write a PR that works for you locally
    3. Someone from Expensify reviews and tests your code locally once there are no merge conflicts
    4. That person will merge your PR
    5. Isabella can re-test and see if the issue is still occuring
  18. stitesExpensify commented on May 25, 2021

    @stitesExpensify
    Contributor

    @kaushiktd I made a change request on the new PR. Let me know when it's good to go and i'll look at it right away

  19. Christinadobrzyn commented on May 27, 2021

    @Christinadobrzyn
    Contributor

    @kaushiktd is paid in Upwork, the contract has been completed, and the Upwork post has been closed

  20. Christinadobrzyn commented on May 27, 2021

    @Christinadobrzyn
    Contributor

    Ah, I accidentally paid this PR too early, it should have been paid 7 days after the correct PR was merged. I'm also going to be ooo next week so I assigned Kadie to this issue.

    If needed, please reopen so @kaushiktd can fix any issues with the PR.

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

Metadata

Metadata

Labels

EngineeringExternalAdded to denote the issue can be worked on by a contributorMonthlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions