-
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-23] [HOLD for payment 2023-10-23] [HOLD for payment 2023-10-20] [HOLD for payment 2023-10-20] [$500] The "Hmm... it's not here" message does not appear when opening the assignee modal of a canceled task using the URL #28026
Comments
ProposalPlease re-state the problem that we are trying to solve in this issue.The "Hmm... it's not here" message does not appear when opening the assignee modal of a canceled task using the URL What is the root cause of that problem?The root cause is when a task is deleted, the App/src/pages/tasks/TaskAssigneeSelectorModal.js Lines 201 to 203 in 4969433
isOpenTaskReport Lines 220 to 222 in 4969433
isOpenTaskReport use isCanceledTaskReport which failed in task.report Lines 201 to 211 in 4969433
What changes do you think we should make in order to solve the problem?We need to use we can also use it in // we use the same page for both new task asignee and edit it,
// so we need to check it because in new task report will be null
// we can also use Boolean(report)
const isOpen = report && ReportUtils.isOpenTaskReport(report); The What alternative solutions did you explore? (Optional)N/A |
Job added to Upwork: https://www.upwork.com/jobs/~0181644eb19fd0aac9 |
Triggered auto assignment to @sophiepintoraetz ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to @miljakljajic ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @robertKozik ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.The "Hmm... it's not here" message does not appear when opening the assignee modal of a canceled task using the URL What is the root cause of that problem?We only update App/src/components/ReportActionItem/TaskView.js Lines 45 to 47 in 71db96d
So this check here is wrong
What changes do you think we should make in order to solve the problem?In
Let's imagine this case when we open the task report which is not canceled and then we open the assignee modal of the canceled task, What alternative solutions did you explore? (Optional)We can still display |
@sophiepintoraetz do we both need to be assigned to this? If not, feel free to unassign yourself. |
@miljakljajic - no, we don't 😂 I can take this seeing as I was assigned first (thank you for replicating, as an FYI, if Applause has applied the |
Oh brilliant I had no idea, thank you! |
Appreciate you grabbing it also <3 |
Waiting for @robertKozik to review the proposals! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Still waiting on @robertKozik here! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.83-11 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-20. 🎊 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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.83-11 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-20. 🎊 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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 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-23. 🎊 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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 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-23. 🎊 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:
|
@ahmedGaber93, @sophiepintoraetz, @srikarparsi, @robertKozik Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Summary of payments:
Eligible for urgency bonus? Y |
@robertKozik - can you complete the b0 checklist please? |
@sophiepintoraetz offer accepted, Thank you |
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:
Upon opening the assignee page of the canceled task using the URL, the "Hmm... it's not here" message should be displayed for the assignee
Actual Result:
The "Hmm... it's not here" message does not appear when opening the assignee modal of a canceled task using the URL
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: 1.3.73-0
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
bandicam.2023-09-22.16-41-37-895.mp4
screen-recording-2023-09-18-at-92636-pm_GqYXLtcn.1.mp4
Expensify/Expensify Issue URL:
Issue reported by: @ayazhussain79
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695054791232689
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: