Skip to content
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

Issue to pay Slack reported bug that got fixed internally before new GH was created. #9363

Closed
mallenexpensify opened this issue Jun 8, 2022 · 7 comments
Assignees
Labels
Daily KSv2

Comments

@mallenexpensify
Copy link
Contributor

From this Slack thread https://expensify.slack.com/archives/C01GTK53T8Q/p1653886712901589

@sobitneupane reported a bug that Applause reported after that ended up getting fixed internally so Sobit is owed $250 for reporting.

@mallenexpensify mallenexpensify added AutoAssignerTriage Auto assign issues for triage to an available triage team member Daily KSv2 labels Jun 8, 2022
@mallenexpensify mallenexpensify self-assigned this Jun 8, 2022
@melvin-bot
Copy link

melvin-bot bot commented Jun 8, 2022

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

@melvin-bot melvin-bot bot removed the AutoAssignerTriage Auto assign issues for triage to an available triage team member label Jun 8, 2022
@mallenexpensify
Copy link
Contributor Author

@sobitneupane hired you, can you accept then I'll pay $250 for reporting the issue? https://www.upwork.com/jobs/~01a76a5fbc7fcb7a60

Sorry @strepanier03 , I should have assigned myself before you were auto-assigned triage, no action needed from you

@sobitneupane
Copy link
Contributor

@sobitneupane hired you, can you accept then I'll pay $250 for reporting the issue? https://www.upwork.com/jobs/~01a76a5fbc7fcb7a60

Accepted.

@Puneet-here
Copy link
Contributor

@mallenexpensify, I just wanted to know the policy here. Do expensify pay for reporting a regression even if it hasn't hit the staging or production. Because I saw a comment earlier where it was stated that we don't and in this case the issue was reported before it was deployed to staging.

@mallenexpensify
Copy link
Contributor Author

Paid @sobitneupane $250. Leaving this open til the below is resolved.

hmm.... good question @Puneet-here , thanks for asking.

To make sure I understand correctly. From @sobitneupane 's bug report here the reported version is v1.1.68-2, are you saying that, on May 29th, when this was reported, that v1.1.68-2 wasn't a production release? Based on the issue QA reported (link), that's what it looks like
image

So.. if it's on staging, then we would compensate based on CONTRIBUTING.md here

The one piece I'm unsure on is the regression part, if the above doesn't answer you question can you rephrase and/or expand on the regression part?

@Puneet-here
Copy link
Contributor

So.. if it's on staging, then we would compensate based on CONTRIBUTING.md here

Thank for answering.

The one piece I'm unsure on is the regression part

Oh I was just asking if we also paying contributors for reporting regression before it hits the staging because this one was reported before getting to staging but I just found after few hours of reporting it was deployed to staging.

if the above doesn't answer you question can you rephrase and/or expand on the regression part?

it's good to be closed now. Thank you.

@melvin-bot melvin-bot bot added the Overdue label Jun 13, 2022
@mallenexpensify
Copy link
Contributor Author

Thanks again for raising @Puneet-here , I brought up internally for 👀, if there's an update we'll address in #expensify-open-source.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Daily KSv2
Projects
None yet
Development

No branches or pull requests

4 participants