Skip to content

[$500] Workspace - The middle message flows out of the container when the email is longer #9287

Closed

Description

@kavimuru

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


Action Performed:

  1. Create a new workspace from an account that's on the policyExpenseChat beta (e.g @expensifail.com)
  2. Add a new member with a big email to the workspace via Manage Members > Invite
  3. Log-in as the member and send a message in the member's workspace chat
  4. Log back in again to the admin account and remove the member from the workspace via Manage Members > Remove
  5. Now log-in as the member again and navigate to the workspace chat

Expected Result:

Verify the all messages (footer and middle) doesn't go out of the container and you can see the whole message.

Actual Result:

The middle message flows out of the container when the email is long.

Workaround:

visual

Platform:

Where is this issue occurring?

  • Android
  • Mobile Web

Version Number: 1.1.70-2
Reproducible in staging?: y
Reproducible in production?: y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Bug5593655_Screenshot_20220601-163231_New_Expensify

Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:

View all open jobs on GitHub

Activity

  1. melvin-bot commented on Jun 2, 2022

    @melvin-bot

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

  2. changed the title [-]Workspace- The message flows out of the container when the email is longer[/-] [+]Workspace- The middlemessage flows out of the container when the email is longer[/+] on Jun 2, 2022
  3. changed the title [-]Workspace- The middlemessage flows out of the container when the email is longer[/-] [+]Workspace- The middle message flows out of the container when the email is longer[/+] on Jun 2, 2022
  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jun 2, 2022
  5. melvin-bot commented on Jun 2, 2022

    @melvin-bot

    Triggered auto assignment to @jliexpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

  6. removed their assignment
    on Jun 2, 2022
  7. changed the title [-]Workspace- The middle message flows out of the container when the email is longer[/-] [+]Workspace - The middle message flows out of the container when the email is longer[/+] on Jun 2, 2022
  8. 35 remaining items

  9. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jun 28, 2022
  10. melvin-bot commented on Jun 28, 2022

    @melvin-bot

    📣 @allroundexperts You have been assigned to this job by @kadiealexander!
    Please apply to this job in Upwork and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
    Keep in mind: Code of Conduct | Contributing 📖

  11. removed their assignment
    on Jun 28, 2022
  12. allroundexperts commented on Jun 28, 2022

    @allroundexperts
    Contributor

    @jliexpensify Applied on upwork!

  13. mvtglobally commented on Jul 5, 2022

    @mvtglobally

    Issue not reproducible during KI retests. (First week)

  14. rushatgabhane commented on Jul 5, 2022

    @rushatgabhane
    Member

    Issue not reproducible during KI retests

    Interesting.. we don't have a PR yet. cc: @allroundexperts

  15. allroundexperts commented on Jul 5, 2022

    @allroundexperts
    Contributor

    @rushatgabhane That's true.

  16. mvtglobally commented on Jul 12, 2022

    @mvtglobally

    Issue not reproducible during KI retests. (Second week). Not sure if we are missing any step.
    @rushatgabhane are you able to repro?

  17. rushatgabhane commented on Jul 12, 2022

    @rushatgabhane
    Member

    @mvtglobally issue not reproducible.

  18. rushatgabhane commented on Jul 12, 2022

    @rushatgabhane
    Member

    @jliexpensify I'm curious if a C+ is compensated when a proposal is approved, but the issue is fixed by another PR.

  19. jliexpensify commented on Jul 12, 2022

    @jliexpensify
    Contributor

    @rushatgabhane let me take this one to the team and I'll get back to you with an answer!

  20. jliexpensify commented on Jul 14, 2022

    @jliexpensify
    Contributor

    @allroundexperts and @rushatgabhane - good news for you both!

    The consensus is that we'll pay you both, even though the issue was solved by another PR - since you both did the work: here is a similar example that was discussed.

  21. rushatgabhane commented on Jul 14, 2022

    @rushatgabhane
    Member

    @jliexpensify appreciate it, thank you! 😊

  22. jliexpensify commented on Jul 14, 2022

    @jliexpensify
    Contributor

    Paid both, closing!

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 contributorWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions