[Feature] Add ability to filter unused tags and bulk‑delete them #2800

Closed
opened 2026-02-28 20:28:40 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @qennenat on GitHub (Jan 10, 2026).

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?

Actual Budget provides a way to identify and clean up unused payees, but there is no equivalent workflow for tags. Over time, tags accumulate as users refine their categorization system, rename tags, or stop using certain tags entirely.

Right now, there is no way to:
• filter tags that have zero associated transactions,
• confirm whether a tag is still in use, or
• delete unused tags in a safe, controlled way.

This leads to long, cluttered tag lists and makes tag hygiene difficult for users who iterate on their budgeting structure.

Describe your ideal solution to this problem

The ideal solution is to replicate the existing “Unused Payees” workflow, but for tags. Specifically:
• Add an “Unused Tags” filter or view that automatically surfaces tags with zero associated transactions.
• Provide the same safe‑delete mechanism used for unused payees, including single‑delete or multi‑select bulk deletion.
• Use the same confirmation pattern to show that deleting these tags will affect 0 transactions.
• Make the Unused Tags view visible only when at least one tag has zero associated transactions, matching the conditional visibility behavior of the unused payees feature.
This keeps the feature consistent with established UI patterns and gives users a predictable, familiar way to clean up unused tags.

Teaching and learning

To help users understand and discover this feature, the documentation and UI can follow the same patterns used for Unused Payees:
• Add a short note in the Tags documentation explaining that an Unused Tags view will automatically appear when at least one tag has zero associated transactions.
• Include a small tooltip or info icon near the Tags list clarifying how Actual determines whether a tag is unused.
• Consider a brief onboarding hint the first time unused tags are detected, similar to how unused payees are surfaced.
• Keep terminology and UI placement consistent with the existing unused‑payees workflow so users immediately recognize the pattern.
This ensures the feature is intuitive, discoverable, and easy for new users to adopt without introducing new mental models.

Originally created by @qennenat on GitHub (Jan 10, 2026). ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [x] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? **Actual Budget** provides a way to identify and clean up unused payees, but there is no equivalent workflow for tags. Over time, tags accumulate as users refine their categorization system, rename tags, or stop using certain tags entirely. Right now, there is no way to: • filter tags that have zero associated transactions, • confirm whether a tag is still in use, or • delete unused tags in a safe, controlled way. This leads to long, cluttered tag lists and makes tag hygiene difficult for users who iterate on their budgeting structure. ### Describe your ideal solution to this problem The ideal solution is to replicate the existing “Unused Payees” workflow, but for tags. Specifically: • Add an “Unused Tags” filter or view that automatically surfaces tags with zero associated transactions. • Provide the same safe‑delete mechanism used for unused payees, including single‑delete or multi‑select bulk deletion. • Use the same confirmation pattern to show that deleting these tags will affect 0 transactions. • Make the Unused Tags view visible only when at least one tag has zero associated transactions, matching the conditional visibility behavior of the unused payees feature. This keeps the feature consistent with established UI patterns and gives users a predictable, familiar way to clean up unused tags. ### Teaching and learning To help users understand and discover this feature, the documentation and UI can follow the same patterns used for Unused Payees: • Add a short note in the Tags documentation explaining that an Unused Tags view will automatically appear when at least one tag has zero associated transactions. • Include a small tooltip or info icon near the Tags list clarifying how Actual determines whether a tag is unused. • Consider a brief onboarding hint the first time unused tags are detected, similar to how unused payees are surfaced. • Keep terminology and UI placement consistent with the existing unused‑payees workflow so users immediately recognize the pattern. This ensures the feature is intuitive, discoverable, and easy for new users to adopt without introducing new mental models.
GiteaMirror added the needs votesfeature labels 2026-02-28 20:28:40 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 10, 2026):

Thanks for sharing your idea!

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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 (Jan 10, 2026): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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 -->
Author
Owner

@csenel commented on GitHub (Jan 11, 2026):

For now, you can delete all (or some) tags and Find Existing Tags option will bring back the ones that are in use. You lose the color setting if you do this but one might assume you add colors to tags you are actively using.

Nevertheless I think it's a good suggestion, same functionality exists for payees.

@csenel commented on GitHub (Jan 11, 2026): For now, you can delete all (or some) tags and `Find Existing Tags` option will bring back the ones that are in use. You lose the color setting if you do this but one might assume you add colors to tags you are actively using. Nevertheless I think it's a good suggestion, same functionality exists for payees.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2800