-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Feedback]: Sankey Chart #1919
Comments
This is a cool graph, I love the idea! It needs to add theme colors and privacy blocks to enable those features for this chart. Needs done on chart page as well as overview card. Cheers! |
Great points, agreed. I'll add those above. |
Sick chart! |
It would be neat if there was a bit more control of the level of detail shown, For instance toggling showing the final categories |
Nice to haves:
|
Bug (possibly applicable to other reports too): payees not showing up when filtering Screen.Recording.2023-11-27.at.19.59.25.mov |
Looks nifty, thanks for working on this. My 2 cents: I notice the right side of budget the output doesn't extend the full way down, is this money added to the budget but not spent? If so I'd create a ghost category or a label to indicate this, as otherwise it looks like something is missing. |
Feature request, option to end the graph at Category Group level. This will allow better scaling and a nice high level view. |
All the incoms should flow insider a container "income". Then incombe + residual budget (previous periodo) = budget... Then add 1 output "remaining budget" (not spent) |
@shaankhosla what's the plan with the sankey graph? If we can't get it in as a stable feature I'd be inclined to cut it. Experimental features aren't meant to live around forever. |
I think the only thing that needs an update would be the dark mode colors. Everything else seems to be just nice to have additions. |
Yep I agree, theme colors and the privacy blocks are critical. I'll work on adding those. |
Enjoying the sankey report, it's really handy to see if my catagories are roughly sane, if one gets too big like I am throwing things in general I can see at a glance that it might need splitting. Came here to say privacy bloicks are not working, but looks like that's already known. Wanted to show off the feature but not the values . |
I have an issue, the income from my employer (payee "employer inc") goes to 2 different accounts ("account a", "account b") every month. Unfortunately on the sankey it only shows income that flows to "account b". My workaround is to set 2 different payees. I also believe that showing "<1k" makes the category breakdown cluttered and meaningless. The easiest solution would be to add decimal, "0.9k" uses the same space but is way more meaningful. Percentages would work well too. |
I would like all the "income" to come from the Income category, instead of from the Payee. The reason is because my payee names are often different and it's a hassle trying to standardise the payee name of deposits just so it appears properly in the Sankey diagram. I think using the Category is a better way. Does anyone agree or have another suggestion? |
/ed/ Actually in hindsight for my comment, it doesn't make sense they aren't grouped by category in the first place given the rest is by category. If people want to represent different sources, they likely already have different categories. |
👋 This feature hasn't been worked on in a very long time. As per the new experimental feature flag policy - we'll be removing it soon unless someone picks it up again. |
very sorry to hear that, this was an awesome report chart |
I miss this feature! I feel like it was the first report that actually helped me get a handle on the big picture! |
Fingers crossed someone can bring it back |
For what it worth, I'd like to bump it too. |
Bumping this feature up, this is such a great chart |
I'm ramping up on the codebase and a big fan of this type of chart. I intend to reimplement this feature once I've learned enough about the codebase |
Known issues:
Upcoming additions:
The text was updated successfully, but these errors were encountered: