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

Proposal for Waterfall chart improvement in handling first and last subtotals (do not add SIP number) #30320

Open
code-luac opened this issue Sep 18, 2024 · 2 comments
Labels
design:proposal Design proposals viz:charts Namespace | Anything related to viz types

Comments

@code-luac
Copy link

Please make sure you are familiar with the SIP process documented
here. The SIP will be numbered by a committer upon acceptance.

[SIP] Proposal for Waterfall chart improvement in handling first and last subtotals<title>

Motivation

  1. Today, the implementation assumes that the first value in the series is zero. However, this is not always the case. For example, I want to review the evolution of my task backlog over time (opened vs. closed tickets and subtotals with a weekly time grain). When filtering for a particular time window (not from the beginning of time), I want to see how many open tickets there were at the beginning of this period.
  2. Today, the last bar in the chart displays the subtotal. I want to control whether this last subtotal appears or not.

This brings the waterfall chart to par with Google Sheets and MS Excel.

Proposed Change

I used the following screenshot from Google Sheets to serve as my wireframe.
Requirements for the Waterfall Chart settings (see the markup in the screenshot):

  1. A new checkbox "Use first value as subtotal" - when checked, render the first bar in the chart as a subtotal (gray) using the first value in the series.
  2. A new checkbox "Add subtotal after last value in series" - when checked, render the last bar in the chart as a subtotal (gray) representing the series' total.
    image

New or Changed Public Interfaces

Describe any new additions to the model, views or REST endpoints:
Change the chart settings API to reflect the 2 new settings checkboxes.

Describe any changes to existing visualizations, dashboards and React components. Describe changes that affect the Superset CLI and how Superset is deployed:
See proposed change section above.

New dependencies

None

Migration Plan and Compatibility

None

Rejected Alternatives

None

@code-luac code-luac added the sip Superset Improvement Proposal label Sep 18, 2024
@dosubot dosubot bot added design:proposal Design proposals viz:charts Namespace | Anything related to viz types labels Sep 18, 2024
@michael-s-molina michael-s-molina changed the title [SIP] Proposal for Waterfall chart improvement in handling first and last subtotals (do not add SIP number) Proposal for Waterfall chart improvement in handling first and last subtotals (do not add SIP number) Sep 26, 2024
@michael-s-molina michael-s-molina removed the sip Superset Improvement Proposal label Sep 26, 2024
@michael-s-molina
Copy link
Member

Hi @code-luac. I believe this is a valid feature request that does not require a SIP given its scope. I don't have the bandwidth to implement this now as I'm focused on stabilizing 4.1 but I hope someone from the community can provide such feature as it would be valuable.

@rusackas
Copy link
Member

Agreed with Michael. We'd welcome a PR with these changes. If you don't want to consider it a SIP, I think there are two potential moves for this issue:

  1. We can move it to an Ideas discussion thread if you want more discussion/feedback/help with it
  2. We can leave it here if you have more immediate plans to open a PR that closes it.
    Let us know which seems appropriate, and thanks for the input/ideas!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design:proposal Design proposals viz:charts Namespace | Anything related to viz types
Projects
None yet
Development

No branches or pull requests

3 participants