Iconic-Aman opened a new issue, #35636: URL: https://github.com/apache/superset/issues/35636
### Bug description ### Summary When using the **Big Number with Trendline** chart and setting the **time grain** to "Week", Apache Superset only displays the **start date** of the week when a **custom date format** is applied. The **adaptive format** correctly displays a full date range (e.g., `2025-10-13 — 2025-10-19`), but it cannot be customized. Custom formats like `%d-%m-%Y` show only `2025-10-13`, omitting the end date of the range. --- ### Steps to Reproduce 1. Create a **Big Number with Trendline** chart. 2. Set the **Time grain** to `Week`. 3. Under **Customize → Date format**, select a **custom format** (e.g., `%d-%m-%Y`). 4. Observe that only the **start date** of the week is displayed. --- ### Expected Behavior - The chart should display both **start** and **end** dates for weekly ranges. - Custom formats like `%d-%m-%Y` should render as: 13-10-2025 — 19-10-2025 instead of just `13-10-2025`. --- ### Actual Behavior - Only the **start date** (`2025-10-13`) is shown. - Adaptive format shows full range but cannot be customized. --- ### Impact This limits localization and readability for dashboards where weekly data needs to be displayed in a regional format (e.g., DD-MM-YYYY). It affects KPI dashboards using **Big Number with Trendline** with **Week** time grain. --- ### Environment - **Chart type:** Big Number with Trendline - **Time grain:** Week - **Superset version:** [Your Superset version] - **Browser/OS:** [Your setup] --- ### Additional Context There appears to be no built-in configuration or workaround for customizing both start and end date formats for week grains. This has been observed and mentioned in Superset community discussions as a current limitation. ### Screenshots/recordings _No response_ ### Superset version 5.0.0 ### Python version I don't know ### Node version I don't know ### Browser Firefox ### Additional context _No response_ ### Checklist - [x] 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. -- 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]
