goto-loop opened a new issue, #21548: URL: https://github.com/apache/superset/issues/21548
When using the Predictive Analytics feature found in different time-series charts, the options TIME GRAIN and FORECAST PERIODS control the forecast granularity and the number of forecasted datapoints, respectively. For example: - TIME GRAIN = Day, FORECAST PERIODS = 10 → forecast the next 10 days - TIME GRAIN = Week, FORECAST PERIODS = 3 → forecast the next 3 weeks When adding a chart with Predictive Analytics to a dashboard, TIME GRAIN can be controlled through a dashboard filter. However, when the value is changed on the dashboard level, the option is ignored by the forecast. #### How to reproduce the bug 1. Create new Time-series Line Chart with new_members_daily dataset. 2. Under METRICS, select AVG(new_members). 3. Open Predictive Analytics section, check ENABLE FORECAST. 4. Click CREATE CHART and save it. 5. Create new dashboard, add chart created above, save. 6. Add new filter of type Time grain, save. 7. Select Month and hit APPLY FILTERS. 8. Look at the length of the prediction: The distance between forecasted datapoints is still a day, not a month. ### Expected results The selected time grain gets applied to the Prophet forecast in the chart. ### Actual results The forecast is performed using the same time grain the chart has been saved with. #### Screenshots TIME GRAIN = Month set on Chart level – this is the expected result.  TIME GRAIN = Month set on Dashboard level – the actual result. As above, the forecast contains 10 values, but the distance between them is one day, not one month.  ### Environment - browser type and version: Firefox 105.0 - superset version: 2.0.0 - python version: 3.9.13 - node.js version: 16.16.0 ### 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. - [x] I have reproduced the issue with at least the latest released version of superset. - [x] I have checked the issue tracker for the same issue and I haven't found one similar. -- 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]
