-
Notifications
You must be signed in to change notification settings - Fork 3k
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 2023-10-09] [$500] Profile - Save button is disabled in Display name page in offline mode #28148
Comments
Triggered auto assignment to @tjferriss ( |
Bug0 Triage Checklist (Main S/O)
|
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Auto-assign attempt failed, all eligible assignees are OOO. |
ProposalPlease re-state the problem that we are trying to solve in this issue.The Save button is disabled in Display name page in offline mode What is the root cause of that problem?In the FormProvider component, the App/src/components/Form/FormProvider.js Lines 237 to 244 in 21b3e64
What changes do you think we should make in order to solve the problem?Forward the <FormWrapper
{...rest}
+ enabledWhenOffline={enabledWhenOffline}
onSubmit={submit}
inputRefs={inputRefs}
errors={errors}
> What alternative solutions did you explore? (Optional)None. |
Job added to Upwork: https://www.upwork.com/jobs/~0134557e3ac359277d |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat ( |
Reviewin |
I'm able to reproduce this one, though I'm not sure if this qualifies as a deploy blocker. |
Triggered auto assignment to @marcochavezf, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
My bad, I forgot to tag the original PR author for the regression. @thesahindia @kowczarz looks like a regression from #27025 |
@parasharrajat Yes, I'm currently available. Do I wait to be assigned or should I just create the PR? |
Actually, there are a couple of bugs with the main PR that caused this regression so I think we should wait for the author to reply. |
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. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.74-3 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 2023-10-05. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Payment Summary:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.75-12 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 2023-10-09. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@parasharrajat can you get started on the checklist? |
To clarify, payment is expected on 2023-10-09 as long as we don't see any regressions. |
This was originally deployed to production on 2023-09-28, so the payment date of 2023-10-05 is the correct one. Looks like it got mixed up in the deployment process a second time so the bot got confused. |
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@akinwale has been paid via Upworks. We're waiting on @parasharrajat to be paid, then we can close the issue. |
Received. Thanks! |
Payment requested as per #28148 (comment) |
$750 payment approved for @parasharrajat based on BZ summary. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Issue found when executing PR #27025
Action Performed:
Expected Result:
User is able to save the changes in offline mode
Actual Result:
Save button is disabled and user cannot make changes during offline
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.74-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Bug6213691_Screen_Recording_20230925_211750_New_Expensify.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: