Closed Bug 1131129 Opened 9 years ago Closed 5 years ago

I'd like to be able to select specific periods of time in order to check for a single contributor's activity

Categories

(support.mozilla.org :: Users and Groups, task, P3)

Tracking

(Not tracked)

RESOLVED WONTFIX
2015Q1

People

(Reporter: atopal, Unassigned)

References

Details

(Whiteboard: u=sumo-team c=community-hub p= s=)

User Story

[S] I as a community manager would like to be able to select specific periods of time in order to check for a single contributor's activity (e.g. I would like to see what cor-el has contributed from day x to day y) so that I can message him

Acceptance Criteria:

* User can select a time frame for any listing on the community hub
* Clicking the time frame selector opens up a calendar widget
* The default range is “last 90 days”
* User can select start date range in a month view
* User can select end date for range a month view
* User can show previous and next month in the month view
* To the right of the start and end date selector is a list of common date ranges:
** Today
** Yesterday
** Last 7 days
** Last 30 days
** This Month
** Last 90 days
** All time
** Custom Range
** User can input a custom range in the form of YYYY-MM-DD
** This range is updated with the selector data
* The User can click the “Apply” button to apply the date range and hide the widget
* The User can click the “Cancel” button to not change anything and hide the date range widget.
[S] I as a community manager would like to be able to select specific periods of time in order to check for a single contributor's activity (e.g. I would like to see what cor-el has contributed from day x to day y) so that I can message him
User Story: (updated)
Blocks: 1131149
User Story: (updated)
User Story: (updated)
Looks good to me.
Depends on: 1143945
Priority: P2 → P3
(a non-developer guess) Switching to ElasticSearch v2 probably means changes in how this could be implemented.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.