-
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
[$1000] Not able to add a task assignee #20807
Comments
Triggered auto assignment to @conorpendergrast ( |
Bug0 Triage Checklist (Main S/O)
|
Hi I'm Ana from Callstack - expert contributor group - I can work on this issue. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Not able to add a task assignee What is the root cause of that problem?We have changed field in recent PR, Line 474 in 961d93c
Line 496 in 961d93c
But we are not using updated field here App/src/pages/tasks/NewTaskPage.js Line 81 in 4fdc8db
What changes do you think we should make in order to solve the problem?We should change field name here to this assigneeAccountID: newAssigneeAccountID What alternative solutions did you explore? (Optional) |
Job added to Upwork: https://www.upwork.com/jobs/~01e2aaeba9308a0daa |
Current assignee @conorpendergrast is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak ( |
Triggered auto assignment to @madmax330 ( |
@eVoloshchak please review the proposal above when you have time! |
I'm getting this fixed in my PR here #20808. |
Unassigning @eVoloshchak based on this being fixed in this PR, please correct me if that's wrong. I'll hire @gadhiyamanan as bug reporter... when Upwork comes back |
Contract sent to @gadhiyamanan via Upwork for bug bounty. I'll pay that when this is fixed by #20808 @youssef-lr I think you need to add this issue (#20807) to the fixed issues sections in that PR, right? |
Ok, looks like the fix for this is on Staging now #20808 I'll re-test now on Staging |
Tested on v1.3.29-1, and no issue with adding the task assignee 👍 |
Once that PR reaches production, I'll get that bug bounty paid and will close this issue |
Not overdue. |
This is on Production: #20808 Time to pay! |
Paid out @gadhiyamanan, ended contract. Closing! |
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:
user should be assign as Assignee
Actual Result:
not able to assign any Assignee
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number:
main
Reproducible in staging?:
Reproducible in production?:
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
Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1686829718168319
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: