Before the 3.0.1 :
After the 3.0.1 :
How to reproduce the bug
- Create a bar chart
- Add a time delay to visualize a comparison between the bar (a year, a month, it does not matter)
- Before the 3.0.1, each couple of bar had two colors, now they are all in the same color
Environment
- superset version:
3.0.1
Comment From: sfirke
When you say "before 3.0.1" do you mean 3.0.0 did not have this problem? What's the latest official release you've found that has the prior, desired behavior?
Comment From: martin-raymond
we were using the 2.1.0 version, and now we have upgraded to 3.0.1 @sfirke
Comment From: michael-s-molina
This was a side-effect of another fix. They should have the same color but we need to add a differentiator between normal and offset bars similar to what the line chart does by using dashed lines. I can take a look at this problem.
Comment From: CairoLee
I also have the same question. For line charts, using dashed lines to differentiate offset lines for the same indicator is possible. But for bar charts, I think maintaining the previous logic might seem more reasonable.
I prefer to have them display different colors, especially when we are only drawing a single indicator and want to compare the data from a week ago. Showing different colors would be very convenient for observation.
But when we are drawing multiple indicators and want to compare the data from a week ago for all of them, using the same color but different styles should be more convenient for observation.
Comment From: jack-chao-htg
In line charts, it makes the time-delay lines dotted instead of solid but in the same color. This is pretty nice, however, if you have multiple time-delay lines, they will all look identical.
Comment From: michael-s-molina
Thank you all for the discussion.
I prefer to have them display different colors, especially when we are only drawing a single indicator and want to compare the data from a week ago. Showing different colors would be very convenient for observation.
My concerns here would be: - Consistency on how we display offsets between charts. It will be hard for users to understand how to view offsets if we use different color strategies for every chart. - Multiple series and their offsets. If a bar chart has multiple series, it's hard to identify the offsets if the colors don't match.
In line charts, it makes the time-delay lines dotted instead of solid but in the same color. This is pretty nice, however, if you have multiple time-delay lines, they will all look identical.
You're correct. We would be need have a number of patterns (dashed, solid, dotted, etc) equal to the number of supported offsets to differentiate the metrics.
Tagging @kasiazjc to bring the designer's perspective to the discussion.
Comment From: cdr4321
Any update on this? We recently switched over to Superset for analytics and I've been getting some complaints about this exact issue.
Comment From: eschutho
I noticed that the behavior is different when using multiple metrics and "Truncate Metric" is unselected if anyone wants to test that out for your use-case.
Comment From: mathieudruart
Hi @eschutho with our use-case it doesn't seem to change anything (Superset 3.0.3) :
Comment From: cdr4321
Same for me. We are on 3.0.1
Comment From: Naga-BI
Same for me. Version 3.1.3. Any update on whether the issue will be fixed?
Comment From: eschutho
We're currently looking into some improvements here. Perhaps by the 4.2 release.
Comment From: jbonaoned
Hello, I'm checking in.When is the release of version 4.2 scheduled?
Comment From: rusackas
It's not clear if there will be a 4.2... though there may well be. We're beginning to focus on 5.0, so 4.x.x releases will be as-needed for patches, or as-wanted by a volunteer release manager (e.g. @sadpandajoe). You can join us on slack in the various release channels if you want to keep an ear out or get involved in the process.
Comment From: shexiaobin
I'm using version 4.1, but I also encountered this problem. It didn't happen before a few days ago. It just suddenly occurred recently. Is there any way to alleviate it?
Comment From: rusackas
Closing this since 3.0 is no longer supported, and 4.1 is even a bit iffy, since 5.0 is out and we're working toward 5.0.
I'm going to close this particular issue since it's a bit dated in those ways, and because it's been inactive for months now. If anyone is still experiencing this in 4.1.3 and/or 5.0, let us know and we can either reopen this issue, or (my preference) link to it in a NEW issue with fresh context and reproduction steps/examples.