You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2023-07-17] [$1000] Remove usage of getReportIDFromRoute #22326
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.38-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-07-17. 🎊
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
External issue reporter
Contributor that fixed the issue
Contributor+ that helped on the issue and/or PR
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
Just some forgotten usage. I don't think we need this
[@Gonals] The PR that introduced the bug has been identified. Link to the PR:
[@Gonals] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[@Gonals] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[@Gonals] Determine if we should create a regression test for this bug.
[@Gonals] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[@flaviadefaria] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
Activity
melvin-bot commentedon Jul 6, 2023
Triggered auto assignment to @mallenexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Jul 6, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)[-]Remove usage of getReportIDFromRoute[/-][+][$1000] Remove usage of getReportIDFromRoute[/+]melvin-bot commentedon Jul 6, 2023
Job added to Upwork: https://www.upwork.com/jobs/~014254ae0a9d055feb
18 remaining items
melvin-bot commentedon Jul 10, 2023
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jul 10, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.38-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-07-17. 🎊
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
melvin-bot commentedon Jul 10, 2023
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
Just some forgotten usage. I don't think we need this
flaviadefaria commentedon Jul 18, 2023
@Gonals what is required from me here? Does anyone need to be paid or can I unassign myself. Sorry, but I'm a bit confused!
Gonals commentedon Jul 19, 2023
I think you are all good!
melvin-bot commentedon Jul 24, 2023
@Gonals Eep! 4 days overdue now. Issues have feelings too...
melvin-bot commentedon Jul 26, 2023
@Gonals Still overdue 6 days?! Let's take care of this!
melvin-bot commentedon Jul 28, 2023
@Gonals 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!
Gonals commentedon Jul 31, 2023
I think we can close this