Skip to content

[HOLD for payment 2023-06-28] [$1000] Inconsistent behavior when copying mentions with different methods #20814

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. Post a comment with text and a mention
  2. Select the posted comment and press CTRL + C to copy it
  3. Paste the copied content elsewhere
  4. Hover over the posted comment on step 1 and click on copy to clipboard icon
  5. Paste the content elsewhere
  6. Post a mention comment only and select the posted comment and use ctrl + c to copy the content
  7. Compare the contents copied with the above different copy methods

Expected Result:

All copy methods should result in the same copied content

Actual Result:

When copying a posted comment which has a text and a mention using selection and ctrl + c copy method the content being copied is different from the other methods. The copied content appends this ""

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.3.28-3
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

2023-06-15.11.43.07.mp4
Recording.976.mp4

Expensify/Expensify Issue URL:
Issue reported by: @Nathan-Mulugeta
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1686818464264869

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~014a3e659d43c036c7
  • Upwork Job ID: 1669428313148706816
  • Last Price Increase: 2023-06-15

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 15, 2023
  2. melvin-bot commented on Jun 15, 2023

    @melvin-bot

    Triggered auto assignment to @isabelastisser (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. melvin-bot commented on Jun 15, 2023

    @melvin-bot

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  4. OSBotify commented on Jun 15, 2023

    @OSBotify
    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. melvin-bot commented on Jun 15, 2023

    @melvin-bot

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

  6. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Jun 15, 2023
  7. 31 remaining items

  8. melvin-bot commented on Jun 23, 2023

    @melvin-bot
  9. Julesssss commented on Jun 26, 2023

    @Julesssss
    Contributor

    Not overdue. We're waiting on payment

  10. Julesssss commented on Jun 30, 2023

    @Julesssss
    Contributor

    @michaelhaxhiu ready for payment

  11. michaelhaxhiu commented on Jun 30, 2023

    @michaelhaxhiu
    Contributor

    So, the payment owed is just the bug reporting bonus it seems? (for @Nathan-Mulugeta)

  12. michaelhaxhiu commented on Jun 30, 2023

    @michaelhaxhiu
    Contributor

    Invited Nathan to accept the job offer for bug reporting bonus.

  13. Nathan-Mulugeta commented on Jun 30, 2023

    @Nathan-Mulugeta

    Just accepted the offer @michaelhaxhiu

  14. michaelhaxhiu commented on Jun 30, 2023

    @michaelhaxhiu
    Contributor

    paid.

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 productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions