Skip to content

Bug: Income category is present in Expense transaction. Also Vice versa #2016

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
5 of 9 tasks
sammieboy97 opened this issue Mar 21, 2025 · 5 comments · May be fixed by #2082
Open
5 of 9 tasks

Bug: Income category is present in Expense transaction. Also Vice versa #2016

sammieboy97 opened this issue Mar 21, 2025 · 5 comments · May be fixed by #2082

Comments

@sammieboy97
Copy link

sammieboy97 commented Mar 21, 2025

General checklist

  • I have removed personal / sensitive data from screenshots and logs
  • I have searched existing issues and discussions to ensure this is not a duplicate issue

How are you using Maybe?

  • I am a paying Maybe customer (hosted version)
    • Paying Maybe users can also open requests in Intercom (if there is sensitive info involved)
  • I am a self-hosted user

Self hoster checklist

Paying, hosted users should delete this entire section.

If you are a self-hosted user, please complete all of the information below. Issues with incomplete information will be marked as Needs Info to help our small team prioritize bug fixes.

  • Self hosted app commit SHA (find in user menu): [enter commit sha here]
    • I have confirmed that my app's commit is the latest version of Maybe
  • Where are you hosting?
    • Render
    • Docker Compose
    • Umbrel
    • Other (please specify) - In Local

Bug description

Income category is present in Expense transaction. Also Vice versa

To Reproduce

Create Expense Category
Open Transaction tab
Open create new Transaction
Open Income Tab
Click on Category, the Expense category you created will be visible

Expected behavior

Only Income categories should be present inside Income transaction.
Same for expense

Screenshots and/or recordings

Image

@sammieboy97
Copy link
Author

I can take this up to fix if this is not an expected behavior

@zachgoll
Copy link
Collaborator

@sammieboy97 good catch, this is not expected behavior. I think we should only show "expense" categories when dealing with expenses as you mention.

@sammieboy97
Copy link
Author

I'm taking this up. Will raise a PR soon. Thanks for confirming @zachgoll

@kirill-andr
Copy link

@sammieboy97 this would be a very valuable fix as I am also struggling with this one. On a side note, there are a few more bugs that I have noticed around this issue:

  • In Home -> Budgets the income categories do not show up for some reason. I can see that XX% of Income came from Salary, but the list of categories in the right column only shows expenses.
  • In Account -> Categories -> New Category. When choosing Income, it is possible to select an Expense category as a parent Category. It should only allow Income Categories to be parents of other Income categories. I have checked that it is also possible to have an Income category to be a parent of Expense category.

@javiermartingonzalez
Copy link

@sammieboy97 Yes, it's an issue that still present from a while.

Don't forget to check it on CSV import page, when you are assigning categories to the imported data, it is showing all categories for positive and negative amounts.

Also, I don't know if is the expected behaviour, but you are not able to have a category with the same name as income and expense. Sometimes, it could be useful. For example, C2C payments like "Bizum" in Spain could be income or expense (it deppends if you are receiving or sending the payment). Now I have to create 2 categories "Bizum Income" and "Bizum Expense" but with this approach it's hard to automatize the categories based on the concept. So, will be great if you take a look on that and say your comments about that implementation :)

Thank you

@D-Gaspa D-Gaspa linked a pull request Apr 11, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants