[HOLD for payment 2024-03-29] [$500] [Simplified Collect][Distance Rates] Implement PolicyDistanceRateSettingsPage

[luacmartins]

Implement PolicyDistanceRateSettingsPage following the specifications in the design doc

cc @MrMuzyk

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~010902f2b08cb0564b
• Upwork Job ID: 1763223051466571776
• Last Price Increase: 2024-02-29

[melvin-bot]

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

[MrMuzyk]

I am Michał from Callstack - expert contributor group. I’d like to work on this job.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~010902f2b08cb0564b

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @ishpaul777 (External)

[melvin-bot]

Current assignee @sakluger is eligible for the NewFeature assigner, not assigning anyone new.

[hereistopdev]

I am a freelancer from Upwork, I would like to work on this issue

[hereistopdev]

I am ready to start work right now

[luacmartins]

@hereistopdev thanks for the interest. However, we already assigned someone to work on this issue.

[hereistopdev]

ok
You are welcome

[ishpaul777]

not overdue

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[parasharrajat]

Are we going to create a follow-up PR?

[luacmartins]

@parasharrajat to fix #38662? I think @MrMuzyk is assigned and will work on a fix.

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.55-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• feat: policy distance rates settings #38060

If no regressions arise, payment will be issued on 2024-03-29. 🎊

For reference, here are some details about the assignees on this issue:

• @MrMuzyk does not require payment (Contractor)
• @ishpaul777 requires payment (Needs manual offer from BZ)

[melvin-bot]

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@ishpaul777] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
• [@sakluger] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

[luacmartins]

Just pending payment

[parasharrajat]

Looks like there is no pending payment here.

[ishpaul777]

I haven't been paid yet @parasharrajat, looks like the follow up is handled as a different issue i never got assigned to that issue 🤔

[sakluger]

Sorry for the delay, I'll handle payment now. Just to confirm, there was a regression on this issue's PR, correct? So the payment would be $250?

[ishpaul777]

@sakluger @luacmartins will that issue be counted as regression, there's a few polish things left with new feature PR do we count it as regression never happened to me on any previous issue so just asking..

[luacmartins]

I don't think that was a regression since the feature didn't exist yet. I think the full l$500 still applies in this case.

[sakluger]

Got it, thanks for confirming!

@ishpaul777 I've sent you an offer via Upwork: https://www.upwork.com/nx/wm/offer/101802947

[ishpaul777]

Accepted! Thanks 😄

[sakluger]

Awesome, thanks! 🙌