-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[HOLD for payment 2023-10-16] [$500] Assign Task - Assignee field active in offline mode while assigning task, should be greyed out #25956
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
ProposalPlease re-state the problem that we are trying to solve in this issue.Assignee field active in offline mode while assigning task, should be greyed out What is the root cause of that problem?We don't set pendingField when editing assignee Line 511 in c435734
What changes do you think we should make in order to solve the problem?In optimistic report data Lines 526 to 531 in c435734
we should add pending field managerID: update like this
We also need to remove pendingFields when updating successful What alternative solutions did you explore? (Optional) |
ProposalPlease re-state the problem we are trying to solveThe task assignee field is doesn't get greyed out when changed offline. What is the root cause of this problem?This was introduced in this PR: #22778 Lines 525 to 534 in a03a21d
Therefore, the pending field for What changes do you think we should make in order to solve the problem?
{
onyxMethod: Onyx.METHOD.MERGE,
key: `${ONYXKEYS.COLLECTION.REPORT}${report.reportID}`,
value: {
reportName,
managerID: assigneeAccountID || report.managerID,
managerEmail: assigneeEmail || report.managerEmail,
pendingFields: {managerID: CONST.RED_BRICK_ROAD_PENDING_ACTION.UPDATE}, // add this line
},
},
{
onyxMethod: Onyx.METHOD.MERGE,
key: `${ONYXKEYS.COLLECTION.REPORT}${report.reportID}`,
value: {pendingFields: {managerID: null}}
} This is the same approach we follow |
Triggered auto assignment to @michaelhaxhiu ( |
Bug0 Triage Checklist (Main S/O)
|
@michaelhaxhiu Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@allroundexperts - do you think this bug report & problem is a dupe of #23200? Would love your input! |
Yep this feels and looks like a dupe, and the other GH is addressing it. Closing. |
@michaelhaxhiu This bug #23200 PR merged but #25956 is still reproducible @allroundexperts can you please also check this one |
Hmm let's see what's suggested on #23200 from those involved. You may be due a bug reporting bounty if this is indeed "separate" and thus unique. |
But firstly I want to ensure this is fixed. If it's not fixed, there is no bug bounty to pay. That's the pre-requisite. |
Commented here for team input on how to best proceed. This is a valid bug and still occurring based on latest testing, so we do need to fix it. But I want to check if we should draft a new PR or amend/update the PR that caused it. |
Job added to Upwork: https://www.upwork.com/jobs/~01cb180f9f96ed4319 |
Current assignee @michaelhaxhiu is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @abdulrahuman5196 ( |
cc'ing |
this is a regression from #22778 |
might make sense for @abdulrahuman5196 to trade this GH to @Santhosh-Sellavel since he was involved in the parent regression, though it's not necessary. I'll let yall decide. |
Pending on @tylerkaraszewski review. |
@abdulrahuman5196 The PR is ready for review: #28378 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.79-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 2023-10-16. 🎊 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:
|
PAYMENTS FOR OCT 16
|
@abekkala Could you help to check the timeline bonus again? The PR is merged in 3 days |
Yes. PR was merged within 3 days. Melvin missed here. |
@DylanDylann and @abdulrahuman5196 ah, yes - I do see that Melvin missed this one. @abdulrahuman5196 please complete checklist prior to payment |
https://github.com/Expensify/App/pull/22778/files
https://github.com/Expensify/App/pull/22778/files#r1361115083
Yes.
|
@ayazhussain79 paid and contract ended - thank you! 🎉 @DylanDylann paid and contract ended - thank you! 🎉 @abdulrahuman5196 paid and contract ended - thank you! 🎉 |
Uh oh!
There was an error while loading. Please reload this page.
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
During offline mode, the assignee field should appear greyed out to indicate its inactivity while assigning a task
Actual Result:
The assignee field remains active and doesn't turn grey while assigning a task in offline mode
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.57-4
Reproducible in staging?: Yes
Reproducible in production?: Yes
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
screen-recording-2023-08-12-at-31853-am_RnxP47TY.1.mp4
Gravar.2977.mp4
Expensify/Expensify Issue URL:
Issue reported by: @ayazhussain79
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1691792826667939
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: