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

Jump to bottom

when enable_create_realtime_segments is set to 0, explain to users that segmented reports will be available later #6731

Closed
mattab opened this issue Nov 27, 2014 · 2 comments
Closed

when enable_create_realtime_segments is set to 0, explain to users that segmented reports will be available later #6731

mattab opened this issue Nov 27, 2014 · 2 comments
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently. duplicate For issues that already existed in our issue tracker and were reported previously. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Milestone
Backlog (Help wan...

Comments

@mattab
Copy link
Member

mattab commented Nov 27, 2014

When enable_create_realtime_segments is set to 0 then all segments are created as Pre-processed by the cron which means that users won't be able to view data in real time.

This can cause confusion if users didn't notice the segment was not real time and they are expecting to see data....

Proposed solutions:

  • Show a notification explaining user has to wait (eg. few hours? up to one day?) before seeing the Segment data
  • Edit the message "There is no data for this report" to explain eg. "The data for this report has not been processed - please check again in a few hours."

Maybe you have other ideas?
@mattab mattab added Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. c: Usability For issues that let users achieve a defined goal more effectively or efficiently. labels Nov 27, 2014
@mattab mattab added this to the Short term milestone Dec 1, 2014
@mattab mattab added the Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. label Dec 1, 2014
@mattab
Copy link
Member Author

mattab commented Jul 14, 2016

There is a similar notification already displayed in Piwik in some cases:

segment not applied

Maybe this fixes this issue already. Users should see a notification anytime we know that the data will not be processed until later. Maybe we could in general even change the "There is no data for this report." message and change eg. "Please check back a bit later after these reports will be processed. We estimate the reports will be available in 1 hour 20 min. ". (we could keep track of successful cron:archive archiving, and estimate the time to next cron run). suggestions welcome!

@mattab
Copy link
Member Author

mattab commented Oct 21, 2019

This was done in the meantime in another issue.

@mattab mattab closed this as completed Oct 21, 2019
@mattab mattab added the duplicate For issues that already existed in our issue tracker and were reported previously. label Oct 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently. duplicate For issues that already existed in our issue tracker and were reported previously. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Milestone
Backlog (Help wanted)
Development

No branches or pull requests
1 participant
@mattab