Before, if a project had its own time-related filters (ones custom to their use case), they might clash with the default time ranges in crystal (in the last month, in the past two weeks, etc) and lead to errors in the conversation. Now, crystal fully supports any configured dynamic filters that relate to time (i.e., period, season, etc.) — resulting in less misclassification errors for members.