github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-15 22:54:03 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #2087] [Feature] Allow filtering out locked transactions when filtering by cleared field #7755

New Issue
Closed
opened 2026-04-10 17:45:35 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-10 17:45:35 -05:00
Owner
Copy Link

Originally created by @Jackenmen on GitHub (Dec 14, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2087

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?

After bank sync, new transactions can show up earlier in the transaction history (between other locked transactions) and I would like to be able to easily find them. Currently, they don't stand out when you have a long list of locked transactions and a single cleared but not locked transaction somewhere in that list.

Describe your ideal solution to this problem

I would like to have a way to see only the cleared but not locked transactions using the filters. I suggest changing the current "Cleared" filter from "is true" and "is false" options to a multi-select ("one of") list allowing you to choose which of the "locked", "cleared", and "uncleared" states should be shown in the transaction list.

Teaching and learning

It's an enhancement to the existing "Cleared" filter so discoverability stays just as easy as it already is.

Originally created by @Jackenmen on GitHub (Dec 14, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/2087 ### 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? After bank sync, new transactions can show up earlier in the transaction history (between other *locked* transactions) and I would like to be able to easily find them. Currently, they don't stand out when you have a long list of locked transactions and a single cleared but not locked transaction somewhere in that list. ### Describe your ideal solution to this problem I would like to have a way to see only the cleared but not locked transactions using the filters. I suggest changing the current "Cleared" filter from "is true" and "is false" options to a multi-select ("one of") list allowing you to choose which of the "locked", "cleared", and "uncleared" states should be shown in the transaction list. ### Teaching and learning It's an enhancement to the existing "Cleared" filter so discoverability stays just as easy as it already is.
GiteaMirror added the feature label 2026-04-10 17:45:35 -05:00
GiteaMirror commented 2026-04-10 17:45:38 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 14, 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 👍!

<!-- gh-comment-id:1856462462 --> @github-actions[bot] commented on GitHub (Dec 14, 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 👍! <!-- feature-auto-close-comment -->
GiteaMirror commented 2026-04-10 17:45:39 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Dec 14, 2023):

This isn't a filter but does this work for you? https://github.com/actualbudget/actual/pull/1994

<!-- gh-comment-id:1856468619 --> @youngcw commented on GitHub (Dec 14, 2023): This isn't a filter but does this work for you? https://github.com/actualbudget/actual/pull/1994
GiteaMirror commented 2026-04-10 17:45:40 -05:00
Author
Owner
Copy Link

@Jackenmen commented on GitHub (Dec 14, 2023):

I think that a filter would still be preferable but the PR you linked could help, if it takes locked state into account, yes.

For now, though, #1994 doesn't actually take into account whether the transaction is locked or not, I left a comment about it:
https://github.com/actualbudget/actual/pull/1994#issuecomment-1856474882
I'm not sure what order would make it easier to spot, i.e. whether "locked" would be in the center such as in locked,cleared,uncleared, or at one of the ends such as in uncleared,locked,cleared or locked,uncleared,cleared.

<!-- gh-comment-id:1856487318 --> @Jackenmen commented on GitHub (Dec 14, 2023): I think that a filter would still be preferable but the PR you linked could help, if it takes locked state into account, yes. For now, though, #1994 doesn't actually take into account whether the transaction is locked or not, I left a comment about it: https://github.com/actualbudget/actual/pull/1994#issuecomment-1856474882 I'm not sure what order would make it easier to spot, i.e. whether "locked" would be in the center such as in `locked,cleared,uncleared`, or at one of the ends such as in `uncleared,locked,cleared` or `locked,uncleared,cleared`.
GiteaMirror commented 2026-04-10 17:45:40 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Feb 8, 2024):

@Jackenmen Can this be closed?

<!-- gh-comment-id:1934418600 --> @youngcw commented on GitHub (Feb 8, 2024): @Jackenmen Can this be closed?
GiteaMirror commented 2026-04-10 17:45:41 -05:00
Author
Owner
Copy Link

@Jackenmen commented on GitHub (Feb 8, 2024):

#2108 solved this, yeah.

<!-- gh-comment-id:1934433124 --> @Jackenmen commented on GitHub (Feb 8, 2024): #2108 solved this, yeah.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#7755
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?