github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-11 04:32:39 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Feature] Create new Category when inputting a new transaction, just like creating a new Payee. #1763

New Issue
Closed
opened 2026-02-28 19:54:06 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 19:54:06 -06:00
Owner
Copy Link

Originally created by @technohiker on GitHub (Jan 11, 2025).

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?

When selecting a Payee for a transaction, we are given a list of Payees to choose from, but we can also type in a new Payee and have it created immediately for the new transaction. This functionality does not exist for the Category field of a transaction. If I come up with a new category, I have to leave the transaction section and go to my budget in order to create a new one, then come back to that transaction to finish creating it. Both the Category and Payee field should be capable of the same functionality.

Describe your ideal solution to this problem

The makeNew function within the PayeeAutocomplete file should be replicated within the CategoryAutocomplete file. At the moment, the function does not exist within CategoryAutocomplete. It doesn't look like it would be a simple copy & paste though, as the makeNew function it utilized in Autocomplete props like onSelect and onUpdate, and a function called handleSelect that are not implemented at all in CategoryAutocomplete.

I am willing to open up a Pull Request myself, but I wanted time to familiarize myself with the two different files. I also wanted to ask, how come PayeeAutocomplete and CategoryAutocomplete have noticeably different implementations?

Teaching and learning

No response

Originally created by @technohiker on GitHub (Jan 11, 2025). ### 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? When selecting a Payee for a transaction, we are given a list of Payees to choose from, but we can also type in a new Payee and have it created immediately for the new transaction. This functionality does not exist for the Category field of a transaction. If I come up with a new category, I have to leave the transaction section and go to my budget in order to create a new one, then come back to that transaction to finish creating it. Both the Category and Payee field should be capable of the same functionality. ### Describe your ideal solution to this problem The [makeNew](https://github.com/actualbudget/actual/blob/1c6697a7eea756c4a2a5d3202771787e1643df14/packages/desktop-client/src/components/autocomplete/PayeeAutocomplete.tsx#L103) function within the PayeeAutocomplete file should be replicated within the CategoryAutocomplete file. At the moment, the function does not exist within CategoryAutocomplete. It doesn't look like it would be a simple copy & paste though, as the makeNew function it utilized in Autocomplete props like onSelect and onUpdate, and a function called [handleSelect](https://github.com/actualbudget/actual/blob/1c6697a7eea756c4a2a5d3202771787e1643df14/packages/desktop-client/src/components/autocomplete/PayeeAutocomplete.tsx#L325) that are not implemented at all in CategoryAutocomplete. I am willing to open up a Pull Request myself, but I wanted time to familiarize myself with the two different files. I also wanted to ask, how come PayeeAutocomplete and CategoryAutocomplete have noticeably different implementations? ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-02-28 19:54:06 -06:00
GiteaMirror commented 2026-02-28 19:54:07 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 11, 2025):

✨ 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 (Jan 11, 2025): :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-02-28 19:54:07 -06:00
Author
Owner
Copy Link

@gitchap commented on GitHub (Jan 25, 2025):

I just added a similar request -- #4240

@gitchap commented on GitHub (Jan 25, 2025): I just added a similar request -- #4240
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
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature needs votes
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#1763
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?