Skip to content

Payout Prince Mendiratta for reporting Magic code bug #14731

Closed

Description

@Beamanator

Slack bug report: https://expensify.slack.com/archives/C049HHMV9SM/p1675264680096279

Led to my fix PR: #14730

Bug report reward due 👍

Activity

  1. self-assigned this
    on Feb 1, 2023
  2. locked and limited conversation to collaborators on Feb 1, 2023
  3. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 1, 2023
  4. unlocked this conversation on Feb 1, 2023
  5. melvin-bot commented on Feb 1, 2023

    @melvin-bot

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

  6. locked and limited conversation to collaborators on Feb 1, 2023
  7. unlocked this conversation on Feb 1, 2023
  8. melvin-bot commented on Feb 1, 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
  9. locked and limited conversation to collaborators on Feb 1, 2023
  10. Beamanator commented on Feb 1, 2023

    @Beamanator
    ContributorAuthor

    @tjferriss I filled out the checklist because this is a bug from my PR, and we fixed it already. But payment is still due to Prince (Idk their GH username) for reporting the bug

  11. removed their assignment
    on Feb 2, 2023
  12. unlocked this conversation on Feb 2, 2023
  13. tjferriss commented on Feb 2, 2023

    @tjferriss
    Contributor

    It might be obvious, but I'm asking for a clarification on how to process this payment in Slack as I've never paid out a one off bug report like this: https://expensify.slack.com/archives/C01SKUP7QR0/p1675365431742829

  14. tjferriss commented on Feb 2, 2023

    @tjferriss
    Contributor

    @Prince-Mendiratta I've created the job post here: https://www.upwork.com/jobs/~01a36f98b52369fc1e

    Can you please apply so that I can process the payment

  15. MelvinBot commented on Feb 6, 2023

    @MelvinBot
    Contributor

    @tjferriss Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  16. MelvinBot commented on Feb 6, 2023

    @MelvinBot
    Contributor

    @tjferriss Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  17. MelvinBot commented on Feb 6, 2023

    @MelvinBot
    Contributor

    @tjferriss Whoops! This issue is 2 days overdue. Let's get this updated quick!

  18. tjferriss commented on Feb 6, 2023

    @tjferriss
    Contributor

    Payment has been made in Upworks.

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

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions