You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Support pinning columns in the spend table #104080
Clicking the caret that shows up when hovering a column
When 'pin left' is selected for multiple columns
Implementation details
We will store the pinned columns in a new search value in the search query: left-pinned-columns:column1,column2 and right-pinned-columns:column1,column2. This will allow search to persist the users pinned columns, per search key
We will start by pinning columns in the order they were pinned in
The 'Hide column' button in the menu will remove the column from the current columns list
I'm going to be OOO tomorrow, so I'll pick it up on Monday
@JS00001 do we want to implement resizable table columns first (at least the core functionality), given we probably want pinned columns to be resizable too?
@Expensify/design have we considered violations text on the pinned columns?
If we pin a column that is too narrow, the violation text will overflow the pinned edge
we can truncate the text, but I wonder if you see some other solution 🤔
The first real pinning PR landed today 🎉 You can pin and unpin Spend columns from the column menu (still behind the pinnableTableColumns beta). For now, pinned columns only move to the start or end of the table. Keeping them in place while scrolling comes next.
changed the title [-][Due for payment 2026-11-20] Support pinning columns in the spend table[/-][+]Support pinning columns in the spend table[/+]on Nov 21, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.51-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
melvin-bot commentedon Oct 15, 2026
Current assignee @dubielzyk-expensify is eligible for the NewFeature assigner, not assigning anyone new.
war-in commentedon Oct 15, 2026
I'm going to be OOO tomorrow, so I'll pick it up on Monday
@JS00001 do we want to implement resizable table columns first (at least the core functionality), given we probably want pinned columns to be resizable too?
JS00001 commentedon Oct 15, 2026
hmm, @JmillsExpensify wdyt?
JmillsExpensify commentedon Oct 15, 2026
Yes, I think that's a good call. No immediate hurry on this, let's do it after resizable columns.
melvin-bot commentedon Oct 20, 2026
@war-in Eep! 4 days overdue now. Issues have feelings too...
24 remaining items
expensify-chore-bot commentedon Nov 19, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)war-in commentedon Nov 20, 2026
Not a deploy blocker (feature behind a beta). We'll handle this in a followup
war-in commentedon Nov 20, 2026
@Expensify/design have we considered violations text on the pinned columns?
If we pin a column that is too narrow, the violation text will overflow the pinned edge
we can truncate the text, but I wonder if you see some other solution 🤔
war-in commentedon Nov 20, 2026
EOW update
The first real pinning PR landed today 🎉 You can pin and unpin Spend columns from the column menu (still behind the
pinnableTableColumnsbeta). For now, pinned columns only move to the start or end of the table. Keeping them in place while scrolling comes next.In review:
Draft:
Merged:
Next:
FYI, I'm going to be OOO next week and @jakubkalinski0 will take over most of my issues
jakubkalinski0 commentedon Nov 20, 2026
Hi everyone, it is me who will be looking after this issue next week while @war-in is OOO, so feel free to ping me with anything related!
shawnborton commentedon Nov 20, 2026
I think truncating makes the most sense personally?
dannymcclain commentedon Nov 20, 2026
Yeah I think truncating would be totally fine here.
JmillsExpensify commentedon Nov 20, 2026
Agreed, that's fine.
[-][Due for payment 2026-11-20] Support pinning columns in the spend table[/-][+]Support pinning columns in the spend table[/+]melvin-bot commentedon Nov 21, 2026
@Krishna2323
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.51-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Contributor+ Checklist: The following checklist (instructions) needs to be completed before this issue can be closed:
If no checklist is needed for this issue, use the K2 [no checklist button].