app/templates/views/dashboard/template-statistics.html

{% from "components/table.html" import list_table, field, hidden_field_heading, right_aligned_field_heading %}
{% call(item, row_number) list_table(
  template_statistics,
  caption="By template",
  caption_visible=False,
  empty_message='You haven’t used any templates {}'.format(period),
  field_headings=['Template', hidden_field_heading('Type'), right_aligned_field_heading('Messages sent')]
) %}
  {% call field() %}
    <a href="{{ url_for('.view_template', service_id=current_service.id, template_id=item.template.id) }}">
      {{ item.template.name }}
    </a>
  {% endcall %}
  {% call field() %}
    {{'Text message' if 'sms' == item.template.template_type else 'Email'}}
  {% endcall %}
  {% call field(align='right') %}
    {{ item.usage_count }}
  {% endcall %}
{% endcall %}
-												Reword ‘recent templates’ section of dashboard

											
										
										
											2016-04-11 09:58:36 +01:00
+								{% from "components/table.html" import list_table, field, hidden_field_heading, right_aligned_field_heading %}
-												Add row numbers to tables

When a table is showing the contents of a CSV file, it should look
something like a spreadsheet.

The minimally skeuomorphic way to do this is by adding row numbers.

This commit doesn’t
- make the row numbers monospace (it’s barely noticeable and doesn’t
  reflect what actual spreadsheets do)
- make the first column heading ‘Row’ (again, doesn’t reflect how actual
  spreadsheets work, and takes up more valuable space)

											
										
										
											2016-04-05 11:16:29 +01:00
+								{% call(item, row_number) list_table(
-												Template statistics now surfaced on dashboard.

Job list removed.

Template statistics retrieved at same time as
notification stats.

											
										
										
											2016-04-05 11:40:13 +01:00
+								  template_statistics,
-												Show all statistics fetched on the dashboard

We want to align all our stats to be for the last 7 days.

This means summing up the stats response from the API to make the Big
Number. Previously the big number was counting sent notifications as
successful. This commit changes it to only look at delivered
notifications.

Right now, the API doesn’t have a way of filtering to only show the last
7 days. So for the moment the dashboard will show statistics for all
time.

The upshot of this is that we can link from the dashboard to the
activity page when there are failures.

											
										
										
											2016-04-19 12:57:55 +01:00
+								  caption="By template",
 								  caption_visible=False,
-												Show template usage for all time on it’s own page

> We show the last weeks template usage on the dashboard, which is
> great, but if you're looking for longer term trends, you're out of
> luck...

> So, let's let you see more on a more detailed page (linked from the
> dashboard). Initially this should just show you all templates that you
> have used ever and the count for each. Order same as dashboard, most
> popular first.

https://www.pivotaltracker.com/story/show/117614585

											
										
										
											2016-04-20 14:09:38 +01:00
+								  empty_message='You haven’t used any templates {}'.format(period),
-												Say ‘sent’ rather than ‘processed’

Hopefully users understand that sent != delivered

											
										
										
											2016-04-20 14:25:05 +01:00
+								  field_headings=['Template', hidden_field_heading('Type'), right_aligned_field_heading('Messages sent')]
-												Template statistics now surfaced on dashboard.

Job list removed.

Template statistics retrieved at same time as
notification stats.

											
										
										
											2016-04-05 11:40:13 +01:00
+								) %}
 								  {% call field() %}
-												Add view for a single template

> At the moment, we have an all email templates page, and an edit an
> individual page.
>
> This gets messy when we refer to templates like the dashboard and the
> activity views. We solve this currently by using anchor links to the
> list page, but this is clunky.
>
> So lets add it, then update the links on the dash and activity to the
> new view page.
>
> Should be a link from the view a single template page, to the template
> hub page.

https://www.pivotaltracker.com/story/show/117349227

											
										
										
											2016-04-12 09:55:51 +01:00
+								    <a href="{{ url_for('.view_template', service_id=current_service.id, template_id=item.template.id) }}">
-												Template statistics now surfaced on dashboard.

Job list removed.

Template statistics retrieved at same time as
notification stats.

											
										
										
											2016-04-05 11:40:13 +01:00
+								      {{ item.template.name }}
 								    </a>
 								  {% endcall %}
 								  {% call field() %}
-												Reword ‘recent templates’ section of dashboard

											
										
										
											2016-04-11 09:58:36 +01:00
+								    {{'Text message' if 'sms' == item.template.template_type else 'Email'}}
-												Template statistics now surfaced on dashboard.

Job list removed.

Template statistics retrieved at same time as
notification stats.

											
										
										
											2016-04-05 11:40:13 +01:00
+								  {% endcall %}
-												Add date field back into template stats

											
										
										
											2016-04-06 15:06:02 +01:00
+								  {% call field(align='right') %}
-												Template statistics now surfaced on dashboard.

Job list removed.

Template statistics retrieved at same time as
notification stats.

											
										
										
											2016-04-05 11:40:13 +01:00
+								    {{ item.usage_count }}
 								  {% endcall %}
 								{% endcall %}