Update Reports docs for date filter relocation#749
Conversation
Reflects UI changes from mautic/mautic#16204: - Date range filter now appears above the Report table - Filters panel only appears when dynamic filters are configured - Updated terminology from "filters drop-down" to "Filters panel"
| - Opened by default - If you want to ensure that the date filters and filter options for any other Report filters are visible on a Report detail page without needing to open the filters drop-down, select Yes. For example, for an Emails Report, you might want to view dynamic filters for subject or sent date. | ||
| - Hide date range - To hide the date range filter so that Users can't change the dates that the Report displays data for, select to **Yes**. | ||
| - Opened by default - Select **Yes** to display dynamic filter options on the Report detail page without requiring Users to open the Filters panel. For example, in an Emails Report, you might want quick access to filters for subject or sent date. The Filters panel only appears when the Report has dynamic filters configured. | ||
| - Hide date range - Select **Yes** to hide the date range filter, preventing Users from changing the dates for the Report data. When visible, the date range filter appears above the Report table. |
There was a problem hiding this comment.
PR #16204 moves the date range filter from inside the Filters panel to above the Report table. The _details_report_content.html.twig file now includes the graph_dateselect.html.twig template above the table section, and the Filters panel in _details_content_header.html.twig now only renders when dynamicFilterFields is not empty.
Source: mautic/mautic#16204
Adds documentation for the Quick Filters feature that provides preset date ranges (Today, Yesterday, Last 7/30/90 days) next to the date range filter above the Report table.
|
@promptless-for-oss can we have one PR docs for each PR at mautic/mautic? That way, we can avoid blockers. |
|
Thanks for the feedback, @adiati98! That's a fair point — keeping one docs PR per source PR makes it easier to merge independently without blockers. I'll update my approach going forward to create separate documentation PRs for each source PR. For this specific case, the current PR combines changes from PR #16204 (moving the date filter above the table) and PR #16205 (adding quick date filters). Would you like me to split this into two separate docs PRs now, or is it okay to proceed with this combined PR since both source changes are closely related? |
Let's split it into two separate docs PRs because we never know if both PRs will be merged at the same time. |
|
Closing this PR as requested by @adiati98 — splitting into two separate docs PRs (one per source PR) to avoid blockers:
This approach allows each documentation change to be merged independently when its corresponding source PR is ready. |
|
Done! I've split the documentation into two separate PRs:
I've also added this as a workflow rule going forward — I'll create one docs PR per source PR to avoid blockers. |
2 participants
Open this suggestion in Promptless to view citations and reasoning process
Updates the Reports documentation to reflect UI changes where the date range filter now appears above the Report table instead of inside the Filters panel. Also clarifies that the Filters panel only appears when dynamic filters are configured.
Trigger Events
Tip: Attach PDFs in Slack messages to Promptless—it can even extract images from them 📎