Updated Views/Created Users View

## Description and Impact
No real impact, allows user to change time frame from which data is displayed.
Changed views to allow this to work.

## Deploy Plan
No Worries
## Rollback Plan
* To roll back this change, revert the merge with: `git revert -m 1 MERGE_SHA` and perform another deploy.

## URLs
> Links to bug tickets or user stories.

## QA Plan
> Fill in scenarios below. Review [QA Best Practices](https://source.sportngin.com/page/show/1227795-qa-best-practices).

#### Risk Level:
- [X] Low
- [ ] Medium
- [ ] High

Just make sure the time picker persists over requests and changing pages, and views update accordingly.
I put it as one td because it’s more of a blurb of info, which I feel doesn’t really lend itself to being table-ized
On Jun 19, 2014, at 11:16 AM, Andy Fleener <notifications@github.com> wrote:

> In app/views/hubstats/metrics/_pulls_table.html.erb:
> 
> > @@ -0,0 +1,7 @@
> > +<table class="table">
> > +  <% @pull_requests.each do |pull| %>
> > +    <tr>
> > +      <td><%= link_to pull.title, repo_pull_request_path({:repo => @repo.name, :id => pull.id}) %> by <b> <%= pull.user.login %> </b> <%= distance_of_time_in_words(DateTime.now,pull.closed_at) %> ago </td>
> This feels like 3 separate data fields that should have their own td.
> 
> —
> Reply to this email directly or view it on GitHub.
>