User Story: View table of all jobs sent with my service

[em-herrick]

As a Notify Admin, I want an aggregate level data on the jobs my team has sent with my service over time so that I can track usage trends, review sender's work, and report out on system usage over time.

Detailed condition or criteria that must be met for the user story to be considered complete.

Users should have a historic record of aggregate level data of jobs completed. Because we delete phone number record data after 7-days, this table provides a history of system usage beyond this timeframe.

If indvidual jobs are less than 7-days old, users can access invidual job reports from this table. If the jobs are older than 7 days, summaries of the job information should still be viewable.

Eventually Users should be able to search these records and sort table columns as needed. Pagination should also be included.

List of specific tasks or sub-tasks that need to be done to implement the user story.

• [ ] Review Jobs page in wireframe and match UI styles.

  • Note: we're replacing the word "Job" with "Activity" as we implement this page

• [ ] Create a new page (that will be linked in our side navigation) for a new jobs page, to be titled "Activity": notify.gov/activity

• [ ] Build a table labeled Activity that displays all jobs sent within a specific Service instance.

  • [ ] Columns should include: 'Uploaded File', 'Template', Time Sent, Sender, Reports, # of Recipients, and Message Parts Used
  • [ ] In "Reports" column: Add a download icon/option for jobs less than 7-days old. Display a N/A in this column if job is older than 7-days.
  • [ ] Explore/talk to Bev if existing endpoint exists for "Message parts used per job" see note below.

• [ ] Review Search and Pagination functions available on other pages in the application.

  • [ ] Test out search function, assess what it would take to get this working
  • [ ] Ensure pagination is cleaned up and working (also test and gather level of effort to fix, if broken)

List any dependencies that need to be resolved before starting or completing this user story.

Please explore level of effort needed for both of these things, and we can prioritize whats most needed first:

• [ ] We may need a new endpoint for Message Parts for a whole Job—this would be an aggregate number of: # of phone numbers in the job [times] # of message parts per phone number. I don't believe this exists.
• [ ] Search and Pagination—these things are displayed but not currently functional. We're looking for an assessment on what is needed to make them work and how long it make take.

Any additional information or context that might be useful for the team.

No response

[em-herrick]

Em to add:

• do we charge for message parts delivered? or sent?
• Add delivery rate to column