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

[KPI with trendline] Time comparison isn't displayed when the value is stable and equal to 0 #17012

Closed
3 tasks
ValentinC-BR opened this issue Oct 7, 2021 · 3 comments
Labels
#bug Bug report

Comments

@ValentinC-BR
Copy link

When a KPI is equal to 0 during 2 periods, the time comparison (+ 0%) isn't displayed

How to reproduce the bug

  1. Create a KPI with trendline
  2. Write "0" in Metrics / Custom SQL
  3. Chose time comparison period = 1
  4. Run

Expected results

"+ 0%" (and the subheader !) should be displayed next to the number

Actual results

There is no subheader nor time comparison.
However, this works with stable trendlines not equal to 0

Screenshots

image

image

Environment

(please complete the following information):

  • browser type and version: Google Chrome Version 94.0.4606.71 (Oficial build) (x86_64)
  • superset version: 1.3.0
  • python version: 3.7.9
  • node.js version: doesn't apply, I run on Kubernetes, using gunicorn as server
  • source : AWS Athena
  • any feature flags active: /

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.

@ValentinC-BR ValentinC-BR added the #bug Bug report label Oct 7, 2021
@stale
Copy link

stale bot commented Apr 17, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

@stale stale bot added the inactive Inactive for >= 30 days label Apr 17, 2022
@ValentinC-BR
Copy link
Author

I may have been too evasive on this point.
What would be nice would be to display a subheader whether there is a change or not.

Otherwise, we have this kind of graphical incoherences :
image

@stale stale bot removed the inactive Inactive for >= 30 days label Apr 20, 2022
@rusackas
Copy link
Member

rusackas commented Jan 6, 2023

This looks to be resolved by the linked PR, so I'll go ahead and close it. If I'm misinterpreting here, say the word and we can re-open this :)

@rusackas rusackas closed this as completed Jan 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report
Projects
None yet
Development

No branches or pull requests

2 participants