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
[Due for payment 2025-04-17] [Simplified Actions] Implement getReportPreviewAction with tests #57440
changed the title [-][Simplified Actions] Implement getReportPreviewAction with tests[/-][+][Due for payment 2025-04-17] [Simplified Actions] Implement getReportPreviewAction with tests[/+]on Apr 10, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.25-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
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:
[@suneox] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
[@lschurr] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
melvin-bot commentedon Feb 26, 2025
Triggered auto assignment to @lschurr (
NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.jnowakow commentedon Feb 26, 2025
Hello, I'm from Software Mansion, an expert agency, and I'll work on this one
melvin-bot commentedon Mar 5, 2025
@jnowakow 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
31 remaining items
melvin-bot commentedon Apr 9, 2025
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 Apr 9, 2025
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.
luacmartins commentedon Apr 9, 2025
I'm closing this issue in favor of #59960. We'll handle payment via that one
[-][Simplified Actions] Implement getReportPreviewAction with tests[/-][+][Due for payment 2025-04-17] [Simplified Actions] Implement getReportPreviewAction with tests[/+]melvin-bot commentedon Apr 10, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.25-4 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 2025-04-17. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Apr 10, 2025
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: