-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[Due for payment 2025-03-24] [Report Creation UI] Create Alias for CreateReport - CreateAppReport #57651
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
Comments
Triggered auto assignment to @alexpensify ( |
Hi, I'm Kuba from SWM and I can do this one. |
Web PR is on staging now, @sumo-slonik. How are you getting on with the draft of the App PR? |
Since this seems strictly tied to my task #57653 and Kuba is busy with another task from Report creation flow, then I will take it and do it along with the linked issue. I will put out the draft ASAP, probably tomorrow. |
Sounds good, done! |
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. |
It looks like @mountiny has a plan here. |
We are moving along, backend should be ready with the report preview action too on monday in staging |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.13-5 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-03-24. 🎊 For reference, here are some details about the assignees on 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:
|
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO. |
@mountiny we don't need to handle payments here, right? If so, let's close it out! |
No payments need to be handled |
Uh oh!
There was an error while loading. Please reload this page.
Implement this section of the design doc
@SzymczakJ @sumo-slonik
Issue Owner
Current Issue Owner: @trjExpensifyThe text was updated successfully, but these errors were encountered: