madankgit opened a new issue, #37673:
URL: https://github.com/apache/superset/issues/37673

   ### Bug description
   
   In Superset version 6.0, the conditional formatting color scheme options for 
charts have been reduced from 8 to 5, and the remaining colors are generally 
dull or visually unappealing.
   
   This makes it difficult to apply meaningful color gradients for numerical 
values, reducing the effectiveness of visual cues in dashboards and reports
   
   <b></b>
   **Previous Behavior**
   
   All previously available 8 color schemes should be present
   Colors should be vibrant and distinguishable to effectively represent 
numerical ranges
   
   <img width="229" height="263" alt="Image" 
src="https://github.com/user-attachments/assets/b880e4bc-a175-4b29-85ac-a3327b322094";
 />
   
   <b></b>
   **Current Behavior**
   
   Only 5 color schemes are available
   The colors are dull and not suitable for highlighting differences in 
numerical values
   
   <img width="121" height="197" alt="Image" 
src="https://github.com/user-attachments/assets/ddc12739-fe72-4770-9810-608c9dffc034";
 />
   
   <b></b>
   **Impact**
   
   - Reduced visual clarity in dashboards
   - Difficult to differentiate metric ranges using color cues
   - Users may need to rely on theme overrides or custom plugins, which is not 
feasible for standard deployments
   
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   6.0.0
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [x] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [x] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [x] 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.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to