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
Move odometer image stitching to confirmation page #84998
PR is ready for review but includes solutions for other issues. Now I am working on splitting them up thematically to separate PRs (most likely they will be stacked upon each other since both backup transaction and blob URL loss detection changes are based on the stitching logic thats being moved to the confirmation page)
changed the title [-]Move odometer image stitching to confirmation page[/-][+][Due for payment 2026-04-02] Move odometer image stitching to confirmation page[/+]on Mar 26, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.48-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
changed the title [-][Due for payment 2026-04-02] Move odometer image stitching to confirmation page[/-][+]Move odometer image stitching to confirmation page[/+]on Apr 3, 2026
Activity
melvin-bot commentedon Mar 16, 2026
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.
melvin-bot commentedon Mar 16, 2026
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.
jakubkalinski0 commentedon Mar 20, 2026
PR is ready for review but includes solutions for other issues. Now I am working on splitting them up thematically to separate PRs (most likely they will be stacked upon each other since both backup transaction and blob URL loss detection changes are based on the stitching logic thats being moved to the confirmation page)
jakubkalinski0 commentedon Mar 21, 2026
@DylanDylann I will finish splitting this up when I wake up
jakubkalinski0 commentedon Mar 23, 2026
The PR #85105 was split into the following PRs to make testing easier:
6 remaining items
[-]Move odometer image stitching to confirmation page[/-][+][Due for payment 2026-04-02] Move odometer image stitching to confirmation page[/+]melvin-bot commentedon Mar 26, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Mar 26, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.48-2 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 2026-04-02. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Mar 26, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)DylanDylann commentedon Apr 2, 2026
No required payment
melvin-bot commentedon Apr 2, 2026
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
DylanDylann commentedon Apr 3, 2026
@Julesssss Could you close this issue?
[-][Due for payment 2026-04-02] Move odometer image stitching to confirmation page[/-][+]Move odometer image stitching to confirmation page[/+]