Skip to content
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

Functional question about "Income" and "Transfer" vs normal buckets #196

Open
cpo opened this issue May 1, 2018 · 5 comments
Open

Functional question about "Income" and "Transfer" vs normal buckets #196

cpo opened this issue May 1, 2018 · 5 comments
Milestone

Comments

@cpo
Copy link

cpo commented May 1, 2018

Not a real bug report but more of a functional question maybe:

I am wondering wether or not the "Income" built in bucket should be replaced with a new bucket type (does an "income" bucket make any sense?)

I am by no means an expert on budgeting, but I would like to see forecasted income categories in the overviews. Also, on realized income I'd like to see to what income they relate to. Currently, everything incoming is displayed as "income", regardless if it is (for example) salary or child support.

Or would it make sense/is it the buckets way to add a bucket with a negative "want"? Just throwing it out there :-)

@iffy iffy added the question label May 2, 2018
@iffy
Copy link
Contributor

iffy commented May 2, 2018

@cpo I think those two things you want are totally valid:

  1. Forecasted income (I'd love to hear more about what you're expecting here. Do you have some examples?)
  2. Reporting/summarizing based on the type income (e.g. salary, child support, interest, etc...)

Do you think you'd be able to achieve those two things if transactions had payees (#101) that you could group and split reports by? I ask because I'm not sure income as a bucket works but I suspect you could get what you want with payees. Or... I guess "pay-ers" in the case of income :)

@Limezy
Copy link

Limezy commented May 2, 2018

From my side, I would love to have more detailed view of my "Incomes".
Payees would be IMHO the best way to split incomes.

@cpo
Copy link
Author

cpo commented May 3, 2018

Payees sound like a great idea, however for me, the main charm of the app is it's simplicity. Setting up buckets and splitting transactions over them is simple and effective. Setting up buckets and payees sounds like more work :-)

Having said that, being able to not only see the expected expense (the buckets' want) but also see the projected income (buckets generating rain?) would be a great addition. When I enter a bucket with a negative want, it gets ignored when "letting it rain", maybe it could "generate rain"?

But then again, I have squat knowledge of budgetting softwares so I gladly let you guys take me by the hand :-)

@iffy
Copy link
Contributor

iffy commented May 3, 2018

@cpo Okay, I think I understand what you want. You want somewhere in the app to be able to enter:

  • I get $1000/mo from income
  • I get $300/mo from child support
  • I get $200/mo from something else...

Let me think about how that could work.

@iffy iffy added this to the v1 milestone Dec 7, 2021
@iffy iffy removed the question label Dec 7, 2021
@iffy
Copy link
Contributor

iffy commented Dec 7, 2021

Related to #330

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

No branches or pull requests

3 participants