Repository navigation
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.3.15-8
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-4454/55614645/1172745437?q=task&issue_type=jira
Email or phone of affected tester (no customers): sddhonisjsoijdsido@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Search
Action Performed:
- Go to staging.new.expensify.com
- Create a new Gmail account.
- Complete the onboarding with Track and budget expenses intent.
- Go to Reports > Expenses.
- Click Type > Task > Apply.
- Click on any task.
Expected Result:
Task will be opened.
Actual Result:
Task cannot be opened from Reports > Task.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
Screenshots/Videos
Bug7070810_1770479714031.Screen_Recording_2026-02-07_at_23.52.56.mp4
Issue Owner
Current Issue Owner: @rojiphilUpwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~022020257760591516196
- Upwork Job ID: 2020257760591516196
- Last Price Increase: 2026-02-14
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
melvin-bot commentedon Feb 7, 2026
Triggered auto assignment to @stephanieelliott (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Feb 7, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rojiphil (
External)twilight2294 commentedon Feb 7, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
When users navigate to Reports > Task and click on a task item in the search results, nothing happens — the task cannot be opened.
What is the root cause of that problem?
The root cause is that the
onSelectRowhandler in the Search component has no logic to handleTaskListItemTypeitems.In
src/components/Search/index.tsx, theonSelectRowfunction processes clicks on search result rows. It has specific handling for transaction items, report action items, transaction group items, and various group types (members, cards, categories, etc.), but it completely lacks handling for task items.When a task item is clicked, the function processes through all the type checks and eventually reaches this guard clause at lines 1080-1082:
A
TaskListItemTypeitem is none of these types (it doesn't have atransactionID,reportActionID, ortransactionsarray), so it hits the early return and no navigation occurs. The function silently exits without opening the task.What changes do you think we should make in order to solve the problem?
We should add explicit handling for
TaskListItemTypeitems in theonSelectRowfunction, just before the guard clause at line 1080.In
src/components/Search/index.tsx, add this code:You'll also need to add
TaskListItemTypeto the imports from@components/SelectionListWithSections/typesat the top of the file if it's not already imported.This follows the same navigation pattern used for chat/report action items at line 1131, using
ROUTES.SEARCH_REPORT.getRoute()with the task'sreportID(which is available in theSearchTasktype).What alternative solutions did you explore?
An alternative would be to navigate to a task-specific route if one exists, but
SEARCH_REPORTis the appropriate route since it handles opening any report byreportID, and tasks are a type of report in Expensify's architecture.melvin-bot commentedon Feb 7, 2026
Current assignee @rojiphil is eligible for the External assigner, not assigning anyone new.
[-]Reports - Task cannot be opened from Reports > Task[/-][+][$250] Reports - Task cannot be opened from Reports > Task[/+]melvin-bot commentedon Feb 7, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022020257760591516196
21 remaining items
michaellinhq commentedon Feb 13, 2026
Hi, I reviewed '[$250] Reports - Task cannot be opened from Reports > Task' and can start immediately. I can deliver a first usable version quickly and iterate based on your feedback. If this scope still matches your priority, I can proceed right away.
melvin-bot commentedon Feb 13, 2026
📣 @michaellinhq! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format:
michaellinhq commentedon Feb 13, 2026
Hi, I reviewed '[$250] Reports - Task cannot be opened from Reports > Task' and can start immediately. I can deliver a first usable version quickly and iterate based on your feedback. If this scope still matches your priority, I can proceed right away.
rojiphil commentedon Feb 13, 2026
@stephanieelliott Let us close the issue as it is fixed already.
81789-web-chrome-001.mp4
michaellinhq commentedon Feb 13, 2026
Hi, I reviewed '[$250] Reports - Task cannot be opened from Reports > Task' and can start immediately. I can deliver a first usable version quickly and iterate based on your feedback. If this scope still matches your priority, I can proceed right away.
michaellinhq commentedon Feb 13, 2026
Hi, I reviewed '[$250] Reports - Task cannot be opened from Reports > Task' and can start immediately. I can deliver a first usable version quickly and iterate based on your feedback. If this scope still matches your priority, I can proceed right away.
michaellinhq commentedon Feb 13, 2026
Hi, I reviewed '[$250] Reports - Task cannot be opened from Reports > Task' and can start immediately. I can deliver a first usable version quickly and iterate based on your feedback. If this scope still matches your priority, I can proceed right away.
HiepPP commentedon Feb 14, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
When users navigate to Reports > Expenses, filter by Type > Task, and click on a task item in the search results, nothing happens. The task detail page fails to open and the click is silently ignored.
What is the root cause of that problem?
The root cause is a regression introduced by PR #80833. In
src/components/Search/index.tsx, theonSelectRowfunction extractsreportIDfromTransactionListItemTypeandReportActionListItemTypeitems, but not fromTaskListItemTypeitems.At line 1123, the code only considers transaction and report action types:
When the item is a
TaskListItemType, neither cast produces a validreportIDbecause the task item structure is different. The type guardisTaskListItemType(item)exists and task items pass validation at line 1114, but thereportIDis never extracted from them.This causes
reportIDto beundefined, triggering the early return at line 1133:As a result, the task navigation code at lines 1167-1170 never executes.
What changes do you think we should make in order to solve the problem?
Add explicit
TaskListItemTypehandling to thereportIDextraction logic insrc/components/Search/index.tsx:Add
TaskListItemTypeto the imports from@components/SelectionListWithSections/types(line 16)Add
taskItemcast and include it in thereportIDextraction at lines 1121 and 1123:This minimal change ensures that when a task item is clicked, its
reportIDis properly extracted, allowing the existing task navigation code to execute.What alternative solutions did you explore? (Optional)
An alternative approach suggested by another proposal was to remove the guard clause entirely. However, this is dangerous because the guard exists to prevent navigation with invalid report IDs. Removing it could cause runtime errors when unhandled item types are clicked.
The correct approach is to handle tasks explicitly by including them in the
reportIDextraction logic, maintaining type safety while fixing the navigation bug.Another alternative was to add a separate task handling block before the guard clause with full telemetry. While this would work, it is unnecessary because the existing code at lines 1167-1170 already handles task navigation correctly - it just never gets reached due to the missing
reportIDextraction. The minimal fix of addingtaskItem.reportIDto the extraction chain is sufficient and follows the existing pattern used for other item types.Result
After the fix:
melvin-bot commentedon Feb 14, 2026
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
energypantry commentedon Feb 16, 2026
Quick conversion proposal for this issue.
24h verifiable deliverable:
2026-02-17T08:30:00Z(UTC), I will publish a draft PR that fixes opening Task from Reports, plus a reproducible verification checklist and acceptance mapping.Pricing (A/B/C):
Acceptance CTA:
stephanieelliott commentedon Feb 17, 2026
This is no longer reproducible, closing!