You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Lost Leads" (pink bar) too thin in Leads chart on Dashboard – visually unclear
Issue Description
In the Dashboard → Leads chart, the pink bars for "Lost Leads" are rendered much thinner than the other bars ("Total Leads" in purple and "Won Leads" in cyan). This causes a visual inconsistency and makes it difficult to identify lost leads at a glance — especially when multiple bars are closely grouped.
This is a UI rendering bug, not a data issue.
Preconditions
Framework Version: Krayin CRM v2.1
Commit ID: (Provide your commit ID if available)
Steps to reproduce
Log in to Krayin CRM.
Navigate to Dashboard.
Check the Leads chart.
Observe the pink bars representing "Lost Leads" around dates with high activity (e.g., April 9–10).
Expected result
Pink "Lost Leads" bars should have equal or proportionate width to other bars.
They should be clearly visible and distinguishable without having to closely inspect or hover.
UI should support quick visual analysis of all lead types.
Screenshot:
Actual result
Pink "Lost Leads" bars are rendered very thin — barely visible in the graph, especially next to wider bars for Total and Won Leads.
This causes confusion or misinterpretation of lost lead count.
Users may miss lost lead data at a glance.
Visually unbalanced UI affects usability.
The text was updated successfully, but these errors were encountered:
Bug report
Title
"Lost Leads" (pink bar) too thin in Leads chart on Dashboard – visually unclear
Issue Description
In the Dashboard → Leads chart, the pink bars for "Lost Leads" are rendered much thinner than the other bars ("Total Leads" in purple and "Won Leads" in cyan). This causes a visual inconsistency and makes it difficult to identify lost leads at a glance — especially when multiple bars are closely grouped.
This is a UI rendering bug, not a data issue.
Preconditions
Steps to reproduce
Expected result
Screenshot:
Actual result
The text was updated successfully, but these errors were encountered: