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

Invalidate the 'All' segment only #63

Open
heurteph-ei opened this issue Sep 12, 2023 · 3 comments
Open

Invalidate the 'All' segment only #63

heurteph-ei opened this issue Sep 12, 2023 · 3 comments

Comments

@heurteph-ei
Copy link

As it is possible to invalidate this segment or another one... Or All segments, it could be interesting to invalidate just only the 'default' segment: ALL. (as a segment, not to invalidate all segments)
(also it could be good to select custom reports to invalidate, I saw this: #11 but has been closed 😞)

@snake14
Copy link
Contributor

snake14 commented Sep 12, 2023

Hi @heurteph-ei . Thank you for taking the time to create this issue and do some searching ahead of time. Doesn't the ALL VISITS segment inherently include all other segments? If not, you could give the console command a try. It looks like you can specify a segment by its UI name, so possibly ALL VISITS. I imagine that it would end up invalidating all segments though.
image

@heurteph-ei
Copy link
Author

heurteph-ei commented Sep 13, 2023

Hi @snake14
The problem is in the segment selection combobox:
image
image

@snake14
Copy link
Contributor

snake14 commented Sep 13, 2023

@heurteph-ei Thank you for the screenshots. We're currently unable to add that option. There is a core issue to add the ability to invalidate 'ALL VISITS' without invalidating all segments. Once that has been implemented, we should hopefully be able to add that as an option for this plugin.

@snake14 snake14 added this to the For Priortisation milestone Sep 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants