Repository navigation
[Due for payment 2026-08-19] Concierge HTML tables: make the whole row clickable and align styling with other tables #97247
Description
Activity
I can be the reviewer here since I reviewed the previous PR.
Reacted by Nguyen Van DucTriggered auto assignment to @marcochavezf, see https://stackoverflow.com/c/expensify/questions/7972 for more details.
- changed the title
[-]Concierge HTML tables: make the whole row clickable and align styling with other tables[/-][+][Due for payment 2026-08-19] Concierge HTML tables: make the whole row clickable and align styling with other tables[/+]on Aug 12, 2026 The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.52-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 2026-08-19. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
BugZero Checklist:
-
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: N/A
-
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
-
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
-
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: https://github.com/Expensify/Expensify/issues/673819
Regression Test Proposal
Precondition:
Test:
- Go to Concierge chat
- Ask the question Show my June 2026 expenses sorted by amount
- Wait until the concierge responds
- Verify the table is shown in this response
- Verify that the row is clickable and we don't show the link in the merchant column
Do we agree 👍 or 👎
Zapier Logs
Run ID: 00040eee-0f1e-a34a-37b1-d224f8032a34-
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)Payment Summary
Resolving PRs:
-
Concierge HTML tables: make the whole row clickable and align styling with other tables #97670
-
Contributor: @dukenv0307 does not require payment (Contractor)
-
Reviewer: @daledah owed $250 via NewDot
BugZero Checklist (@mallenexpensify)
- I have confirmed assignees, roles, and Upwork contracts look correct
- I have paid out Upwork contracts / manual NewDot requests
-
Payment Summary
Contributor+: @daledah due $250 via NewDot
Problem
In PR #94926 we added native support for HTML tables in Concierge responses (e.g. the expenses table). In that implementation only the Merchant cell is a link, which raised a concern in this discussion: having only one interactive cell makes the table stick out from the rest of our tables and may teach users that other "non-link" tables aren't interactable.
Proposed enhancement
Iterate on the table styling/interaction so it behaves more like our other tables (e.g. the "Recently added" table on Home):
Design mock and full context in the discussion: #94926 (comment)
Design agreed this direction is preferable and that we can improve it iteratively after the initial PR merges. This issue tracks that follow-up work.
Notes
dukenv0307flagged that making the whole row clickable + restyling is non-trivial, so it was split out of Add native support for HTML tables in responses #94926 (which merges first to fix a separate breakage). See this comment.Follow-up from PR #94926.
Issue Owner
Current Issue Owner: @mallenexpensify