When creating or editing saved views with the “Quarter of year” filter, only the first quarter (Q1) appears to save correctly. Attempts to save Q2, Q3, or Q4 quarter selections cause the screen to flash and revert the view back to the previous dataset with the filter reset to Q1. This prevents users from creating accurate quarter-based reports.
Steps to Reproduce
Open an existing view or create a new view.
Set the date filter to Quarter of year and choose a quarter other than Q1 (for example, Q2 or Q3).
Apply the filter and confirm the results update accordingly.
Click Save or Save / Overwrite.
Observe that the screen flashes and the view reverts to the previous dataset with the filter reset to Q1.
Repeat with duplicated views or newly created views to confirm the issue persists.
We’re already looking into this and analyzing the issue. We’ve prioritized all of your reported issues and hope to have the first findings within the next one or two days. I’ll keep you updated as soon as we know more.
And thank you again for the great report! The description is incredibly detailed and really helpful!
The only thing I couldn’t open was the video. I think the community embedding may be blocking it on our side. But your explanation was so good that I think we already have a strong chance of reproducing the issue. If you still have the direct video link, it would be great if you could send it to me again.
Thanks again, and we’ll definitely take care of it
@CarsonRedCliffLabs if you edit your post, you can place the video inside a code block and that should stop it from rendering broken. I have to do it when I post.
@Leo - I just edited like @1F2Ns suggested. It’s working for me to copy and paste that loom video link into an incognito browser, so hopefully it works for you now to review the example.
Also, I just wanted to mention I’m not trying to be pushy about getting these bugs resolved immediately. I know you guys must be working 24/7 with all the feature releases and cheat sheets you’ve shared recently.
I just like coming in and making a note to log how many times an issue actually comes up so there is a reference of that beyond just a one time bug report.
