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
Core: Provide custom date range feature #572
Comments
Think this is a must as a core feature, and was the first thing one of my users asked :) |
I think this is a must-have. Amazing that there is so little request for this feauture. |
Agree, this is a must have feature. |
I would suggest a different spec than mentioned in the ticket desc:
|
See also 'Week beginning setting' #1633 |
When this is implemented, we can improve user settings, and allow to set the default date to "Last 7 days", "Last 30 days", etc. |
I agree with @greg's suggestion of implementation. Has anyone begun on this? If not, I can look into it, but I don't want to step on someone else's half-completed implementation. Thank you. |
mrisher, work hasn't started on this so feel free to pick it up. However, I think the proposed implementation should be followed (Piwik chooses which is the most efficient way of archiving custom date ranges, selecting weeks and/or months when this is faster). |
Hi, Matt: I wanted to update the comment so nobody else was scared off. Sorry, |
I'm working on this preferring a last N Days range since I do not need a in between Dates range. Hope to come up with this soon. Regards, Ron |
(In [4159]) Refs #572
TODO
NB: 3 tests fail in Main.test.php on my box, but I'm really not sure why... let's see if Jenkins fails as well |
(In [4170]) Refs #572 Fixing bug when the range goes in the future of current month, forcing to stop at the specified end date |
(In [4171]) Refs #572 Health checks |
Note: update FAQ: http://piwik.org/faq/how-to/#faq_33 when feature released |
(In [4174]) Refs #572 Fixing known archiving issues when period=range |
(In [4188]) Refs #572
Testing is welcome, please report any bug you find! |
(In [4189]) Refs #572
|
(In [4190]) Adding unit tests metadata & range & last7 refs #572 |
(In [4192]) Refactor JS & css + i18n Refs #572 |
I'm thinking it would be nice to show, in the calendar, "Last 7 days", "Last 30 days", etc. but I don't know how to show these without making the calendar look complicated/ugly. Any idea? |
(In [4193]) Fixing broken admin UI (Anthon, could we add a simple webtest request that checks no JS errors?) refs #572 |
Checking all the screens and widgets for errors is on the todo list. It will have to wait until we get Selenium tests as there are some blocking webtest bugs. |
(In [4207]) Refs #572 All Websites dashboard now work when a range is selected |
(In [4215]) Refs #572 PDF reports now work with a Custom Date Range |
(In [4216]) Refs #572 Fixing Widgetize screen with Custom Date Range. All known bug fixed! RC release soon? |
(In [4217]) Refs #572
|
Marking as fixed since all known issues are fixed. Please test on trunk and report any problem you have with this feature! |
(In [4252]) Refs #572
|
(In [4255]) Refs #572 Deleting "Custom Date Range" reports after 1 day, since they can be re-processed and would take up unecessary space |
(In [4342]) Refs #572 lastN and previousN were buggy for custom date ranges, added tests + fixed algorithm |
Piwik provides reports for days, weeks, month and year, but not for custom date ranges.
The mechanism used to process reports for weeks, month and year use a generic code that could be used to generate reports on any custom date range.
List of changes to make this happen:
- the date range should be set in the “date” parameter and not in a new parameter date_range, and “period” parameter would be “range”
- Archiving: when period=range, the Archiving code will test if an archive exists already. If it doesn’t, it will look at the most efficient way to process the range: the minimum number of sub date ranges.
– For example, requesting data from Jan 1st to March 15th 2009:
– we can sum jan month + feb + sum of the first 15 days of july? which is 17 archives to select and sum
– but if we minimize the nb of date ranges in the requested range, by doing: jan + feb + day 1st of march + week from 2nd to 8th + week from 9th to 15th, we only select & sum 5 archives which will be a lot more efficient and better user experience.
The archive sum of all sub archives will then be recorded and read as normal.
- UI: period selector will change to use a calendar that allows for date range selector ([example](http://eyecon.ro/datepicker/)). We could add “Date range” after “day, month, year” buttons, when clicked would show 2 calendars.
- UI: maybe it would be nice to show date ranges shortcut, “last 7 days”, “last 30 days” somehow ?
- QA: add new integration tests that test with the date range “date=2011-01-01,2011-03-22&period=range”
- Note: none of the plugins code for Archiving, API querying etc. will need to be modified, since all the logic is hidden
Any ideas? Any volunteer to work on this interesting challenge? Please comment :)
The text was updated successfully, but these errors were encountered: