[Feature] Sort payees by transaction count and volume #770

New Issue

GiteaMirror · 2026-02-28T19:18:36-06:00

GiteaMirror commented

2026-02-28 19:18:36 -06:00

Originally created by @curiousercreative on GitHub (Nov 28, 2023).

Verified feature request does not already exist?

I have searched and found no existing issue

💻

Would you like to implement this feature?

Pitch: what problem are you trying to solve?

I have a lot of transactions already and a lot of payees. I'd like to create rules, but because there are so many payees, I must focus my efforts. I'd like to focus on the most common payees and those that are responsible for most of my expenses.

Describe your ideal solution to this problem

I think we could add table columns for transaction count and volume and then make the table sortable by any column (right now it sorts on payee name). A bonus would be to link each payee row to a transactions table filtered for that payee.

Teaching and learning

Perhaps a new section on the [rules documentation]?

Originally created by @curiousercreative on GitHub (Nov 28, 2023). ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? I have a lot of transactions already and a lot of payees. I'd like to create rules, but because there are so many payees, I must focus my efforts. I'd like to focus on the most common payees and those that are responsible for most of my expenses. ### Describe your ideal solution to this problem I think we could add table columns for transaction count and volume and then make the table sortable by any column (right now it sorts on payee name). A bonus would be to link each payee row to a transactions table filtered for that payee. ### Teaching and learning Perhaps a new section on the [rules documentation]?

GiteaMirror added the needs votes feature labels 2026-02-28 19:18:36 -06:00

GiteaMirror closed this issue

2026-02-28 19:18:37 -06:00

GiteaMirror commented

2026-02-28 19:18:37 -06:00

@github-actions[bot] commented on GitHub (Nov 28, 2023):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

@github-actions[bot] commented on GitHub (Nov 28, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍!