Offset metrics are not displayed as dashed lines on line chart in version 6.0.0.

[iercan]

Bug description

In version 6.0.0, offset metrics are no longer displayed as dashed compared to version 4.1.4, a crucial issue for us.
The issue occurs when a chart doesn't have any dimension. If a dimension added it works as expected

We would appreciate a fix in the next minor release. Thanks.

This is version 4.1.4

And this is version 6.0.0

Screenshots/recordings

No response

Superset version

master / latest-dev

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[dosubot]

This is a regression caused by a change in how Superset detects and styles offset metrics (derived series) in line charts. In recent versions, the code only applies dashed line styling to offset metrics if the chart's comparison_type is set to "Values". If it's set to anything else, offset metrics are not flagged as derived and appear as solid lines instead. This differs from earlier versions, where dashed styling was applied regardless of comparison_type (source).

Currently, there is no documented configuration or workaround to restore dashed lines for offset metrics in 6.0.0. You may be able to work around this by explicitly setting comparison_type to "Values" in your chart configuration, but if your use case requires a different comparison type, a code change will be needed to restore the previous behavior (source).

If this is critical for your workflow, tracking this as a regression for a future fix is recommended.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[anumukul]

Hi, I’d like to take this issue and can deliver a fix within 24 hours.
I’ve worked on similar projects before and have relevant experience, so I should be able to handle this efficiently.

[sfirke]

Hi @anumukul - if you would still like to contribute, go for it!

[anumukul]

Working on it