-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[HOLD for payment 2024-07-22] [HOLD for payment 2024-07-17] [Report Fields] [External] Implement the policy report fields creation flow #43684
Comments
Current assignees @rushatgabhane and @shubham1206agra are eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to @sakluger ( |
Hello, Im Artem from Callstack and would like to help with this issue |
Hi, I’m Michael (Mykhailo) from Callstack and I would like to work on this issue. |
Actively working on the issue. |
Actively working on the issue. I've opened a draft PR. Progress
WIP.mp4 |
Updates:
|
Updates:
|
Updates:
|
Updates:
|
Updates:
|
I've opened the PR (#44275) for review. |
I believe the PR was merged so we are done here |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.5-13 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 2024-07-17. 🎊 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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.6-8 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 2024-07-22. 🎊 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:
|
[Main tracking issue].(https://github.com/Expensify/Expensify/issues/365155)
Design doc link.
Implement the following section of the design doc:
https://docs.google.com/document/d/10b7pTVvgpB6_O8sRTKaCzZEVM3Ba6hxnIwyyQSSXCLY/edit#bookmark=kix.3s2yd5r621zv
This might technically be on hold for #43677 but I think Callstack can start on these in parallel using feature branch.
Include unit tests for the optimistic actions
Issue Owner
Current Issue Owner: @Issue Owner
Current Issue Owner: @saklugerThe text was updated successfully, but these errors were encountered: