Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UX: when you apply a segment within the goal report, it goes back to default report channel type #21847

Open
Chardonneaur opened this issue Jan 24, 2024 · 1 comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. triaged

Comments

@Chardonneaur
Copy link

Hi Team,

When you visit the goal report page: https://demo.matomo.cloud/index.php?module=CoreHome&action=index&idSite=1&period=day&date=yesterday#?idSite=1&period=day&date=yesterday&segment=visitConvertedGoalId%3D%3D7&category=Goals_Goals&subcategory=General_Overview.
If you click on any reports: Search engines, Page URLs, Country, and then you select segment... then it goes back on the Channel Type report.
That's non logic.
Normally you should stick on the report you previously selected.

@Chardonneaur Chardonneaur added Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. To Triage An issue awaiting triage by a Matomo core team member labels Jan 24, 2024
@sgiehl
Copy link
Member

sgiehl commented Feb 8, 2024

This is caused by the way our report pages are built / rendered. When a segment or date is changed it triggers the whole reporting page to reload. The reporting page can contain various widgets, but might also call middleware API to check which widgets to display. Afterwards those widgets are loaded with the current data.

To realize the requested behavior we would need to change how the flow currently works. For pages that contain fixed widgets, that might be easily doable, as we could only trigger a refresh of a widget. But as soon as some middleware is involved, that becomes more complicated.

Rewriting how the report page loading is organized might be a bit more effort.

@sgiehl sgiehl removed the To Triage An issue awaiting triage by a Matomo core team member label Feb 8, 2024
@sgiehl sgiehl added this to the For Prioritization milestone Feb 8, 2024
@ronak-innocraft ronak-innocraft added Bug For errors / faults / flaws / inconsistencies etc. and removed Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. labels Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. triaged
Projects
None yet
Development

No branches or pull requests

4 participants